Installing Started Tasks
Once the ftp successfully completes, you are ready to install the selected CONNX components.
1. Log on to TSO on the target system.
Given the CONNX Server Data set prefix = CONNX.STASK, the ftp process creates a JCL/control record partitioned data set with the name and members listed in the following table:
Default Partitioned Data Set Name = CONNX.STASK.CNTL

Member | Purpose
INST | The CONNX Started Task installation job built by the CONNX installation program.
REMOVE | CONNX Started Task uninstallation job + delete steps for sample files
REMOV01 | CONNX Started Task uninstallation job - delete steps for sample files
CICSALOC | JCL procedure to allocate the SAS/C STDERR, STDOUT, and STGRPT output data sets for SAS/C runtime- and CONNX debug- error messages and SAS/C virtual memory usage reporting
CNXIDC | JCL procedure to execute IDCAMS to delete/define/load CONNX VSAM / QSAM / PDS components
CNXLINKB | JCL procedure to execute the IBM linkage editor against CONNX prelinked SAS/C 7.00 object code and create the CONNX Started Task load modules
CNXLOAD | JCL procedure to create a new load library for CONNX Started Task components
CNXPARMS | Sample control records which define SAS/C environment variables for the CONNX Started Task TCP/IP Listener and Server programs (CNXRUNB and CNXVSD0B)
CNXVSAM | JCL procedure to invoke the CONNX Started Task TCP/IP Listener/Server programs to access the CONNX VSAM and QSAM sample files
CNXVSAMJ | Execution JCL for procedure CNXVSAM
CNXVSCT | JCL procedure to invoke the CONNX Started Task TCP/IP Listener/Server programs to access the CONNX VSAM / QSAM / PDS sample files and the SCT master files
CNXVSCTJ | Execution JCL for procedure CNXVSCT
CNXVSCT1 | Same as procedure CNXVSCT, minus the CONNX sample DDNAMEs
CNXVSJ01 | Execution JCL for procedure CNXVSM01
CNXVSJ02 | Execution JCL for procedure CNXVSCT1
CNXVSM01 | Same as procedure CNXVSAM, minus the CONNX sample DDNAMEs
IDCCNX0 | IDCAMS control records to delete/define the CONNX TCP/IP server VSAM configuration file
IDCCUST0 | IDCAMS control records to delete/define/load the CONNX sample KSDS, ESDS, and RRDS customer files
IDCEQU00 | IDCAMS control records to delete/define/load the CONNX sample KSDS, ESDS, and RRDS equipment files
IDCEQU01 | IDCAMS control records to define the CONNX sample KSDS equipment file alternate index #1
IDCEQU02 | IDCAMS control records to define the CONNX sample KSDS equipment file alternate index #2
IDCEQU03 | IDCAMS control records to build the CONNX sample KSDS equipment file alternate index #1
IDCEQU04 | IDCAMS control records to build the CONNX sample KSDS equipment file alternate index #2
IDCORD00 | IDCAMS control records to delete/define/load the CONNX sample KSDS, ESDS, and RRDS order files
IDCORD01 | IDCAMS control records to define the CONNX sample KSDS order file alternate index #1
IDCORD02 | IDCAMS control records to define the CONNX sample KSDS order file alternate index #2
IDCORD03 | IDCAMS control records to build the CONNX sample KSDS order file alternate index #1
IDCORD04 | IDCAMS control records to build the CONNX sample KSDS order file alternate index #4
IDCPGRP0 | IDCAMS control records to delete/define/load the CONNX sample KSDS, ESDS, and RRDS product group files
IDCPROD0 | IDCAMS control records to delete/define/load the CONNX sample KSDS, ESDS, and RRDS product files
LNKCFGB | Linkage editor control records for load module CNXCFGB
LNKRUNB | Linkage editor control records for load module CNXRUNB
LNKVSAMB | Linkage editor control records for load module CNXVSD0B

2. Install the server component.
Edit the INST JCL and make any necessary modifications to the job card. When you have completed any JCL modifications, submit the job. This acion creates the load modules in the load library specified as well as create sample files if needed.
The return code from INST should be <= 4. If it is greater than 4, review the job output and correct any errors.
3. After successfully running the INST JCL, review the CNXPARMS file in the CNTL directory. Note the following values:
CNXRUNPORT defaults to 6500. This is the port the CONNX listener will listen on. If this port is not available on your system, change the value to a port that is available.
CNXNOPREAUTHORIZE defaults to 0. A value of 0 means the CONNX server will validate the User ID and password. If password validation is being used, the CONNX load library along with all the libraries in the STEPLIB must be APF authorized. If you do not wish to use User ID and password authentication, set this value to 1.
ALLOWMIXEDPWD defaults to 1. If your z/OS system does not have mixed case password support enabled, set this value to 0.
4. Once the parameters are set to your liking in CNXPARMS, edit the CNXVSAMJ JCL and make any necessary adjustments to the job card.
5. Submit CNXVSAMJ to start the CONNX listener.