CA JCLCheck Runtime Options › Description of Runtime Options › DEBUG

DEBUG

IBM Operating Systems – Debug Actions:

The DEBUG option causes an SVC DUMP to be taken for diagnostic analysis by CA. Use of the DEBUG option requires that CA JCLCheck be APF authorized. After the DUMP is produced, CA JCLCheck processing continues.

Non-IBM Operating Systems – Debug Actions:

The DEBUG option causes an ABEND to produce a formatted dump on the standard SYSABEND DD statement. For additional information, see ABEND codes: U1000, U2222, and U3xxx. Once the dump is produced, CA JCLCheck processing terminates.

This option has the following format:

DEBug[([error-msg-number] [occurrence-number])]|NODEbug

Default: NODEbug

error-msg-number

(Optional) Defines the number of CA JCLCheck errors. These errors are prefixed by the character string CAY6 and are defined by the JCLMSG modules, or by the user of the Job Control Standards option.

occurrence-number

(Optional) Defines how many occurrences of the specified error-msg-number should occur at the time CA JCLCheck issues an ABEND.

If you do not supply any operands, CA JCLCheck DEBUG actions are taken upon completion of CA JCLCheck processing.

If you do not specify the occurrence-number, a default value of 1 is used.

• Typically, you use this option only at the request of CA Technical Support; however, it can be useful in debugging user exit routines.
• CA JCLCheck automatically produces the same formatted dump if it encounters a program check during operation. In this case, the user-ABEND code is set to 1000.

Example: Cause a dump on the second occurrence of message 66

The following example causes CA JCLCheck to take DEBUG actions on the second occurrence of message CAY6066.

DEBUG(66 2)

Example: Cause a dump on the occurrence of message number 79

The following example causes CA JCLCheck to take DEBUG actions on the first occurrence of message CAY6079.

DEBUG(79)