User Exits › COBOL User Exit Facility › Defining and Storing User-Specific Data

Defining and Storing User-Specific Data

The COBOL user exit program contains the data descriptions for all information passed between the exit program and CA JCLCheck. It also includes the call to the I/O interface module. You can specify other data areas within the designated USER-WORK-AREA (defined as an 01 level at the end of WORKING STORAGE). Values of the fields in the USER-WORK-AREA are under the complete control of the COBOL exit program. You can use this area as a scratch pad data area for performing specific analysis at a single exit point. Also, this area can contain data to be saved for evaluation at later exit points.

Another method for saving statement-specific information from a JOB, EXEC, and DD statement for access by a later exit process is the use of the CA JCLCheck USERDATA feature. This feature allows you to specify the storage of up to 20 bytes of statement information during the CA JCLCheck validation of the statement. These data areas are defined in the XJB as JUSER, EUSER and DUSER fields. (You select the information for storage and completely control it through modification of the JCLTABLE.)

CA JCLCheck stores your requested information through the SAVE=common in the $VTB macro. For more information about macros, see CA JCLCheck Macros.

This 20-byte USERDATA field is part of the standard data provided by CA JCLCheck with a JOB, EXEC, or DD statement. Using this feature allows the exit program to store statement information that is not a part of the standard interface data area. The exit program is then able to obtain such data at both the specific statement exit points and as a result of an I/O request to the interface module.