This section assumes that TCP/IP is functional on the DB2 Connect and host systems.
See Software Requirements for the communication protocol requirements for your platform. See Possible Client-to-Server Connectivity Scenarios for the protocols supported for communication between your particular client and server.
To set up TCP/IP communications between your DB2 Connect workstation and a host database server, perform the following steps:
Step 1. | Identify and record parameter values. |
Step 2. | Configure the DB2 Connect workstation:
|
Step 3. | Catalog the TCP/IP node. |
Step 4. | Catalog the database. |
Step 5. | Catalog the database as a Database Connection Service (DCS) database. |
Step 6. | Bind utilities and applications to the database server. |
Step 7. | Test the host connection.
|
![]() |
Due to the characteristics of the TCP/IP protocol, TCP/IP may not be immediately notified of the failure of a partner on another host. As a result, a client application accessing a remote DB2 server using TCP/IP, or the corresponding agent at the server, may sometimes appear to be hung. DB2 uses the TCP/IP SO_KEEPALIVE socket option to detect when there has been a failure and the TCP/IP connection has been broken. If you are experiencing problems with your TCP/IP connection, refer to the
Troubleshooting Guide for information on how to adjust this parameter and other common TCP/IP
problems.
|