Very Computer

Class.forName(jdbcDriver);
catalogConn = DriverManager.getConnection(Url, username, password);

the url is jdbc:db2://172.16.4.86:50000/hd1100pd, but got below error,

CLI0616E Error opening socket.  

Explanation: Cannot open the socket to server, server may be down.

but if i using the same coding and start the app server on my machine,
i have no problem connect to database. why is that?

Quote:> i am able to install db2 v8.1 on my  window 2000  machine. and use
> type 4 driver which come with installation com.ibm.db2.jcc.DB2Driver,
> i have a client try to start an app server on his machine and
> connection to my machine which is db server to retrive data with
> coding

> Class.forName(jdbcDriver);
> catalogConn = DriverManager.getConnection(Url, username, password);

> the url is jdbc:db2://172.16.4.86:50000/hd1100pd, but got below error,

> CLI0616E Error opening socket.

> Explanation: Cannot open the socket to server, server may be down.

> but if i using the same coding and start the app server on my machine,
> i have no problem connect to database. why is that?

--
Knut Stolze
DB2 Spatial Extender
IBM Germany / University of Jena

Sounds like your listener may not be started.

Paul.

client and server here are all within network, there is no firewall in
between, and server has TCP/IP configuration setup, since type 4
driver use TCP/IP for communication, why the client can't access the
server?

Quote:> i am able to install db2 v8.1 on my  window 2000  machine. and use
> type 4 driver which come with installation com.ibm.db2.jcc.DB2Driver,
> Class.forName(jdbcDriver);

Perhaps because of this it doesn't find the proper net driver and (if
you still have db2java.zip in the classpath) trys the app driver
instead. A CLI error sounds like it's using the old app driver. Just a
guess.

I have also had problems with errors like you mention trying to
connect between versions. 8 really doesn't want to talk to 7.

we had the same problems with db2 v8.1 on a win2000 machine.
we used jdbc type 4 driver to access the db using the
com.ibm.db2.jcc.DB2Driver and opened the connection with the url
"jdbc:db2://57.56.x.y:50000/PROD".
the result was same message. furthermore the db2 database on th
win2000 machine hangs up and nothing could be done with the database.
the solution was to reboot the machine.
i think he problem is the port "50000". everything on our db2 win2000
machine is installed and configured correctly. tcp/ip is set, registry
variable db2comm is set, port is set, tcp/ip service name is set.

after hours of tests i think there is still a bug inside db2 v8.1 or
the new type 4 driver.

anbody agreeing ?