AOF Variables Available in MSG Rules

Coding Each AOF Rule Type › Message Rules › AOF Variables Available in MSG Rules

AOF Variables Available in MSG Rules

You can use all AOF variable types in MSG rules, as described in the chapter “AOF Rule Tools.” You can use the following unique AOF event variables in the )PROC section of a MSG rule, and you can manually interrogate the corresponding OPSLOG display field as an aid in debugging or implementing rule logic.

MSG.AMRF

Displays a value indicating whether the message should be retained in the Action Message Retention Facility (AMRF).

Data Type: Integer, read/write

Possible Values: 0 (do not retain this message) or 1 (retain this message)

Sample Value: 1

Usage Notes:

A message must have one of the AMRF descriptor codes in order to be considered for AMRF. See the OPSBITS OPS/REXX function for the following AMRF eligible descriptor code values: IMEDACTN, EVENACTN, CRITEVET. Unless the message has one of these descriptor codes, setting MSG.AMRF to 1 has no significant effect on the AMRF retention status of the message.
For messages originally issued with any of the AMRF descriptor codes, setting MSG.AMRF to 0 will prevent the message from being retained by AMRF, even if the descriptor codes are not changed in the AOF rule.
Suppressing or deleting a message using the AOF rule RETURN statement has no effect on the AMRF retention status of a message.

Example: The following two lines of code in a MSG rule will result in the message being retained by AMRF:

MSG.DESC = OPSBITS("IMEDACTN")
MSG.AMRF=1

OPSLOG Browse Column: Fourth bit of AFLAGS

MSG.AUTOFLAG

The NetView automation flag, taken from the WQESAUT bit flag. In addition, the WQEAUTO bit flag is also used.

Data Type: Integer, read/write

Sample Value: 1, if automation is specified

Notes:

Modifying the MSG.AUTOFLAG variable is equivalent to dynamically modifying the AUTO(YES|NO) parameter in the appropriate MPFLSTxx member of the Logical Parmlib Concatenation. For more information, see the IBM documentation.
Modifying this variable determines whether NetView processes the message. Using a rule, you can change the value of the variable to 0 (equivalent to AUTO(NO)) or non-zero (equivalent to AUTO(YES)).

OPSLOG Browse Column: The high order bit in the AFLAGS (AF) column

MSG.AUTOTOKN

The NetView automation token, taken from the WQEAUTOT flag in the WQE

Data Type: 8-byte character, read/write

Sample Value: Parm1

Notes:

Modifying the MSG.AUTOTOKN variable is equivalent to modifying the AUTO(token) parameter in the appropriate MPFLSTxx member of the Logical Parmlib Concatenation. For more information, see the IBM documentation.
Only the first 8 bytes of the modified value are passed to NetView.
If you set fewer than 8 bytes of the value, the remainder of the 8-byte field is padded with nulls.

OPSLOG Browse Column: AUTOTOKN

MSG.CMDRESPONSE

A value indicating whether the current message is a command response

Data Type: Integer, read-only

Possible Values: 0 (message is not a command response) and 1 (message is a command response)

Sample Value: 0

OPSLOG Browse Column: Third bit of AFLAGS

MSG.COLOR

The color that the message will have in OPSLOG Browse and, optionally, on the console

Data Type: 1-byte binary (unprintable), read/write (write takes effect only if the value of the PROPAGATEATTR parameter is YES)

Sample Value: '00'X

Notes:

Use the OPSCOLOR function of OPS/REXX to set the MSG.COLOR variable.
IMS messages use the colors set in IMSnCOLOR parameters.
MCS descriptor codes 1 and 11 generate red messages; code 2 generates a white message.
If multiple rules set the MSG.COLOR variable for the same message, CA OPS/MVS uses the last value set. To determine the color of each rule set, set the CA OPS/MVS RULETRACE parameter to ON. For a description of the RULETRACE parameter, see the Parameter Reference.
For messages from the generic data set interface, MSG.COLOR contains the color specified with the optional third parameter in the SUBSYS JCL keyword. If you do not specify this parameter, the variable contains the text string NONE.

OPSLOG Browse Column: COLOR

MSG.CONSNAME

The name of the console used to get messages from the subsystem interface

