This Knowledge Base article describes the enhancement made to runtime option MCOSYS and MCOUSR by PTF SO01359.
JCLCheck Workload Automation release 12.0
JCLCheck PTF # SO01359 changes the format of the system message control option statement as follows:
Indicates the error message number. The messagenumber must be in columns 1-3.
The messagenumber must be numeric and a valid CA JCLCheck message number in the range of 001-999.
Indicates the message severity prior to MCO processing. The SEV must be in column 4.
, - Comma indicates all severities of the message should be changed to the new severity.
M indicates that messages that have been suppressed (-1) should be changed to the new severity.
I indicates that Informational messages should be changed to the new severity
W indicates that Warning messages should be changed to the new severity.
E indicates that Error messages should be changed to the new severity.
S indicates that Severe messages should be changed to the new severity.
Indicates the message severity to be used when the message is issued in JCLCheck.
The newmessageseverity must be in columns 5-6.
A newmessageseverity of -1 indicates the message is be suppressed. The newmessageseverity must be numeric and within a range of -1 through 15 as shown below:
-1 Suppress the message
00 - 03 Informational severity
04 - 07 Warning severity
08 - 11 Error severity
12 - 15 Serious error severity
The messagenumber and newmessageseverity must be separated by a comma or severity code.
An asterisk (*) in column 1 is considered a comment.
Entries can be in any sequence; duplicate entries are overwritten. Invalid entries result in an error.
Any matching entries will be modified, and unmatched entries will be added in this sequence.
added in this sequence.
When using severity codes in column 4, you can have a message number statement for each of the severity codes (M,I,W,E,S).
If a comma is used to apply to all severities, then only one statement can be specified for the message number.
For an individual message number the comma (,) cannot be used with any of other severity codes.
While processing a message, the following order of precedence is used to establish the message severity:
1. JCLMSG (out of the box or as modified by USERMOD MZ2C023)
2. JCLCheck program that issues the message
3. MCOSYS (if option specified)
4. MCOUSR (if option specified)
5. CAZ1REXX or REXX EXEC specified in the STDREXX option (if REXXMSG option is specified)
6. CAZ1XERR (if option specified; out of the box retains all messages or as modified by USERMOD MZ1C030)
When options SETPRP or CTLSCAN(IDCAMSIM) are used for IDCAMS control cards, the message severities can change after they are initially
issued. To allow better control of these altered messages, MCOSYS and MCOUSR is used a second time in these cases to allow you to change the severity of these modified messages.
Example of use:
To suppress the messages CAY6079W (warning) and CAY6079I (informational), code the control option statement as follows:
Note that the old format of 079,-1 will still work which will suppress all severity encountered for CAY6079 message.
Change to debug message CAY6425I
mcooption CHANGED MESSAGE number TO SEVERITY severity SEVCOD sevcode
The mcooption listed in the message will change the message number with the indicated sevcode to the severity listed in the message if
the message is generated. if sevcode is comma, then the change will apply to the message number no matter which severity.
None. This informational message is generated when the CAISUPT option is specified.
New message CAY6569E
MCO FILE ERROR: COMMA AND SEV CODES CANNOT BE USED FOR SAME MSG NUMBER statement
The statement listed in the message conflicts with a previously defined statement for the same message number.
A statement that has a comma in column 4 cannot be included in a MCO file that has a statement with a severity code (M, I, W, E or S) in column 4 for the same message number.
Either remove the statement for the message number that uses a comma, or remove any statements for the message number that contain
severity codes. You can have multiple statements for the message number that use severity codes.
Runtime option MCOSYS and MCOUSR are documented here: