Customization › Changing and Suppressing Message Severity Level

Changing and Suppressing Message Severity Level

The severity of the CA JCLCheck error messages can be altered or suppressed. You can do this task with the following methods:

1. Change table JCLMSG by applying a USERMOD.
2. Internally by the program which issued the error message.
3. Use the MCOSYS runtime option.
4. Use the MCOUSR runtime option.
5. Code a REXX exec.
6. Code an Assembler user error exit.

CA Technologies recommends using the runtime options MCOSYS or MCOUSR due to ease of use and quicker implementation.

The MCOSYS runtime option specifies the data set name that points to the system message control option file. The data set must be a sequential file or a PDS member with a logical record length of 80.

The following syntax is for the MCOSYS option:

MCOSYS(sequential.file.name) | MCOSYS(pds.file.name,member)

The following format is the format of the message control file:

Column    1-3     Indicates the valid CA JCLCheck WA message number from 001-999 (CAY6nnn)
Column     4      Must contain a comma
Column    5-6     Indicates the message severity
          -1      Suppress the message 
         00-03    Informational severity 
         04-07    Warning severity
         08-11    Error severity
         12-15    Serious error severity 
Column    7-80    Comments

Example:

027,04      CHANGE #27 $DMSG 'PROCEDURE','NOT FOUND'  TO SEV 4
079,-1      SUPPRESS #79 $DMSG 'DATA SET','SPECIFIED AS OLD OR SHR 

Note: If the line starts with an asterisk (*) in column 1, it is considered to be a comment.

Entries can be placed in any sequence and duplicate entries override previous entries. As a best practice, keep the message numbers in sequence to simplify locating and entry.

The MCOUSR runtime option enables you to specify the DDname of a user message control option file. The DDname must be allocated in your TSO logon proc or to your TSO/ISPF session. When running CA JCLCheck in batch mode, the DDname must also be defined in the CA JCLCheck job. The format of the MCOUSR control file is identical to the MCOSYS control file. If MCOUSR is used, MCOUSR takes precedence over the MCOSYS control file.

The following syntax is for the MCOUSR option:

MCOUSR[ddname]

The DDname is an optional parameter and if it is omitted, MCOUSR is used as the DDname:

//MCOUSR  DD  DISP=SHR,DSN=DATASET1.NAME

The sequence of processing the message control is in the following order:

1. JCLMSG is processed first.
2. The program that issued the error message.
3. The MCOSYS runtime option.
4. The MCOUSR runtime option.
5. REXX message processing.
6. Assembler user error exit (CAZ1XERR).

   This order of precedence means that the CAZ1XERR user exit is processed last.

The use of MCOSYS or MCOUSR adds flexibility and lets you quickly change the message severity.