Special Usage Considerations › OPC/ESA Support

OPC/ESA Support

The CA JCLCheck OPC/ESA interface is an established method that allows you to validate JCL used by OPC/A (Operations Planning and Control/Advanced), which is an IBM scheduling package. This interface is comprised of three procedures:

• CAZ1OPCA
• CAZ1NEAT
• CAZ1JCHK

The first procedure (CAZ1OPCA) contains five steps.

To use this interface you must have the following items available on your system:

• OPC/ESA
• The Daily Operating Plan Report
• The Plan for Workstation xxxx report (where xxxx is the CPU)
• CA JCLCheck V12.0 or higher
• The sample source library (CAI.CAZ2SAMP) that contains the source for CAZ1OPC1 and CAZ1OPC2 (two COBOL programs).

  Note: You need to change CAZ1OPC1 to identify report heading lines that are delimited by question marks (????) in the code.

• The procedure library (CAI.CAZ2PROC) that contains the procedure CAZ1OPCA, which runs the two procedures (member name CAZ1OPCA).

  CAZ1OPCA is described in more detail on the following page.

Important! There is an option within OPC/ESA that allows users to concatenate the Daily Operating Plan report and the Plan for Workstation report onto a single data set. Specify this option to ensure that the Daily Operating Plan is placed before the Plan for Workstation. This data set is used as initial input to the five-step batch job described in this section. You must also have a temporary sequential data set (See Step 4.)

The CAZ1OPCA interface batch job procedure does the following:

• Uses the Daily Plan Report and the Plan for Workstation Report for the CPU as input.
• Creates a sequential file of JCL that consists of all the jobs to run in the plan, enabling JCLNeat to replace all percent (%) symbols with the proper value for CA JCLCheck to validate the JCL being scheduled by OPC/ESA.

The following are descriptions of the steps included in the job for CAZ1OPCA:

Step 1

This step extracts information from the data set created from the Daily Plan and Plan for Workstation reports. This step creates two output files, which are delete/defined at the beginning of the job.

• The first output file (xxx.OPCESA.JCK.JCLCOPY) contains all the job names required to copy the job's JCL from the various libraries onto a temporary PDS library.
• The second file (xxx.OPCESA.JCK.JCLSCHED) contains the job names ordered as they are run (as per the Workstation report), with the corresponding application name, operation ID, input arrival date, and input arrival time.

Step 2

This step sorts xxx.OPCESA.JCK.JCLCOPY for duplicate names in preparation for the IEBCOPY in Step 3. It may be necessary to change the SORT module, the SORTLIB name and the sort commands where appropriate.

Step 3

This step uses the sorted xxx.OPCESA.JCK.JCLCOPY file to retrieve the specified members from OPC/ESA's JCL libraries and places them in a temporary library, with a ddname of PDSFILE.

Step 4

This step performs an IDCAMS REPRO of the first record in OPC/ESA's log file, xxx.OPCESA.CKPT, into a small sequential file, xxx.OPCESA.JCK.CKPT. It is necessary to create this copy file beforehand either through ISPF or some JCL in a prior step. You must create this copy file because OPC/ESA's logfile (xxx.OPCESA.CKPT) has an undefined record format, and the first record is required to determine which of OPC/ESA's two VSAM staging libraries is current during the run.

Step 5

This step uses the output file from Step 1 (xxx.OPCESA.JCK.JCLSCHED) to ascertain the order of the job dependencies. The step then copies each job's JCL from either the active OPC/ESA-VSAM file (if it exists), or from the temporary PDS library to a sequential file (xxx.OPCESA.JCK.JCLCheck). If CA JCLCheck cannot find any JCL, a warning message is issued and the job ends with a return code 4.

The CAZ1NEAT procedure runs JCLNeat using SEQIN and SEQOUT ddnames. SEQIN points to the extracted JCL data set. SEQOUT creates new JCL data sets with resolved %variables. Use the Global String Replacement feature in JCLNeat. The control card looks like:

//GSRCNTL DD *
   |%MMDDYY|REPL|
   |110895|

The CAZ1JCHK procedure is the final procedure which runs CA JCLCheck, using batch, validating the JCL for the whole Daily Plan in the sequential output file from Step 5, looking for syntax and environmental errors.