Install Connect CDC (SQData) using ISPF Installer - aws_mainframe_modernization_service - Latest

1. Execute the installer using the ISPFLIB data set and one of the following methods:
   • Edit the ISPFLIB data set listed in ISPF option 3.4 (DSLIST), locate the SSLSETUPmember, type ex next to SSLSETUP, then press Enter.
   • From an ISPF command line, enter: TSOEX 'SQDATA.V4nnnn.ISPFLIB(SSLSETUP)'

The Installer Main Menu

The AWS Mainframe Modernization Installer main menu displays the steps required to unload the product libraries and prepare SQDATA to run in your environment.

1. Unpack the AWS Mainframe Modernization distribution data sets
2. Link the AWS Mainframe Modernization load modules
3. Bind the AWS Mainframe Modernization DB2 package

1. Tab to the Unterse distribution data sets option.
2. Type s and press Enter.
3. Confirm the names of the input and output data sets. Input data sets are the product distribution libraries in Terse format. They will be unpacked into the output data sets shown on the panel.
   
   

At this point a job is built with all names and file sizes, etc., and is prepared for submission. This will define each output file and execute the terse steps. You should review and verify that the generated JCL and parameters are correct.

1. Tab to the Link Connect CDC SQData load modules option.
2. Type s and press Enter.
   
   
   
   Note:

   • The data set names displayed are referenced in subsequent installation jobs.

   • The system data set names displayed on this panel are generic and may not be correct for your environment. Therefore, you should change the name to suit your system requirements.

   • The files in the first group are mandatory.

   • The second group of files are optional, depending on the features that you plan to use. If for example, the current site only has DB2, then you can erase the CICS and IMS file name and only DB2 will be linked.

At this point, a job is built to link all of the Load Modules. Review and verify that the generated JCL and parameters are correct.

1. Tab to the Bind CDC DB2 package option.
2. Type s and press Enter.
   
   
   
   Note:

   • Specify the name of the data set that contains the DBRM modules (DB2 Database Request Module).

   • Specify the subsystem ID and load library of the DB2 to Bind the CDC DB2 package to.

   • The permissions required by the Bind Job may require intervention.
3. Press Enter to continue.

   At this point a job is built to Bind the Db2 Package. You should review and verify that the generated JCL and parameters are correct.

4. Type SUBMIT on the command line and press ENTER to run the job, confirm that it was successful before continuing.

1. Tab to the Create UNIX directories option, type s and press Enter.
   • Specify the starting path name and permission mask for the SQDATA UNIX files and directories. The maximum length of the starting path name is 56 characters.
   • The permission mask consists of three octal digits to define owner, group, and world access.
     
     
     
     Note: You may want to confirm the User_ID to be used for execution of the product.
2. Press Enter to continue.

   At this point, a job is built to create the OMVS directory structure. You should review and verify that the generated JCL and parameters are correct.

3. Type SUBMIT on the command line and press ENTER to run the job, confirm that it was successful before continuing.

1. Tab to the Create Daemon Agents and ACL files option, type sand press Enter.

   If the UNIX directory path and file permission were provided on the Create UNIX File System Directories panel, that information will be used again for the Create Daemon Agents and ACL files option.

   However, if you skip the Create UNIX directories option and proceed directly to the CreateDaemon Agents and ACL files option, which you might do if the UNIX directories already exist, you will be prompted for that information on the same Create File System Directories panel used for UNIX directories.

   
   
   
2. Press Enter to continue.

   At this point, a job is built to create the OMVS directory structure. You should review and verify that the generated JCL and parameters are correct.

3. Type SUBMIT on the command line and press ENTERto run the job, confirm that it was successful before continuing.

The final two options on the main menu generate SAMPLE jobs to review with your systems and security staff. Resource planning, additional customization, and special authorization is usually required to complete these steps.

Create Started Task and Admin Userids

This panel collects information used to generate a sample RACF command job to define userids for a capture task, a daemon, and a product administrator. It is not intended to be submitted as-is and must be modified to conform to your security environment.

Security requirements should be discussed with your RACF administrator. The sample definitions generated in this step can help to facilitate that discussion.

1. Press Enter to continue.
2. A job is built to create the OMVS directory structure. Review and verify that the generated JCL and parameters are correct.
3. Make a note of the Member created ISPFLIB(SSLJRACF)because you may not have adequate permissions to run this job, which is required before you will be able to execute a Capture

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.

Make sure that the APF authorization is made a permanent part of the IPL APF authorization procedure prior to attempting to run Connect CDC (SQData).