For messages originating in the subsystem interface, MSG.CONSNAME contains the console name.
For messages originating in the JES3 IATUX31 exit, MSG.CONSNAME contains the JES3 DSP name.
For messages originating in the generic data set interface or in the OMEGAMON interface, MSG.CONSNAME contains the report ID.

Data Type: Character, read/write

Sample Value: MSTCONS

OPSLOG Browse Column: CONSNAME

MSG.CONTROLLN

A value indicating whether the current message is a control line a multi-line message (MLWTO)

Data Type: Character, read-only

Possible Values: 0 (this is not a control line) and 1 (this is a control line)

Sample Value: 1

OPSLOG Browse Column: Fourth bit of OPSFLAGS

MSG.DATALN

A value indicating whether the current message is a data line in a multi-line message (MLWTO)

Data Type: Character, read-only

Possible Values: 0 (this is not a data line) and 1 (this is a data line)

Sample Value: 1

OPSLOG Browse Column: Sixth bit of OPSFLAGS

MSG.DATESTMP

The date when the message was issued

Data Type: Character, read-only

Sample Value: 20050908

Notes:

CA OPS/MVS sets this variable only for messages where OPSINFO("EXITTYPE") returns a value of either MVS or NIP.
The format of the date value is the same as the format for the REXX standard date function - DATE("S") - which is yyyymmdd.
This variable is related to the MSG.TIMESTMP variable in that it represents the operating system's point of view as to the date and time the message was issued. It is theoretically possible for a message issued a fraction of a second prior to midnight, for MSG.DATESTMP to return a date one day earlier than the REXX DATE("S") function in a message rule. Any such difference reflects the difference in time between when the operating system constructed the message control block and when CA OPS/MVS intercepted the message.

It is recommended that you use the REXX DATE("S") function since that date will always match the date for the message in OPSLOG Browse. MSG.DATESTMP is provided for completeness.

MSG.DESC

The descriptor codes of the message, taken from the WQEDESCD field of the WQE control block

Data Type: 2-byte binary (unprintable), read/write

Sample Value: '0400'X

Note: Use the OPSBITS function of OPS/REXX to set the MSG.DESC variable. For a description of message descriptor codes, see the IBM documentation.

OPSLOG Browse Column: ROUTE or ROUTEX

MSG.DISP

The current disposition of the message (such as SUPPRESS) as set by previously executed rules

Data Type: Integer, read-only

Sample Value: 4

Note: CA OPS/MVS sets this variable automatically after each rule processes a message; you cannot set the variable manually. The next rule always gets the highest return code set by all of the previous rules. The following list shows the correspondence between the MSG.DISP value and the AOF RETURN values:

0-NORMAL
4-SUPPRESS
8-DISPLAY
12-DELETE

OPSLOG Browse Column: DISP (This column uses descriptive character strings to display the final, highest return code.)

MSG.ENDLN

A value indicating whether the current message is the end line in a multi-line message (MLWTO)

Data Type: Character, read-only

Possible Values: 0 (this is not an end line) and 1 (this is an end line)

Sample Value: 1

OPSLOG Browse Column: Seventh bit of OPSFLAGS

MSG.FLAGS

The message type (for example, MLWTO), taken from CA OPS/MVS message flags described below

Data Type: 2-byte binary (unprintable), read-only

Example: '0010'X

Message Flags: Many of the bits represented in MSG.FLAGS are also represented by bit-specific MSG variables. We recommend using the bit-specific variables wherever possible. In all cases, the bit-specific variable takes on a value of 1 or 0 to show whether the corresponding bit is set.

'8000'X

Single line message flag.

Single-bit equivalent: MSG.SINGLELN

'4000'X

WTOR message flag.

Single-bit equivalent: MSG.WTOR

'2000'X

Multi-line message (MLWTO) flag.

Single-bit equivalent: MSG.MULTILN

'1000'X

Control line of a MLWTO flag.

Single-bit equivalent: MSG.CONTROLLN

'0800'X

Label line of a MLWTO flag.

Single-bit equivalent: MSG.LABELLN

'0400'X

Data line of a MLWTO flag.

Single-bit equivalent: MSG.DATALN

'0200'X

End line of a MLWTO flag. See note.

Single-bit equivalent: MSG.ENDLN

'0100'X

Last command output message flag (set by CA OPS/MVS to mark the last output line).

'0080'X

Urgent attention message flag; set if message has descriptor code 1 or 11 set.

Single-bit equivalent: MSG.URGENT

'0040'X

Immediate action message flag; set if message has descriptor code 2 set, or is a WTOR.

Single-bit equivalent: MSG.IMMEDACT

'0020'X

Message is from a local JES3.

'0010'X

Current message is a z/OS (WTO/SVC 35) message from a global JES3.

'0002'X

Current message is a WTL (SVC 36) rather than a WTO. CA OPS/MVS intercepts WTL messages only if its SSIWTL parameter is set to YES.

'0008'X

Current message is from an authorized task.

'0004'X

Current message was originally issued on a different system and is now being reissued on the current system.

Single-bit equivalent: MSG.REISSUE

'0001'X

MPF has suppressed the current message.

Single-bit equivalent: MSG.MPFSUPP

Note: The '0200'X bit is set for the last line of an MLWTO, and usually marks the end of output from a single command. However, HSM, JES2, and other products may issue multiple MLWTOs in response to a single command, so this bit is not a reliable indication that output has been completed.

OPSLOG Browse Column: OPSFLAGS

MSG.FULLTEXT

For message rule events from the CICS Transient Data Queue that are generated by the COF feature of the product, this variable contains up to 256 characters of the TD queue message text. If the MSG.TEXT variable is reworded, it will replace the MSG.FULLTEXT value once the message event has been fully processed by message rules. Since the maximum length of MSG.TEXT is shorter than MSG.FULLTEXT, truncation of the original message text value may occur. For all other message rule event types, this variable is the same as MSG.TEXT.

Data Type: 256 byte character, read-only

Sample Value: DFHTD0101I applid Transient Data initialization has ended.

MSG.ID

The message identifier, usually the first token or the first blank delimited word of the message text. This variable has a maximum length of 10 characters. If this token exceeds 10 characters in length, this variable contains the leftmost 10 characters of the token.

Data Type: Character, read-only

Sample Value: IEF125I

Note: The MSG.ID variable value determines which message rules execute for the current message event. This variable will never contain any special screen characters or leading or trailing blanks.

OPSLOG Browse Column: MSGID

MSG.IMMEDACT

A value indicating whether the current message is an immediate action message. An immediate action message is one that has descriptor code 2 set.

Data Type: Character, read-only

Possible Values: 0 (this is not an urgent attention message) and 1 (this is an urgent attention message)

Sample Value: 1

OPSLOG Browse Column: Tenth bit of OPSFLAGS

MSG.IMSID

The IMS ID of the associated IMS control region; or, for non-IMS messages, the value of the IMSNONE parameter (the default of the IMSNONE parameter is NONE)

Data Type: Character, read-only

Sample Value: IMSA

Notes:

The IMS ID is set for all z/OS messages that any IMS‑related address space issues; for example, messages from the IMS control and message processing regions.
The MSG.IMSID variable is available only if the IOF is licensed, installed, and active at your site (that is, the INITIMS parameter must be set to YES).

OPSLOG Browse Column: IMSID

MSG.JOBID

The identifier that JES2 or JES3 assigned to the message issuer

Data Type: Character, read-only

Sample Values: T12345 for a TSO user; J12345 for a job; S12345 for a started task; ACF2 for a started task started with SUB=MSTR. When JOBIDs greater than 100,000 are supported and activated in z/OS 1.2 and above, the above sample values will be in the format T0012345, J0012345, and S0012345.

Note: The contents of this variable depend on where the current address space was created:

If the address space was created using JES2 or JES3 and does not have a job ID, the value of the variable is a modified job identifier that begins with a character identifying the address space type: T for TSO, J for a batch job, S for a started task.
If the address space was created using the MSTR subsystem, the variable value is the first 5 characters of the job name.

This value may be different than the value returned by OPSINFO('JOBID') when used in a message rule. MSG.JOBID contains the job ID explicitly specified by the message issuer or determined by z/OS. Messages issued by JES2 in response to JES2 commands specify the job ID of the address space to which the message relates rather than the job ID of JES2. If the WQE does not contain an explicit job ID, CA OPS/MVS uses the job ID of the address space that issued the message.

OPSLOG Browse Column: JOBID

MSG.JOBLOGSUP

A value indicating whether the message should appear in the JES job log of the job that issued the message or on whose behalf the message was issued

Data Type: Integer, read/write

Possible Values: 0 (display the message in the JES job log) or 1 (suppress the message from the JES job log)

Sample Value: 1

Notes:

For example, if you use the OPSPRM function to change the severity of message OPS1000 to J, you can keep the result of SAY statements from rules out of the JES job log by setting the MSG.JOBLOGSUP variable to 1 in a message rule for OPS1000J.
The value of the MSG.JOBLOGSUP variable takes effect only if the value of the SSIMSG parameter is YES.

OPSLOG Browse Column: Sixth bit of AFLAGS

MSG.JOBNAME

The job name of the message issuer, taken from:

The WQE, for IMS or z/OS messages that are reissues of messages that originated on another system
Data areas the ASCB points to, for all other IMS and z/OS messages
The message text prefix areas, for most JES3 messages.

Note: The MSG.JOBNAME value is blank for some JES3 messages.

Data Type: Character, read-only

Sample Value: VTAM

OPSLOG Browse Column: JOBNAME

MSG.JOBNM

The name of the job associated with this line of output, taken from the WQEJOBNM field of the WQE

Data Type: Character, read-only

Sample Value: VTAM

Notes:

Set only for z/OS messages, the MSG.JOBNM variable contains the data displayed on an MCS console using the MFORM=J keyword of the Control command. For more information, see the IBM documentation.
Usually, the MSG.JOBNM value is a job name string, but is set to a job number for output from some JES2 commands. For example, MSG.JOBNM contains job numbers for each output line from the JES2 command $DA.
If the CA OPS/MVS SSIMSG parameter is set to YES at startup, JES2 does not put a job name in MSG.JOBNM because this parameter setting dictates that CA OPS/MVS receives messages before the subsystem.

OPSLOG Browse Column: JOBNM

MSG.LABELLN

A value indicating whether the current message is a label line in a multi-line message (MLWTO).

Data Type: Character, read-only

Possible Values: 0 (this is not a label line) and 1 (this is a label line)

Sample Value: 1

OPSLOG Browse Column: Fifth bit of OPSFLAGS

MSG.MCSFG

Internal z/OS, IMS, or MCS message flags, taken from:

z/OS messages-The WQEMCSF field of WQE
JES3 messages-The MSGMASK field of MESSAGE macro PLIST
IMS messages-2 flag bytes of UEHB or DFSAOE0, and the 1-byte entry code
- UEHBFLG1/UEHBFLG2 for IMS DFSAOUE0 (type 1) exit
- AOE0FLG1/AOE0FLG2 for IMS DFSAOE00 (type 2) exit
COF messages-The CICS start code.

Data Type: 3-byte binary (unprintable), read-only

Sample Value: '0E0000'X

Note: For information about WQE flags, see the IBM documentation.

OPSLOG Browse Column: FLAGS

MSG.MIC

A value indicating whether the current message is a message that was imported and reissued on this system by CA MIC.

Data Type: Character, read-only

Possible Values: 0 (message not reissued by CA MIC) and 1 (message reissued by CA MIC)

Sample Value: 1

Note: CA MIC reissued messages (even messages that are the responses that are returned to this system as a result of a cross-system command issued on this system through CA MIC), are only eligible to be processed by the AOF when the AOFMESSAGES parameter is set to MVSGLOBAL.

MSG.MLWTOMIN

If the message is a minor line of a MLWTO message, the value is 1; if the message is the major line of a MLWTO message, or the only line of a WTO message, the value of the variable is 0.

Data Type: Character, read-only

OPSLOG Browse Column: Second bit of AFLAGS

MSG.MPFSUPP

A value indicating whether the z/OS Message Processing Facility (MPF) has suppressed the current message.

Data Type: Character, read-only

Possible Values: 0 (message not suppressed by MPF) and 1 (message suppressed by MPF)

Sample Value: 1

Note: MPF processes messages before they are passed to the subsystem interface where CA OPS/MVS processes them.

OPSLOG Browse Column: 16th bit of OPSFLAGS

MSG.MSFID

The system ID of the system where the message originated, supplied by the CA OPS/MVS Multi-System Facility (MSF)

Data Type: Character, read-only

Sample Value: SYSA

Note: The MSF ID of a message is the local SYSID, for a message created on the current system. For a remote system, the MSFID is the SYSID of that system.

OPSLOG Browse Column: MSFID

MSG.MULTILN

A value indicating whether the current message is a part of a multi-line message (MLWTO).

Data Type: Character, read-only

Possible Values: 0 (this is not part of a multi-line message) and 1 (this is part of a multi-line message)

Sample Value: 1

Third bit of OPSFLAGS

MSG.OASID

The original ASID associated with the message.

When the message is issued asynchronously from the CONSOLE address space or is reissued for some reason, this value differs from OPSINFO("ASID") which represents the ASID in which the message was intercepted.

In the following cases, the value of MSG.OASID is always the same as OPSINFO("ASID"):

AOFTEST
The EXITTYPE is not MVS

Data Type: 2-byte binary (unprintable), read-only

Sample Value: '003E'X

Notes:

Use the C2X function of OPS/REXX to convert the value of this variable to hexadecimal characters.
Use MSG.ASID to determine the ASID from which a message was originally issued.

MSG.ODESC

The original descriptor codes assigned to a message

Data Type: 2-byte binary (unprintable), read-only

Sample Value: '0400'X

Note: The MSG.ODESC variable is equivalent to the Automate &DESC environmental variable.

MSG.OJOBNAME

The original job name associated with the message.

When the message is issued asynchronously from the CONSOLE address space or is reissued for some reason, this value differs from MSG.JOBNAME.

In the following cases, the value of MSG.OJOBNAME is always the same as MSG.JOBNAME:

AOFTEST
The EXITTYPE is not MVS

Data Type: Character, read-only

Sample Value: VTAM

MSG.OMAJORTEXT

The original message text. The value of MSG.OMAJORTEXT does not change from rule to rule, even if a rule rewords the message text.

Possible Values: For a WTO message, the value is the original message text; for an MLWTO message, the value is the possibly updated text from first line of the message

Data Type: Character, read-only

Notes:

The MSG.OMAJORTEXT variable is equivalent to the Automate &MSG environmental variable.
For example, if there are two MSG rules processing a message and the first MSG rule modifies MSG.TEXT, the second rule will see the changed MSG.TEXT but MSG.OMAJORTEXT will remain unchanged and contain the original text of the message. On the other hand, if a MSG rule changes the text of the first line of an MLWTO, rules for the minor lines will see the changed text in MSG.OMAJORTEXT.

MSG.OROUTE

The original routing codes assigned to a message

Data Type: 16-byte binary (unprintable), read-only

Sample Value: '100000000000000000000000000000'X

Note: The MSG.OROUTE variable is equivalent to the Automate &ROUTCDE environmental variable.

MSG.OTEXT

The complete text of a secondary line (a line other than the first or primary line) of a multi-line WTO message; this value is null for a message that is not a multi-line WTO

Data Type: Character, read-only

Note: The MSG.OTEXT variable is equivalent to the Automate &MLMSG environmental variable.

MSG.REISSUE

A value indicating whether the current message is a message that was originally issued on another system and has been transported and subsequently reissued on this system

Data Type: Character, read-only

Possible Values: 0 (this is not a reissued message) and 1 (this is a reissued message)

Sample Value: 1

Note: Messages may be reissued as a result of sysplex console processing, MSF, CA MIC, and possibly other software products. Reissued messages are only eligible to be processed by the AOF when the AOFMESSAGES parameter is set to MVSGLOBAL.

14th bit of OPSFLAGS

MSG.REPLYID

The reply number associated with a WTOR message, taken from the OREID field of the ORE

Data Type: Character, read-only

Sample Values: 01

Notes:

This variable is valid only for WTORs.
The MSG.REPLYID variable field is the size defined by RMAX in the DEFAULT statement of the appropriate CONSOLxx member of the Logical Parmlib Concatenation.

OPSLOG Browse Column: First part of the text field when the message is a WTOR

MSG.REPORTID

The report ID associated with the message. If the message comes from the generic data set interface, MSG.REPORTID contains the subsystem report ID parameter.

Data Type: Character, read-only

Sample Value: PAYLOG1

OPSLOG Browse Column: DSPNAME

MSG.ROUTE

The routing codes of the message, taken from the WQE control block

Data Type: 16-byte binary (unprintable), read/write

Sample Value: '100000000000000000000000000000'X

Notes:

Use the OPSBITS function of OPS/REXX to set this variable.

For a description of routing codes, see the IBM documentation.

OPSLOG Browse Column: ROUTE or ROUTEX

MSG.SINGLELN

A value indicating whether the current message is a single line message

Data Type: Character, read-only

Possible Values: 0 (this is not a single line message) and 1 (this is a single line message)

Sample Value: 1

OPSLOG Browse Column: First bit of OPSFLAGS

MSG.SPCHR

The message special screen character. For example, the + preceding problem CA OPS/MVS messages.

Data Type: Character, read-only

Sample Value: +

Note: This variable often is blank. For more information about special screen characters, see the IBM documentation.

OPSLOG Browse Column: SPECIAL

MSG.SUBSMOD

A value indicating whether the current message is eligible for subsystem modification. It is determined by the value of the SUBSMOD parameter specified for the WTO message.

Possible Values: 0 (message is not eligible for subsystem modification) and 1 (message is eligible for subsystem modification)

Data Type: Integer, read-only

Sample Value: 1

OPSLOG Browse Column: Fifth bit of AFLAGS

MSG.SYNA

The system name of the system issuing the message

Data Type: Character, read-only

Sample Value: MVS34

Notes:

The system name is derived from the SYSNAME parameter specified in the appropriate IEASYSxx member of the Logical Parmlib Concatenation.

For messages imported through the CA MIC product, this variable contains the name of the system from which the message originated.

OPSLOG Browse Column: SYSNAME or SYNA

MSG.SYSID

The system ID of the system where the message was issued (usually the SMF ID). For JES3 messages, the SYSID value derives from the MPNAME field of the Active Main Processor Control Table. For JES2 messages, the SYSID value derives from the SMF ID string.

Data Type: Character, read-only

Sample Value: S000

Note: The OPSLOG Browse column displays two characters of this variable, not the complete field. The CA OPS/MVS BROWSEIDFORMAT parameter determines which characters are displayed. For a description of the BROWSEIDFORMAT parameter, see the Parameter Reference.

OPSLOG Browse Column: SYSID

MSG.TERMNAME

The name of the terminal associated with the message:

For z/OS messages, the variable has the value NONE unless the message originated from a TSO address space.
For IMS messages, the variable contains the name of the IMS LTERM.
For JES3 messages, the variable contains the JES3 console name.
For COF messages, the variable contains the CICS intra-partition queue name.
For messages from the generic data set interface, the variable contains the ddname related to the subsystem data set from which the message was obtained.

Data Type: Character, read-only

Sample Value: OPSS1

OPSLOG Browse Column: TERMNAME

MSG.TEXT

The message text: for z/OS messages, taken from the WQE text field (excluding special characters and blanks); for JES3 messages, taken from a parameter list passed to the IATUX31 exit; for IMS messages, taken from the AOI exit parameter list.

Data Type: Character, read/write

Sample Value: IEF125I USERA - LOGGED ON - TIME=06.49.05

OPSLOG Browse Column: Text is always displayed.

MSG.TIMESTMP

The time when the message was issued, as it would appear on an MCS console through MFORM=T

Data Type: Character, read-only

Sample Value: 12.43.14

Notes:

CA OPS/MVS sets this variable only for messages where OPSINFO("EXITTYPE") returns a value of either MVS or NIP.
The format of the time stamp value (hh.mm.ss) is slightly different than the format for the REXX normal time function - TIME("N") - which is hh:mm::ss. The time stamp format uses a period as a delimiter, whereas the TIME function uses a colon as a delimiter.
This variable is related to the MSG.DATESTMP variable in that it represents the operating system's point of view as to the date and time the message was issued. It is possible for MSG.TIMESTMP to return a time slightly earlier than the REXX TIME("N") function in a message rule. Any such difference reflects the difference in time between when the operating system constructed the message control block and when CA OPS/MVS intercepted the message.
It is recommended that you use the REXX TIME("N") function since that time will always match the time for the message in OPSLOG Browse. MSG.TIMESTMP is provided for completeness.

