Error connecting to V9 remote database

[mairhtin o'feannag]

Hello,

I'm having problems connecting to my new v9 db box. The pertinent
information is below:

DB2_db2inst1 60000/tcp
DB2_db2inst1_1 60001/tcp
DB2_db2inst1_2 60002/tcp
DB2_db2inst1_EN D 60003/tcp

TCP/IP Service name (SVCENAME) = DB2_db2inst1

[db2inst1@mairht in db2dump]$ db2set
AUTOSTART=yes
DB2COMM=tcpip

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

db2 catalog tcpip node homesvr remote 67.170.223.55 server DB2
_db2inst1
db2 catalog db sample as sample2 at node homesvr
Database 2 entry:

Database alias = SAMPLE2
Database name = SAMPLE
Node name = HOMESVR
Database release level = b.00
Comment =
Directory entry type = Remote
Catalog database partition number = -1
Alternate server hostname =
Alternate server port number =

Node 1 entry:

Node name = HOMESVR
Comment =
Directory entry type = LOCAL
Protocol = TCPIP
Hostname = 67.170.223.55
Service name = DB2_db2inst1
Any help would be appreciated.

Mairhtin O'Feannag

[Knokmans]

You can give a db2 ? <messageon the commandline. I quote:

db2 ? SQL1337N
SQL1337N The service "<service-name>" was not found.
Explanation:
The system cannot resolve the port number associated with the
service-name. Possible causes are:
o An incorrect service-name value was specified when the TCP/IP
node was cataloged.
o The correct service-name was specified, but was not defined
in the client's services file.

Federated system users: this situation can also be detected by
the data source.

User Response:
Make sure that the service-name specified when cataloging the
TCP/IP node is a correct name, and that it is defined in the
local services file.
Federated system users must also ensure that the name is defined
in the services file at the data source.
"Knut Stolze" <st****@de.ibm. comwrote in message
news:59******** *****@mid.indiv idual.net...

mairhtin o'feannag wrote:

>I have done just that several times. Currently the SVCENAME is set to
50000, which is why I cannot understand the reference to db2cdb2inst1
on the connecting machine. It is obviously being "picked up" from the
server side of the conversation. Then it complains (actually DB2
complains) that it cannot find the service :

SQL1337N The service "db2cdb2ins t1" was not found.

Just a guess: do you have "db2cdb2ins t1" in your /etc/services file on the
client system set to port 50000?

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany