Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How to connect DB2 v2.1 on OS/2 using ODBC from Windows ?

Status
Not open for further replies.

rmani13

Programmer
Aug 16, 2002
6
US
Hi,

I am in need of connecting to a DB2 database (v2.1) in OS/2 Warp thru ODBC from my windows system. The OS/2 system is connected in my network with TCP/IP. I have my windows system installed with DB2 client which comes along with the UDB 7.1. As per the help I have configured the TCP port number for the db2 in OS/2 in the Services file. But the service name (svcename) field in the database configuration dialog is disabled, so I couldn't enable the db2 database for TCP/IP listening.

Please help me to configure this. Is there any work around ?

Thanks in advance.

Regards
Manikandan
 
i think the client can only work with one version up or down... did you try updating the db cfg from the command line in the command window?
 
Hi,

If you mean the cataloging stuff to be done at the client, then I have done that. I am aware that the client can access one or two versions up or down with the database. Does it mean that these 2.1 databases is OS/2 platforms cannot be accessed with higher versions of DB2 clients in Windows (UDB 7.1)?
While trying this at times the DB2ENG.DLL in the OS/2 system crashes with sys3175. I feel there is no communication problem. It would be better if any one let me know the configuration to be done at the server and the client. FYI these two machines are in a TCP/IP network.

Thanks
Regards
Manikandan
 
try:
db2 "update dbm cfg using svcename whateveryourservicenameis"
from the command line
 
Hi,

I again got the followin error after I updated the dbm.

The connection test failed.

[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 error: "recv". Protocol specific error code(s): "*", "*", "0". SQLSTATE=08001

Regards
Manikandan
 
It looks as though you do not have DB2COMM set to tcp/ip... use the db2set command to set it correctly
 
Hi,

I have gone thru the help materials and configured almost everything. DB2COMM environment variable has been configured to TCPIP as part of first steps.

Please list everything you know off so that I can use that as a checklist instead of one by one.

It would be of great help.

Thanks
regards
Manikandan
 
Hi,

I have gone thru the help materials and configured almost everything. DB2COMM environment variable has been configured to TCPIP as part of first steps.

Please list everything you know off so that I can use that as a checklist instead of one by one.

It would be of great help.

Thanks
regards
Manikandan
 
Hi,

I have gone thru the help materials and configured almost everything. DB2COMM environment variable has been configured to TCPIP as part of first steps.

Please list everything you know off so that I can use that as a checklist instead of one by one.

It would be of great help.

Thanks
regards
Manikandan
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top