Writing Rules › Writing Message Rules

Writing Message Rules

In message rules, include the MSGID keyword and some text identifying the message or group of messages that causes the rule to execute; the text, which causes the rule to execute, is usually the message number. For example, a rule beginning with MSGID($HASP395) executes when CA Automation Point finds a message that begins with $HASP395.

When writing rules to process messages from the VAX or VAXALL type of asynchronous consoles, you can specify the MSGID keyword and part of the message text. (For VAX messages, do not include the OPCOM header as part of the message text that CA Automation Point looks for.) For example, suppose that you want to write a rule that executes when CA Automation Point sees this message:

%%%%%%%%%%%  OPCOM 18-JUL-94 16:26:07.89  %%%%%%%%%%%
Message from user DECNET...(message_text)

In your rule, specify Message as the text that CA Automation Point should look for. Your rule might look like this:

MSGID(Message), WHEN(WORD4 EQ DECNET), OSCMD(CANCEL)

The rule executes when CA Automation Point finds a message whose first word is Message and whose fourth word is DECNET. When it sees such a message, CA Automation Point sends the write-to-operator message CANCEL to the console.

CA Automation Point also processes its own messages through the CA Automation Point rules processor, allowing you to write rules to respond to those messages. To restrict a rule to only these internal product messages, use the SESSION keyword and specify the session name of AXC.