Installing CONNX for Adabas Components

Once the ftp successfully completes, you are ready to install the selected CONNX components. To begin this process, log on to TSO on the target system. Given the CONNX Server Data set prefix above = CONNX.Adabas, the ftp process creates a JCL/control record partitioned data set with the name and members listed in the following table:

Member	Purpose
INST	The CONNX for Adabas installation job built by the CONNX installation program.
REMOVE	CONNX for Adabas uninstallation job + delete steps for sample files.
REMOV01	CONNX for Adabas uninstallation job - delete steps for sample files.
CNXLINKA	JCL procedure to execute the IBM linkage editor against CONNX prelinked SAS/C 7.00 object code and create the CONNX for Adabas load modules.
CNXPARMS	Sample control records which define SAS/C environment variables for the CONNX for Adabas TCP/IP Listener and Server programs (CNXRUNA and CNXAD'X'0B) where 'X' is the version number (10=A, 11=B, 12=C, 13=D, etc).
CNXADA	JCL procedure to invoke the CONNX for Adabas TCP/IP Listener/Server programs to access the CONNX for Adabas sample files.
CNXADAJ	Execution JCL for procedure CNXADA.
LNKRUNA	Linkage editor control records for load module CNXRUNA.
LNKADAB	Linkage editor control records for load module CNXAD'X'0B, where 'X' is the version number (10=A, 11=B, 12=C, 13=D, etc).

You can edit the INST member and change the job card to match your site standards. Then, submit this job to the batch execution queue. All job steps must end with condition codes less than or equal to 4.