I am trying to connect to a DB2 database, but getting the following error every time:
*** Error: (08001) [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting
The connection string I am using is:
I can connect to the database through an ODBC Connection Test tool, so that tells me the ODBC part is configured and connections are possible. But in SilkTest (5.5), the connection fails.
Does anything special need to be done to allow SilkTest to talk to the IBM DB2 ODBC Driver?
I don't have a problem accessing a DB2 (UDB) database with licensed DataDirect drivers. My connection string looks like yours. Seems as if IBM did something specific to their driver, or maybe there's a setting in the ODBC control panel for the driver you can tweak.
SQA Automation Team Manager
Workforce Central Group
E-Mail: email@example.com www.kronos.com
Improving the Performance of People and Business™
DSN is defined in the ODBC Data Source Admin (from Control Panel), as a System DSN - same place my Oracle and Excel DSN's are defined.
The DSN works - I can connect with the Oracle ODBC Tester (which can connect via ODBC to any defined DSN entry) and I downloaded a program called "Advanced Query Tool" which also works through ODBC. The entry I have for the DB2 database works fine. It is just with SilkTest that I am getting this error.
There might be some other Attributes that are needed to pass to the ODBC driver (currenly just passing UID and PWD). But which ones? I tried also passing the Server (SRVR), but that didn't help (and shouldn't be needed since the DSN entry just points to the DB2 Profile that has all of the connection information other than the username and password).
The only item I have heard, both from Steven Tyler (post above) and from others is that they use third-party ODBC drivers. That gets expensive (I have 12 systems I need to get this working on).