Typically, a user exit is installed to provide additional analysis of a job stream to conform to specific installation standards. Upon detection of a violation, the exit likely issues an error message for the associated statement so that it appears on the CA JCLCheck error report. To do this, the COBOL exit program issues a special STORE ERROR MESSAGE I/O request to the CA JCLCheck Interface module.
Define the error message that you want generated to CA JCLCheck using the $DMSG macro (see the Defining Error Message to CA JCLCheck section at the beginning of this chapter). The definition of each error message includes an associated SEVERITY level, standard message text, and positional variable text. When issuing an error message, your exit should supply any variable message text with the I/O request. You can include up to five variable text units (error message parms). Each parameter is designated as alpha (maximum of 44 characters) or numeric (halfword binary). Prior to printing the error message, CA JCLCheck inserts the variable information within your message at the designated locations. When issuing an error message, it is necessary to pass a +0 to the last occurrence of JCLCEXIT-ERR-PARM-TYPE. For example, if the message includes no variable text units, this statement should be coded just before the call to JCLCXIO:
MOVE +0 TO JCLCEXIT-ERR-PARM-TYPE (1).
If the error message contains two variable text units, code this statement just prior to calling JCLCXIO:
MOVE +0 TO JCLCEXIT-ERR-PARM-TYPE (3).
This +0 marks the end of the passed parameters to CA JCLCheck. You can find an example in CAZ1XCOS, paragraph 3010-TEST-STD-PREFIX.
|
Copyright © 2014 CA.
All rights reserved.
|
|