Understanding Messages › Message Format

Previous Topic: Rules for Changing Message Severity

Next Topic: Message Variable Data

Message Format

CA OPS/MVS messages have the following format:

xx OPsnnnnc

The following explains the format of the messages.

xx

The reply number (only for WTOR, Write-To-Operator-with-Reply messages).

s

The last (fourth) character of the subsystem identifier of the copy of CA OPS/MVS. that is issuing the message. This is almost always the letter S (OPSS is the default value of the SSID parameter for the CA OPS/MVS JCL procedure member). For more information, see the Administration Guide.

nnnn

The message serial number.

c

The severity code for the message. The following are possible codes:

I

Informational messages. No action required.

J

Informational messages. No action required. However these messages are also sent to the AOF where they are eligible to execute MSG rules.

O

Automateable messages. No action required. However these messages are also sent to the AOF where they are eligible to execute MSG rules.

W

Warning messages. Processing continues, but some assumptions (perhaps erroneous) are made.

E

Error messages. Some product function is lost.

S

Severe error messages. The function for an entire component is lost.

U

Unrecoverable error messages. Most, if not all, product function is lost.

A

Action messages. This message is related to an associated operator reply message (WTOR) and provides information on the action(s) that the operator must take.

H

Hardcopy messages

R

Reply messages

T

Trace messages. These messages only appear in the OPSLOG.

Text

The text of the message. The message can contain fixed and variable data. Fixed data is shown in all uppercase letters. Variable data is shown in all lowercase letters.

Note: Over the next few releases we intend to change all of the CA OPS/MVS messages to mixed case text. To maintain consistency in rules you write against CA OPS/MVS messages, you must always copy and uppercase the value of the MSG.TEXT environmental variable before using it. This prevents the rules from being impacted by changes to the case of messages. For example: msgtext = TRANSLATE(MSG.TEXT)