OPSLOG Browse Column: TIMESTMP

MSG.TOKEN

The variable token set when the MSF receives the message and the originating system specified OPSSEND('W' ,...)

Data Type: 4-byte binary (unprintable), read-only

Sample Value: '00004C94'

Notes:

MSG.TOKEN has the same value as the MSG.WTOID variable on the originating system.
Using MSG.TOKEN, a DOM rule on the receiving system can translate the DOM.WTOID variable by comparing its value to that of MSG.TOKEN. If the DOM.WTOID and MSG.TOKEN values match, the DOM has been issued for MSG.WTOID.

OPSLOG Browse Column: TOKEN

MSG.URGENT

A value indicating whether the current message is an urgent attention message. An urgent attention message is one that has descriptor codes 1 or 11 set.

Data Type: Character, read-only

Possible Values: 0 (this is not an urgent attention message) and 1 (this is an urgent attention message)

Sample Value: 1

OPSLOG Browse Column: Ninth bit of OPSFLAGS

MSG.USER

An 8-byte variable providing communication between rules that execute for the same message event. The variable can contain any installation data that these rules need, and it can store a character string displayable through OPSLOG Browse.

Data Type: User-defined, read/write

Notes:

Before AOF processing, this variable is initialized to binary zeros. It is then passed to each rule that executes for the same message event; each rule can look at or change the variable contents before passing the variable to the next rule for the message event.
The primary purpose for the USER variable is to provide a method to pass a small amount of data between the rules. This data may be binary or mixed case. The USER field may also be used for filtering in the OPSLOG. However, USER data used for OPSLOG filtering must be uppercase and displayable.

OPSLOG Browse Column: USER

MSG.USERID

The user ID for the security product on your system. This value is usually the CA ACF2 user ID from the ACFASVT or the RACF user ID from the current ACEE. For IMS, the user ID from the CTB is valid only if IMS is generated with enhanced security.

Data Type: Character, read-only

Sample Value: TSOID01

Note: The MSG.USERID value may have the same value as the JOBNAME (which is typical for a TSO address space). These values need not match; for instance, the user IDs and the job names for batch jobs or started tasks may be different.

OPSLOG Browse Column: USERID

MSG.WTOID

The internal WTO sequence number, taken from the WQERTCT field of the WQE delimited word of the message text

Data Type: 4-byte binary (unprintable), read-only

Sample Value: '00004C94'X

Notes:

The MSG.WTOID value provides information that the OPSSEND function of OPS/REXX uses in transmitting message events to other systems.
Your system assigns sequence numbers to WTO or WTOR messages. You can use these sequence numbers to delete (using DOM) highlighted, non-scrollable messages. Use the sequence of a message as its unique token identifier, but do not use the contents of the sequence number itself.
If you want to store a WTO ID, use the C2X REXX function. To use a WTO ID, such as with the OPSDOM built-in function, use the X2C REXX function.

OPSLOG Browse Column: WTOID

MSG.WTOR

A value indicating whether the current message is a WTOR.

Data Type: Character, read-only

Possible Values: 0 (this message is not a WTOR) and 1 (this message is a WTOR)

Sample Value: 1

OPSLOG Browse Column: Second bit of OPSFLAGS

MSG.WTP

A value indicating whether the message should be WTPed. WTP stands for Write to Programmer. WTPed messages appear in the JESYSMSG data set (this is the same place that allocation messages appear and is different than the job log) of the job that issued the message or on whose behalf the message was issued. If the issuing address space is a TSO address space, a WTP message is written (TPUT) to the TSO screen.

Data Type: Integer, read/write

Possible Values: 1 (issue the WTP) or 0 (do not issue the WTP)

Sample Value: 1

For example, if you use the OPSPRM function to change the severity of message OPS1000 to J, you can keep the results of SAY statements from rules out of the JESYSMSG data set by setting the MSG.WTP variable to 0 in a message rule for OPS1000J.

By default, messages issued with a ROUTE code of 11 will have MSG.WTP set to 1.

OPSLOG Browse Column: Seventh bit of AFLAGS