Installation Options › The SUBCHEK Feature › Controlling SUBCHEK

Controlling SUBCHEK

There are two ways to control SUBCHEK:

• You can specify the runtime options and PROCLIBs CA JCLCheck uses to validate the JCL prior to submission.
• You can specify whether SUBCHEK validates the JCL or passes it directly to SUBMIT without validation.

You specify runtime options and PROCLIBs in a control file that is allocated to SUBCHKDD. CAZ2OPTN contains examples of this file in members CAZ1SSUP and CAZ1SSUA. CAZ1SSUP shows you how to define the PROCLIB allocations and CAZ1SSUA shows you how to set up SUBCHEK using AUTOPROC. AUTOPROC does not need PROCLIB allocations.

If you do not allocate the control file SUBCHKDD, SUBCHEK does not validate the JCL, but passes it directly to SUBMIT. You can use a sample CLIST, SUBCHK, in CAZ2CLS0 to allocate and deallocate SUBCHKDD at your discretion. SUBCHK OFF deallocates SUBCHKDD prior to invoking SUBCHEK and CA JCLCheck does not validate the JCL. SUBCHK ON allocates SUBCHKDD, causing validation of the JCL before submission. Tailor this CLIST to allocate the appropriate file and to allocate and deallocate the CA TLMS CAIVMFI file, if you are using the TLMS option.

You can use the CAZ1JSDX exit to dynamically allocate SUBCHKDD if it is not allocated to the TSO session. This is useful for sites that want to force certain users to use SUBCHEK. See the comments in the source for CAZ1JSDX module on OPTION.

Note: For more information about SUBCHEK installation, see the Installation Guide.