JDBC connect to OS/390 subsystem

Kirk Hampton

JDBC connect to OS/390 subsystem
Hi all,
good to have the group back 'on the air', long time listener,
first time caller.

We are OS/390 v 2.6 running (I believe) the Websphere - formerly
known as Domino Go - web server. We are successfully running
Net.Data queries on our intranet against any of three DB2
subsystems that all run on the same LPAR (one test, two prod).
Now we are experimenting with Java and JDBC, and running the
sample Java application that comes with the JDBC installation. We
can only seem to make this work (all it does is a SELECT * from
SYSTABLES) if we name our test DB2 subsystem in the application.
When we put either of the Prod names in it, it gets an error saying
location name was not found. I feel like somewhere, maybe in
websphere, we have only named one DB2 ssid, and that's the only
place it can connect to.

Has anyone else tried out JDBC, and can you select which DB2 ssid
to connect to ?
TIA,
Kirk Hampton
DB2 Systems Programmer
TXU Electric and Gas
Dallas, TX

BUFF (PB) COLLINS

Re: JDBC connect to OS/390 subsystem
(in response to Kirk Hampton)
Hello. I believe all you need to do is change the DB2SQLJSSID=ssid in
your JDBC properties file. This is assuming you have bound the JDBC
packages and plans on the other DB2 you are trying to select from.



Buff Collins - DB2 System Support
Pacific Bell - EACOLLI@.PACBELL.COM


-----Original Message-----
From: Kirk Hampton [mailto:[login to unmask email]
Sent: Thursday, October 07, 1999 12:33 PM
To: [login to unmask email]
Subject: JDBC connect to OS/390 subsystem


Hi all,
good to have the group back 'on the air', long time listener,
first time caller.

We are OS/390 v 2.6 running (I believe) the Websphere - formerly
known as Domino Go - web server. We are successfully running
Net.Data queries on our intranet against any of three DB2
subsystems that all run on the same LPAR (one test, two prod).
Now we are experimenting with Java and JDBC, and running the
sample Java application that comes with the JDBC installation. We
can only seem to make this work (all it does is a SELECT * from
SYSTABLES) if we name our test DB2 subsystem in the application.
When we put either of the Prod names in it, it gets an error saying
location name was not found. I feel like somewhere, maybe in
websphere, we have only named one DB2 ssid, and that's the only
place it can connect to.

Has anyone else tried out JDBC, and can you select which DB2 ssid
to connect to ?
TIA,
Kirk Hampton
DB2 Systems Programmer
TXU Electric and Gas
Dallas, TX