Install Connect CDC (SQData) using JCL - connect_cdc_sqdata - aws_mainframe_modernization_service - Latest

AWS Mainframe Modernization Data Replication for IBM z/OS
Product type
Software
Portfolio
Integrate
Product family
Connect
Product
AWS Mainframe Modernization > AWS Mainframe Modernization Service
Version
Latest
ft:locale
en-US
Product name
AWS Mainframe Modernization
ft:title
AWS Mainframe Modernization Data Replication for IBM z/OS
Copyright
2025
First publish date
2000
ft:lastEdition
2025-02-10
ft:lastPublication
2025-02-10T15:55:15.122000
  1. Allocate the CNTL (JCL) Library

    Allocate a z/OS partitioned dataset, SQDATA.V4nnnn.CNTL to store the JCL using the following attributes. We recommend naming installation libraries with the full ver/rel/build, i.e. V40031. Production libraries are often named with only the ver/rel, ie V400 to minimize the impact of upgrades on existing JCL, Procs, Parms, etc.

    Attributes Value
    Organization PO
    Directory Blocks 50
    Record Format FB
    Record Length 80
    Block Size 21200
    1st Extent Blocks 100
    2nd Extent Blocks 50
  2. Unterse the Distribution CNTL file

    Using the following JCL as an example, unterse the distribution CNTL file into the newly created SQDATA.V4nnnn.CNTL library.

    //UNTERSE EXEC PGM=AMATERSE,PARM='UNPACK' 
//SYSPRINT DD SYSOUT=* 
//SYSUT1 DD DISP=SHR,DSN=SQDATA.V4nnnn.CNTL.TERSE 
//SYSUT2 DD DISP=SHR,DSN SQDATA.V4nnnn.CNTL
  3. Create System Libraries

    Edit CNTL member ALLOCDS, set the dataset names for your environment and submit to create the SQDATA system libraries. The return code from this job should be 0.

  4. Unterse the System Library Members

    Using CNTL member UNTERLIB, unterse the distribution library members into their respective libraries as illustrated in the following table.

    File name Description Target z/OS Library
    SQDATA.ZOS.V4nnnn.DBRMLIB.TERSE DB2 DBRM SQDATA.V4nnnnn.DBRMLIB
    SQDATA.ZOS.V4nnnn.ISPFLIB.TERSE ISPFLIB members SQDATA.V4nnnnn.ISPFLIB
    SQDATA.ZOS.V4nnnn.PARMLIB.TERSE PARMLIB members SQDATA.V4nnnnn.PARMLIB
    SQDATA.ZOS.V4nnnn.PGMOBJ.TERSE Object modules SQDATA.V4nnnnn.PGMOBJ
    SQDATA.ZOS.V4nnnn.PROCLIB.TERSE PROCLIB members SQDATA.V4nnnnn.PROCLIB
    SQDATA.ZOS.V4nnnn.SAMPLIB.TERSE Samples SQDATA.V4nnnnn.SAMPLIB
  5. Prepare to Link the Load Modules

    Edit the SQDLINK procedure in the SQDATA PROCLIB to specify the required system dataset names (i.e. Language Environment, IMS, CICS, Db2, etc.). The SQDLINK procedure contains instructions on the necessary modifications.

  6. Link the Load Modules

    Edit the SQDLINK JCL in the CNTL library to set the dataset names and submit the job. The return code from this job should be 0.

    Requirements for Linking will vary depending on both the type of Capture to be used and other environmental factors. Review the Implementation checklists and environment preparation steps for each type of capture to be deployed. Beginning with SQDLINKA, edit the JCL member(s) in the CNTL library to set the dataset names and submit the jobs. The return codes from each Job must be 0.

  7. APF Authorize the Load Library
    Important: The SQD LOADLIB must be APF authorized. Initially, this can be done via the operator’s console via the SETPROG APF command.
    The list of currently APF authorized files can be viewed using the z/OS ISPF/SDSF facility. First, enter "/D PROG, APF" at the SDSF command prompt to generate the list. Next, enter "LOG" at the SDSF command prompt, scroll to the bottom of the log to display the results of the previous command and then back up and to the right to view the complete listing of the command.
    Note: Make sure that the APF authorization is made a permanent part of the IPL APF authorization procedure prior to attempting to run SQData.
  8. Other z/OS Security Requirements

    While some security authorization requirements are specific to the types of source datastores to be captured, other requirements apply to all components.