Use the following procedure to configure the TCP/IP software for XDB Link. Use your values from the TCP Host/Service worksheet to complete these steps.
To configure TCP/IP perform the following steps:
- Install a TCP/IP protocol. If a TCP/IP protocol is already installed (for example, Microsoft TCP/IP), ensure that it is enabled.
- Make a backup copy of the HOSTS and SERVICES files (under Windows 95, these files are called HOSTS.SAM and SERVICES.SAM).
| If you a running under... |
Look for these files in... |
| Windows NT |
C:\WinNT\SYSTEM32\DRIVERS\ETC
|
| Windows 95 or 98 |
C:\WINDOWS
|
- Add the following line to the HOSTS file:
IPAddress IPName
where:
- IPAddress specifies the TCP/IP address of the host system. Use the value in J1 of the TCP Host/Service worksheet.
- IPName is a name that you assign to this address. Type IPName in uppercase letters. Lowercase characters will cause problems under certain circumstances. Use the value in J2 of the TCP Host/Service Worksheet.
For example: 204.17.148.230 LUDB2
Note:
If this is the last line in the HOSTS file, type a carriage return at the end of the line.
- Edit the SERVICES file by adding the following line:
ServiceName Port/tcp
where:
ServiceName specifies a name that represents the port number on the host system. (You will use this name when you configure XDB Link in a later step.) Type the ServiceName in uppercase letters. Lowercase characters will cause problems under certain circumstances.
Port specifies the dedicated TCP/IP port assigned to the XDB Link Host Option on the host system. Use the value in J4 of the TCP Host/Service worksheet.
For example:
XDBSRV 5170/tcp
Note:
If this is the last line in the SERVICES file, type a carriage return at the end of the line.
When connecting to DB2 with native TCP/IP:
- Choose DRDA(TCP/IP) as your Connection Type
- The Remote Host entry should match the mainframe's IP address entry in your HOSTS file.
- The port entry should match the DB2 port entry in your SERVICES file. IBM's default port is 446/tcp but users should check with their administrators to find out what port their DB2 listens on.
