Configuring TCP/IP for DB2 Universal Database for OS/390 and z/OS
This topic describes how to configure TCP/IP communications between your DB2 Connect™ workstation and DB2® Universal Database (UDB) for OS/390® and z/OS® Version 7 or later. The instructions assume the following conditions:
- You are connecting to a single host database via TCP/IP. Multiple host connections will be handled in exactly the same way, although the port number and service number required in each case might be different.
- The target database resides on DB2 UDB for OS/390 and z/OS Version 7 or later.
- All the necessary software prerequisites are installed.
- DB2 clients have been set up as required.
- Before you can use DB2 Connect over a TCP/IP connection, collect information about both the host database server and the DB2 Connect server. For each host server that you are connecting to via TCP/IP, have the following information:
- The location of the TCP/IP services and hosts files at the DB2 Connect workstation:
- On UNIX® and Linux
- /etc/
- On Windows® XP and Windows Server 2003
- Usually %SystemRoot%\system32\drivers\etc\, where %SystemRoot% represents the Windows install path directory.
You might want to add the host information to a domain name server to avoid maintaining this file on multiple systems.
- The locations of the equivalent files at the target DB2 Universal Database™ for z/OS and OS/390 host.
- The TCP/IP port number defined to DB2 Universal Database for z/OS and OS/390.
Note: The associated service name information is not exchanged between the DB2 Connect workstation and DB2 Universal Database for z/OS and OS/390. Port number 446 has been registered as the default for communication from a DB2 Connect workstation.
- The TCP/IP addresses and host names for both the host and the DB2 Connect workstation.
- The LOCATION NAME of the DB2 for OS/390 database server.
- The user ID and password to be used when issuing CONNECT requests to the database at the host or System i™ server.
- Refer to your local network administrator and your DB2 for OS/390 and z/OS administrator for help getting this information. Use the tables that follow as a worksheet to plan each TCP/IP connection between DB2 Connect and a host database server.
Table 1. User InformationRef. |
Description |
Sample Value |
Your Value |
TCP-1 |
User name |
A.D.B.User |
|
TCP-2 |
Contact info |
(123)-456-7890 |
|
TCP-5 |
User ID |
ADBUSER |
|
TCP-6 |
Database type |
db2390 |
|
TCP-7 |
Connection type (must be TCPIP). |
TCPIP |
TCPIP |
Table 2. Network Elements at the HostRef. |
Description |
Sample Value |
Your Value |
TCP-8 |
Host name |
MVSHOST |
|
TCP-9 |
Host IP address |
9.21.152.100 |
|
TCP-10 |
Service name |
db2inst1c |
|
TCP-11 |
Port number |
446 |
446 |
TCP-12 |
LOCATION NAME |
NEW_YORK3 |
|
TCP-13 |
User ID |
|
|
TCP-14 |
Password |
|
|
Note:
- To obtain the host's IP address TCP-9, enter at the host:
TSO NETSTAT HOME
- To obtain the port number TCP-11, look for DSNL004I in the DB2 master address space or system log.
Table 3. Network Elements at the DB2 Connect WorkstationRef. |
Description |
Sample Value |
Your Value |
TCP-18 |
Host name |
mcook02 |
|
TCP-19 |
IP address |
9.21.27.179 |
|
TCP-20 |
Service name |
db2inst1c |
|
TCP-21 |
Port number |
446 |
446 |
Table 4. DB2 Directory Entries at the DB2 Connect WorkstationRef. |
Description |
Sample Value |
Your Value |
TCP-30 |
Node name |
MVSIPNOD |
|
TCP-31 |
Database name |
nyc3 |
|
TCP-32 |
Database alias |
mvsipdb1 |
|
TCP-33 |
DCS database name |
nyc3 |
|
- Complete a copy of the worksheet example for each TCP/IP host:
- Fill in the values to be used for the host name and IP address of the DB2 Universal Database for z/OS and OS/390 host (TCP-8 and TCP-9).
- Fill in the values to be used for the host name and IP address of the DB2 Connect workstation (TCP-18 and TCP-19).
- Determine the service name or port number to be used for the connection (TCP-10 or TCP-20, or TCP-11 or TCP-21).
- Determine the LOCATION NAME of the DB2 for OS/390 and z/OS database server to which you want to connect.
- Determine the values to be used for user ID and PASSWORD when connecting to the host database.
- At your zSeries® server:
- Verify the host address or the host name.
- Verify the port number or the service name.
- Update the services file with the correct port number and service name if necessary.
- Update the hosts file (or the Domain Name Server used by the DB2 Universal Database for z/OS and OS/390 system)
with the host name and IP address of the DB2 Connect workstation if necessary.
- Ensure the new definitions are active before attempting to test the connection. Refer to your host network administrator or change control staff if necessary.
- Check with the DB2 Universal Database for z/OS and OS/390 administrator that you have a valid user ID, password, and database LOCATION NAME.
- PING the DB2 Connect server, using the correct port number if that option is supported by TCP/IP on the host system. For example:
ping remote_host_name -p port_number
Note: DB2 Connect does not support the PING command when issued from a Version 7 client through a Version 9 gateway to the host.
Support for your zSeries or OS/390 server is available at http://www.ibm.com/servers/eserver/support/zseries/
Parent topic: Preparing DB2 Universal Database for OS/390 and z/OS for connections from DB2 Connect