Backing off to the 4.1.3 ODBC driver works for me also. Hopefully I don't
run into lost functionality by backing off to an older version, but for now
this will work.
Tivoli's first level support needs to look a little deeper at some of these
reported problems before throwing up their hands.
Tha
I uninstalled the 4.2.1.0 ODBC driver, and installed the previous 4.1.3.0
ODBC driver. Now things are working just fine. I'll stick with this
configuration for the time being.
I will update the PMR with this information to see if Tivoli would like to
pursue it.
Bill
-Original Message-
F
