From the MVS TCP/IP perspective, IOAGATE is one of its client applications. As such, IOAGATE needs a client profile data set, hlq.TCPIP.DATA, which is specified using the //SYSTCPD DD statement.

This is the main resolver configuration data set that contains information on the host name, domain origin, and so on. In addition, this data set also contains the TCPIPJOBNAME parameter that identifies the TCP/IP stack to use.

For more information on this data set, see the z/OS V1Rx Communications Server IP Configuration Reference.

When the //SYSTCPD DD statement is not specified, the standard client searches for hlq.TCPIP.DATA in the following sequence:

1. jobname.TCPIP.DATA for batch jobs and started tasks
2. SYS1.TCPPARMS(TCPDATA)
3. TCPIP.TCPIP.DATA

   Note: The default hlq distributed with TCP/IP is the string TCPIP. When found, the data set is dynamically allocated.

If the client profile data set name does not conform to the conventions described above, and as a result cannot be found using the standard search order, the data set should be allocated by the //SYSTCPD DD statement. Otherwise, the DD statement can be omitted.

The issue should be discussed and agreed upon with the local MVS/TCP system network staff.

To assign the proper SYSTCPD data set, use the TCPDATA parameter in the IOAGATE member of the PROCJCL library.

When you have specified the TCPDATA, mark this step complete.