When the CA JCLCheck WA SUBCHEK feature is enabled and the TSO SUBMIT command is issued, the SUBCHEK feature is called first to validate the JCL. If the JCL is validated cleanly, the JCL is submitted to the internal reader. If the JCL does not validate cleanly (non-zero return code), the JCL will not be submitted. This Knowledge Document describes the necessary steps to enable the SUBCHEK feature.
- Allocate a sequential file or PDS member to ddname SUBCHKDD. The SUBCHKDD data set contains the CA JCLCheck runtime options. If the SUBCHKDD data set is not found, CA JCLCheck WA does not validate the JCL and passes the JCL to TSO SUBMIT. An example of a SUBCHKDD file content is as follows:
SUBCHEK TSOE NOL AU
- Add the following product statement to the PARMLIB DD in your CAS9 CAIRIM job:
PRODUCT(CA JCLCHECK) VERSION(Z1B0) INIT(Z1B0INIT) PARM(SUBCHEK)
- Run CAS9 CAIRIM to initialize the SUBCHEK feature. The following will be displayed in the syslog:
CA-JCLCHECK SUBCHEK INITIALIZATION PHASE I - COMPLETE
CA-JCLCHECK SUBCHEK INITIALIZATION PHASE II - COMPLETE
CA-JCLCHECK SUBCHEK INITIALIZATION PHASE III ? COMPLETE
To disable SUBCHEK, run CAS9 with the following product statements:
PRODUCT(CA-JCLCHECK) VERSION(Z1B0) INIT(Z1B0INIT)
CA JCLCheck Workload Automation Installation guide r11 chapter 4 installation step 17:(Optional) Install SUBCHEK.
CA JCLCheck Workload Automation Programmer guide r11 chapter 2 Installation Options - The SUBCHEK feature