Configuring connections to IBM mainframe database servers

You can manually configure your TCP/IP connection between a Db2 Connect server and a IBM mainframe database using the Db2® command line processor (CLP). For details on configuring connection using db2dsdriver.cfg, see the topic about db2dsdriver configuration file.

Before you begin

Before you manually configure a TCP/IP connection between Db2 Connect and a IBM mainframe database server, ensure that:
  • TCP/IP is functional on the Db2 Connect server and IBM mainframe system.
  • You have identified the following parameter values:
    • Hostname (hostname) or IP address (ip_address)
    • Connection Service name (svcename) or Port number/Protocol (port_number/tcp)
    • Target database name (target_dbname)
    • Local database name (local_dcsname)
    • Node name (node_name)

Procedure

To manually configure TCP/IP communications between your Db2 Connect server and an IBM mainframe database:

  1. Configure TCP/IP on the Db2 Connect server.
  2. Catalog the TCP/IP node.
  3. Catalog the IBM mainframe database as a Database Connection Service (DCS) database.
  4. Catalog the IBM mainframe database.
  5. Bind utilities and applications to the IBM mainframe database server.
  6. Test the IBM mainframe connection.

Results

Note: Due to the characteristics of the TCP/IP protocol, TCP/IP might not be immediately notified of a partner's failure on another IBM mainframe. As a result, a client application accessing a remote Db2 server using TCP/IP, or the corresponding agent at the server, might sometimes appear to be hung. The TCP/IP SO_KEEPALIVE socket option is used to detect when there has been a failure and the TCP/IP connection has been broken.