Previous Topic: REXX Execution ExamplesNext Topic: CA JCLCheck Control Blocks


User Exits

CA JCLCheck provides exit routines to enforce installation standards, using two types of exit facilities:

CA JCLCheck uses two types of exit routines with these facilities:

CA JCLCheck invokes standard exits as a part of standard processing. You use standard exits to invoke defined events when CA JCLCheck is scanning a job (that is, the completion of validation for a JOB statement).

Note: For information about activating these exits, see the DYNEXITS parameter in the Command Reference Guide.

CA JCLCheck invokes parameter exits as a part of parameter processing. You use parameter exits when the $VTB macro defining a parameter's operand specifies an exit routine. CA JCLCheck invokes a parameter exit after syntax checking the parameter. For details about the $VTB macro.

CA JCLCheck uses varying conventions for passing values to exit routines in registers. Details are described later in this chapter.

You can code standard exits using the assembler exit facility and the COBOL user exit facility; however, you can only code parameter exits in assembler.

This chapter covers both the assembler exit routines and the COBOL User Exit facility.

Note: CA JCLCheck is REENTRANT. The CA JCLCheck entry and exit macros, GETMAIN and FREEMAIN, are a work area where you can define all data that you need to alter. Code all exits as reentrant. If they are not reentrant, link them as NORENT. If a non-reentrant program is linked as reentrant and if it is running from an authorized library, it receives a S0C4 (U1000) when it attempts to alter its own storage.

This section contains the following topics:

CA JCLCheck Control Blocks

CA JCLCheck Standard Exits in Assembler

COBOL User Exit Facility