User Exits › CA JCLCheck Standard Exits in Assembler › Parameter Exit Coding Conventions

Parameter Exit Coding Conventions

Effective with r6.1 of CA JCLCheck, you can load parameter exits for the z/OS table dynamically at runtime. (Parameter exits for the Utility table, JCLUTIL, must be linked into CAZ2CJCL.) To do this, specify LOAD=YES and add the EXIT parameter as part of the $VTB macro. Loading a parameter exit dynamically allows you to link the exit as a stand-alone module rather than linking it as part of the CA JCLCheck common component.

Note: Effective with CA JCLCheck Version 11.0, CA JCLCheck internal parameter exits are invoked by the CAEXIT parameter of the $VTB. Do not use CAEXIT for user exits. Continue to use EXIT.

Use the following coding conventions for z/OS table parameter exits:

• Use the $JCLENT macro to generate initialization code required to save registers and establish a base register.
• Always use the $JCLPRTN macro to invoke a supplied exit from your own parameter exit. The format of the macro call should be label $JCLPRTN ca‑exitname. The name of your exit should always be different from that of the supplied exit for a given parameter. Otherwise, CA JCLCheck never invokes your exit. The $JCLPRTN macro automatically generates a termination code for returning from your parameter exit to CA JCLCheck.
• If you are writing an exit for a parameter that already includes a CAEXIT on the $VTB macro, use the following coding conventions for JCLUTIL exits:
• Use the $JCLENT macro to generate initialization code required to save registers and establish a base register.
  1. Modify the $VTB in JCLUTIL to point to your exit.

     Install this change using CAZ2JCL member MZ2C044.

  2. Use $JCLPRTN, without a parameter, to return control from your exit to CA JCLCheck.
  3. Use CAZ2JCL member MZ2C046 to assemble and link your exit.

See CAZ1XPAR in your CAZ2SRC library for an example of the coding conventions described here.