JCLCheck allows you to change the severity level or suppress a message using various methods. The use of the runtime option of MCOSYS and MCOUSR provides this capability without having to apply a Usermod, and is easily implemented.
Component: JCLCheck Workload Automation
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 partition data set with a logical record length of 80. Using a PDS member allows flexibility in making changes to the file to limit data set contention. Below is the syntax of the option:
MCOSYS(sequential.file.name) or MCOSYS(pds.file.name,member)
The format of the message control option file is:
Column 1-3 Indicates the numeric valid JCLCheck message number from 001-999
Column 4 must contain a comma
Column 5-6 Indicates the message severity
-1 Suppress the message
00 to 03 Informational
04 to 07 Warning
08 to 11 Error
12 to 15 Serious
Column 6-80 Comments
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 are overwritten.
The MCOUSR runtime option enables you to specify the DDNAME of a user message control option file. The DDNAME must be allocated to your logon proc or allocated to your TSO/ISPF session. When running JCLCheck in batch mode, the DDNAME must also be defined in the 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.
Here is the syntax for the MCOUSR option.
The ddname is an optional parameter and if it is omitted, MCOUSR is used as the DDNAME. This DDNAME must be allocated to your TSO/ISPF session if using EDCHEK. When running JCLCheck in batch mode, this DDNAME must be added to the JCLCheck job.
//MCOUSR DD DISP=SHR,DSN=DATASET1.NAME
The sequence of processing message control will be in the following order:
Important note: JCLCheck PTF # SO01359 adds new format to the message control statement. The format documented here is still valid, and is supported. Details about PTF SO01359 is found in the following Knowledge Base article: https://knowledge.broadcom.com/external/article?articleId=124781