DB2 and TCPIP

Allocate TCPIP port numbers for the DRDA and RESYNC ports. Update the TCPIP profile with reservations for these numbers. This is not strictly necessary if the numbers are above 1024.

Note the TCPIP home address, from the profile.

Update the BSDS with the port numbers. (Usually done with DB2 down). PORT= for the DRDA port and RESPORT= for the RESYNC port.

Ensure that the user on the xxxxDIST job has a RACF definition for OMVS(UID(0)) and that the group has the definition OMVS(GID(n)). Note UID must be zero, whilst GID can be any number.

Add the TCPIP profile dataset to the xxxxDIST job. Also ensure the xxxxDIST job has the LE/370 runtime library in the STEPLIB.

Get the host name and address for any TCPIP hosts that will connect to this DB2. This includes other lpars and any PC’s that may be running DB2 Connect. Update the TCPIP HOSTS file with the host addresses, and run the MAKESITE utility.

Add the port numbers to the TCPIP ETC.SERVICES file, if IPNAMES (below) is to contain host names rather than host addresses.

Review the ZPARM parameters that relate to TCPIP. Initially use TCPALVER=YES to minimise problems with the first connections. It can be changed to NO later, if necessary.

Add entries to the DB2 communications database for the hosts to be defined. Entries will be required in SYSIBM.LOCATIONS and SYSIBM.IPNAMES at a minimum.

0 comments on DB2 and TCPIP

MyMusic