Examples

Example 1

Entries for messages in DSIMSG member DSIABC12 are as follows:

*********************************************************
120I ...
121I ...
122I &1 &2 ON THE &3
123I 10 40 THE EAGLE HAS &1
124I ...
*********************************************************

An automation procedure contains the following AOCMSG calls referencing messages ABC122 and ABC123.

<other automation procedure code>
:
AOCMSG HELP,ABC122,,IS,WAY
AOCMSG LANDED,ABC123
:
<other automation procedure code>

When AOCMSG is called as specified in the automation procedure, DSIMSG member DSIABC12 is searched for messages ABC122I and ABC123I. Variable substitution for the variables in the message entries occurs, resulting in the following messages being generated:

ABC122I HELP IS ON THE WAY
ABC123I THE EAGLE HAS LANDED

Note: Because the DSIMSG member entry for ABC122I does not specify message class information, only the issuer of the automation procedure receives the message, not any notification operators. Because the DSIMSG member entry for message ABC123I specifies message classes 10 and 40, notification operators defined to receive message classes 10 and 40 also receive message ABC123I.

Example 2

Use of the AOCMSG request_code parameter value NOMID has the following effect on the messages generated.

The same entries in DSIMSG member DSIABC12 are used.

The AOCMSG calls using the NOMID request_code parameter value are as follows:

<other automation procedure code>
:
AOCMSG HELP,ABC122,NOMID,IS,WAY
AOCMSG LANDED,ABC123,NOMID
:
<other automation procedure code>

These calls and the DSIABC12 entries result in the following messages:

HELP IS ON THE WAY
10 40 THE EAGLE HAS LANDED

Note: In message ABC123I, the message classes 10 and 40 have not been processed as message classes and appear in the message text. No notification operators receive either message. This is an error for message ABC123. The message is not implemented to use the NOMID parameter value effectively.

Use of the AOCMSG request_code parameter value MIM has the following effect on the messages generated.

The same entries in DSIMSG member DSIABC12 are used.

The AOCMSG calls using the MIM request_code are as follows:

<other automation procedure code>
:
AOCMSG HELP,ABC122,MIM,IS,WAY
AOCMSG 'HELP 40',ABC122,MIM,IS,WAY
AOCMSG LANDED,ABC123,MIM
:
<other automation procedure code>

These calls and the DSIABC12 entries result in the following three messages:

HELP IS ON THE WAY: The text HELP is considered to be the new message ID. Because no message classes are in the AOCMSG call, no notification operators receive the message.
HELP IS ON THE WAY: In this case, the value 40 is processed as a message class. This processing causes notification operators defined to receive class 40 messages to also receive this message.
10 THE EAGLE HAS LANDED: The value 40 is processed as a message class, as in previous AOCMSG examples. In contrast, the value 10 is processed as the message ID, not a message class. Message ABC123 is not implemented to effectively use the MIM parameter value.