Configuring Mainframe Connector for TCPaccess TCP/IP Environments
If Mainframe Connector will be running on a z/OS system that will be using TCPaccess for TCP/IP communication, additional install steps must be carried out. The default load modules created by the installation process are compatible with the IBM TCP/IP stack. The following sections will describe the steps necessary for creating a TCPaccess compatible Mainframe Connector .
If Mainframe Connector will be running with an IBM TCP/IP stack this section will not apply to your installation. Skip ahead to Other Requirements if Mainframe Connector will be running with an IBM TCP/IP stack.
Mainframe Connector TCPaccess load module dataset
A second load module dataset for Mainframe Connector should be created. The first step of the sample job of member LNKSNS in the INSTLIB install dataset creates this additional load module dataset.
Two approaches can be taken with the load module dataset that will be used for TCPaccess environments. You can decide to create this dataset to be used as a self contained Mainframe Connector load module dataset. If that is the choice, the load modules that have been created in the primary Mainframe Connector load library should be copied into this newly created load library.
If you decide to use the new dataset to contain just the module changes required for TCPaccess, you can use the TCPaccess specific load library and the original load module dataset together in a STEPLIB concatenation in your Mainframe Connector started task procedure.
Creating the Mainframe Connector TCPaccess specific load modules
Four modules need to be re-created specifically for Mainframe Connector to function in a TCPaccess environment. The four modules - PSNCDRVR, PSNCT254, PSNCLDRV, and PSNCTTOC - are created by running the LNKSNS job from the INSTLIB dataset. You will need to supply the name of your TCPaccess .LOAD dataset in the SYSLIB DD statement of this job.
The LNKSNS job will create versions of PSNCDRVR, PSNCT254, PSNCLDRV, and PSNCTTOC that will be able to function with a TCPaccess stack.
Mainframe Connector Started Task Procedure for TCPaccess
In order for Mainframe Connector to properly operate in a TCPaccess environment, the .LINK TCPaccess dataset MUST be included in the STEPLIB concatenation in your Mainframe Connector started task procedure. Member PROCSNS from the INSTLIB dataset provides a sample Mainframe Connector procedure for TCPaccess environments. Also, see SYS1.PROCLIB to review the differing requirements for the Mainframe Connector started task procedure when TCPaccess will be used.