CA JCLCheck front-ends the TSO submit command through its SUBCHEK feature. This feature allows CA JCLCheck to analyze the JCL being submitted before the JCL is sent to the internal reader. If any errors are identified, the CA JCLCheck messages are displayed at your terminal, and consequently the JCL is not submitted for processing.
There are two ways you can control SUBCHEK:
Runtime options and PROCLIBs are specified in a control file allocated to SUBCHKDD. Examples of this file, CAZ1SSUP and CAZ1SSUA, are provided in CAZ2OPTN. CAZ1SSUP shows you how to define the PROCLIB allocations and CAZ1SSUA is an example of how to set up SUBCHEK using AUTOPROC, which you do not need PROCLIB allocations.
If the control file SUBCHKDD is not allocated, SUBCHEK does not validate the JCL, but passes it directly to submit. You can use a sample CLIST, SUBCHK, in CAZ2CLS0 to allocate and de-allocate SUBCHKDD at your discretion. SUBCHK OFF de-allocates SUBCHKDD prior to invoking SUBCHEK and the JCL is not validated. SUBCHK ON allocates SUBCHKDD, causing validation of the JCL prior to submission. Tailor this CLIST to allocate the appropriate file and to allocate and de-allocate 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 contained in the source for the CAZ1JSDX module on CAZ2OPTN.
You can allocate the control file in your LOGON procedures. You can also allocate or free the control file by command or by a CLIST. A sample CLIST has been provided (SUBCHK in CAZ2CLS0), which enables you to turn SUBCHEK on or off.
Note: For information about installing the SUBCHEK feature, see the Installation Guide. For information about SUBCHEK control statements, see the Programming Guide. For information about the SUBCHEK runtime option, see the Command Reference Guide.
|
Copyright © 2013 CA.
All rights reserved.
|
|