Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / January 2006

Tip: Looking for answers? Try searching our database.

DB2 Connectivity problem from a wndows client to DB2 AS/390 server

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
techsatish@gmail.com - 16 Jan 2006 10:45 GMT
hi all,

I have a DB2 connect PE ver 8.2 installed in my windows client which
tries to connect to AS/390 Database Instance via CCA.It uses TCP/IP.

While trying to connect the Server from the windows client

SQL30081N  A communication error has been detected.  Communication
protocol being used: "TCP/IP".  Communication API being used:
"SOCKETS".  Location where the error was detected: "192.168.134.201".
Communication function detecting the error: "connect".  Protocol
specific error code(s): "10060", "*", "*".  SQLSTATE=08001

My windows is running DB2 Connect ver 8.2
Mainframe is running IBM UDB ver 7.1

What cause this error and how do i resolve this?
Note:here my ports are open from either side

TIA
-Satish Sivasubramanian Gopinathan
doug - 17 Jan 2006 19:10 GMT
First check with your OS390 DBA's and check to see if they have setup
the required TCPIP entries for mainframe connects with in DB2 on OS390.

If so get the Location name and port number.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.