Previous Topic: The EDCHEK Options Menu (JCK21)Next Topic: Invoking remote validation using ChekPlex


Invoking with the SUBCHEK Facility

The SUBCHEK program, an optional feature of CA JCLCheck, is installed as a front end to the IBM supplied TSO SUBMIT command processor. This feature allows CA JCLCheck to analyze the JCL in the file being submitted before the JCL is sent to the internal reader. If any errors are identified, CA JCLCheck displays messages at your terminal and does not submit the JCL for background processing. If CA JCLCheck does not detect any errors, it transfers control to the IBM SUBMIT routine for normal processing, including any SUBMIT exit routine installed on your system. CA JCLCheck displays the warning messages (severity 4 or less) and allows the submission of JCL for execution.

SUBCHEK requires you to allocate a special control statement file to the TSO user's session. This control file specifies CA JCLCheck processing options and contains file allocation information for your installation's PROCLIBs. If you do not allocate the control file, CA JCLCheck does not perform any preprocessing.

You can allocate the control file in your LOGON procedures. You can also allocate or free the control file by command or CLIST. You use a sample CLIST named SUBCHK (in the CAZ2CLS0 library) to turn SUBCHEK on and off. In this way, the installation or individual users can control the invocation of SUBCHEK.