CONNX Data Integration Suite 14.8.0 | Installation Guide | Installation Steps | Installing Mainframe-Compatible Server | CONNX for VSAM and QSAM | CONNX for VSAM - CICS | Installing the CONNX Components
 
Installing the CONNX Components
Installing the Selected Components on the z/OS Target
1. Log on the target z/OS system. Given the default data set prefix of CONNX.CICS, the ftp process creates a JCL control record partitioned data set with the name and members listed in the following table.
2. Edit the INST member and change the job card to match your site standards.
3. Submit this job to the batch execution queue.
Default Partitioned Data Set Name = CONNX.CICS.CNTL
Member
Purpose
INST
The CONNX and SAS/C 7.00 installation job built by the CONNX VSAM installation program.
INST02
The CONNX installation job created by the CONNX PC installation program. Submit this job to install CONNX onto a second CICS region.
REMOV0
CONNX for VSAM uninstallation JCL.
CICSALOC
JCL Procedure to allocate the SAS/C CICS transient data queues.
CICSDCT
Sample CICS Destination Control Table (DCT) source with entries for the IBM CICS TCP/IP interface and the SAS/C extra-partition transient data queues.
CICSDCTJ
Sample JCL to assemble / link-edit the CICSDCT source code into a target CICS load library.
CNXCSD
JCL procedure to execute IBM DFHCSDUP utility and define CONNX CICS components to a target RDO VSAM file.
CNXFCT0
FCT source for CONNX CICS/VSAM configuration and sample files.
CNXIDC
JCL procedure to execute IDCAMS to delete/define/load CONNX VSAM components.
CNXLINK
JCL procedure to execute the IBM linkage editor against CONNX prelinked SAS/C 7.00 object code and to create the CONNX CICS and batch load modules.
CNXLOAD
JCL procedure to delete/allocate a separate load library for the CONNX CICS programs.
CNXPPT0
PPT source for CONNX CICS/VSAM programs.
CSDFILE0
IBM DFHCSDUP utility control records to define the CONNX TCP/IP server VSAM configuration file to the target CICS RDO VSAM file.
CSDPROG0
IBM DFHCSDUP utility control records to define the CONNX CICS programs and transactions to the target CICS RDO VSAM file.
CSDSAMP0
IBM DFHCSDUP utility control records to define the CONNX CICS sample VSAM files, paths, and alternate indexes to the target CICS RDO VSAM file.
IDCCNX0
IDCAMS control records to drop the CONNX TCP/IP server VSAM configuration file.
IDCCUST0
IDCAMS control records to delete/define/load the CONNX sample VSAM customer file.
IDCEQU00
IDCAMS control records to delete/define/load the CONNX sample VSAM equipment file.
IDCEQU01
IDCAMS control records to define the CONNX sample VSAM equipment file alternate index #1.
IDCEQU02
IDCAMS control records to define the CONNX sample VSAM equipment file alternate index #2.
IDCEQU03
IDCAMS control records to build the CONNX sample VSAM equipment file alternate index #1.
IDCEQU04
IDCAMS control records to build the CONNX sample VSAM equipment file alternate index #2.
IDCORD00
IDCAMS control records to delete/define/load the CONNX sample VSAM order file.
IDCORD01
IDCAMS control records to define the CONNX sample VSAM order file alternate index #1.
IDCORD02
IDCAMS control records to define the CONNX sample VSAM order file alternate index #2.
IDCORD03
IDCAMS control records to build the CONNX sample VSAM order file alternate index #1.
IDCORD04
IDCAMS control records to build the CONNX sample VSAM order file alternate index #2.
IDCPGRP0
IDCAMS control records to delete/define/load the CONNX sample VSAM product group file.
IDCPROD0
IDCAMS control records to delete/define/load the CONNX sample VSAM product file.
LNKCFG
IBM linkage editor control records for CONNX CICS load module CNXCFG.
LNKRUN
IBM linkage editor control records for CONNX CICS load module CNXRUN.
LNKSTOP
IBM linkage editor control records for CONNX load module CNXSTOP.
LNKVSAM
IBM linkage editor control records for CONNX CICS load module CNXVSD0.
If you requested that a new CONNX load library be created by specifying a new PDS name in the Target Load Library text box of the installation program, then the example CONNX CICS load library is allocated. In both cases, the CONNX load module members are linked into the Target Load Library PDS:
CONNX.CICS.LOAD
CNXCFG
CNXRUN
CNXVSD0
CNXSTOP
After the required CONNX CICS components are installed, they must be defined to the target CICS region. The CONNX installation automates the definition of CONNX CICS programs, files, and transactions to the target region RDO file. Depending on the CICS version and release installed on the target region, optional manual steps include updating the DCT (Destination Control Table), the PPT (Program Processing Table), and PCT (Program Control Table). If the CONNX load modules were linked into a new load library, then the final required manual step is to add the CONNX load library (default name = CONNX.CICS.LOAD) to the target CICS region startup JCL DFHRPL (Run Program List) DDNAME.