In this section, we describe the possible alternatives and the steps during the implementation of the connectivity configuration and the OS/390 functions. The environment consists of two workstations connected in a LAN remotely connected to the OS/390. One of the workstations has been also used as a gateway.
To prepare DB2 UDB for OS/390 to receive connection requests from DB2 Connect, you must complete the following steps at the OS/390 host:
Prepare OS/390 for DB2 Connect.
This step consists of making sure that DB2 is at the right maintenance level and that TCP/IP is active on the host system.
Verify the DB2 for OS/390 maintenance (i.e., PTFs).
Verify the TCP/IP on OS/390 (i.e., started tasks TCPIPMVS and TCIPOE).
Configure TCP/IP for DB2 UDB for OS/390.
This step consists of configuring TCP/IP communications between your DB2 Connect workstation and the DRDA Application Servers running DB2 for OS/390.
Prepare the LE/370 run-time library in the DDF startup JCL procedure.
Enable DDF for MVS OpenEdition in RACF.
Customize the TCP/IP data sets or files.
Configure DB2 UDB for OS/390.
Before you can use DB2 Connect, your DB2 for OS/390 Administrator must configure DB2 for OS/390 to permit connections from the DB2 Connect workstation. This step highlights the minimum updates required to permit the DB2 Connect application requester to make a connection to DB2 for OS/390.
Set up DDF as an application server (i.e., update table SYSIBM.IPNAMES).
Define a VTAM LU for DB2 UDB for OS/390.
Update the BSDS data set.
Change DSNZPARM parameters for activating DDF. The DDF parameter must be set to something other than NO to have DDF work at all. The EXTSEC parameter, which defaults to NO, should be set to YES, because it will provide clients the actual reason why their connection failed due to a security violation.