Concurrent Action Processing › How to Activate Concurrent Action Processing › SCL Requirements for CAP

SCL Requirements for CAP

When batch jobs or packages are submitted for CAP processing, the SCL statements in these jobs must conform to the following requirements to process properly.

• Use explicit element names in SCL, if you plan to submit different actions in the same job.

  If you use wildcards in the element or member names, then actions against the same element may not be processed in statement order. For example, if you code the following, with the GEN following the ADD statement, the ADD may not complete before the GEN begins:

  ADD ‘*’ TO ENV ‘TESTENV’ SYSTEM ‘TESTSYS’ SUBSYSTEM ‘TESTSBS’ TYPE ‘TESTTYPE’…
  GEN ‘*’ FROM ENV ‘TESTENV’ SYSTEM ‘TESTSYS’ SUBSYSTEM ‘TESTSBS’ TYPE ‘TESTTYPE’ …
  

• You can use wildcards or masking, if you submit one action per job. For example, you can use wildcards when submitting multiple Add actions in the same job.
• Examine your SCL requests. If your job will use Concurrent Action Processing, check all ADD, UPDATE, and RETRIEVE actions ensuring that all data sets referenced by the TO FILE, TO DSNAME, TO DDNAME and FROM FILE, FROM DSNAME, and FROM DDNAME are cataloged data sets. They cannot be uncatalogued, temporary or JES2 file data sets.
• If your site uses exit 4 programs to alter input/output files prior to the execution of an ADD, UPDATE, or RETRIEVE, ensure that the data sets specified in the SCL are cataloged data sets, even if the exit 4 program changes the data set names.