Typically to do this you need to 1) create a DB2 instance on the DB2 Connect server. Normally this would have been done during the installation process unless the installer had specifically skipped the step. 2) attach to the instance on the zLinusx system 3) catalog tcpip node <zos db2 location name> remote 192.168.1.69 server <port#-of-zos- db2> system <zosname> ostype os390 4) attach to the DB2 client instance on the XP workstation 5) catalog tcpip node <somename2> remote 10.128.24.232 server <port#-of-zlinux-db2- connect> system <zlinux> ostype linux
Your client now issues connect to <somename2> user <zos-user-id> using <zos-password> automagically the connection is made to the DB2 connect which transforms the connection request and passes it on to the Zos DB2 system. I presume you've read Quick Beginnings for DB2 Connect Enterprise Edition http://publib.boulder.ibm.com/infocenter/db2luw/v8/topic/com.ibm.db2.udb.doc/conn/c00082 25.htm covers the basic scenarios. I'd suggest that DB2-L might be a better place to raise this problem - as it seems to be a DB2 Connect, rather than a zLinux, problem. http://www.idugdb2-l.org/adminscripts/wa.exe?REPORT&z=3 Alternatively the comp.databases.ibm-db2 newsgroup - although it is more orientated towards DB2 on LUW database (rather than Connect) issues James Campbell ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
