MSGID Keyword

The MSGID keyword defines the start of a message rule.

This keyword has the following format:

MSGID(characters)

characters: Identifies a message that you want CA Automation Point to process. You can specify multiple messages by specifying the portion of the message ID that indicates a specific group of messages.

Usage Note:

CA Automation Point processes MSGID rule clauses in the following order:

MSGID(), MSGID(string), MSGID(*)

Examples:

In the following example, z/OS issues message IRA201I when there is a critical shortage of auxiliary storage. The following rule highlights message IRA201I:
```
MSGID(IRA201I), HILIGHT
```
In the following example, CA Automation Point issues the following message when it cannot send keystrokes to a given session because of a workstation problem or host failure:
```
AXC0901E  Continued sendkey failures to session S008
```
The following rule dispatches a REXX procedure called CHKSESS to determine whether a workstation problem or a host problem generated message AXC0901E:
```
MSGID(AXC901E), EVERY(5 MINUTES),
  REXX(CHKSESS SESSION(&WORD7))
```
In this example, OpenVMS issues this message when a VAX printer goes offline:
```
%%%%%%%%%% OPCOM   8-APR-1994 06:10:19.32 %%%%%%%%%%
DEVICE $1$LPA0: (VAXD) IS OFFLINE
```
The following rule sounds an audible alarm when this message contains the text LP and OFFLINE:
```
MSGID(DEVICE),
  WHEN(&WORD2(4:5) EQ 'LP' AND &WORD5 EQ OFFLINE),
    ALARM(3)
```
Note: The rule shows DEVICE as the MSGID. When you write messages for OpenVMS sessions, the MSGID begins after the OPCOM header.

In this example, MSGID rule clauses are case-sensitive. For the message Please mount tape 1233, use the following:
```
MSGID(Please)
```
For the message PLEASE MOUNT TAPE 1233, use the following:
```
MSGID(PLEASE)
```