TS/MP 2.5 Management Programming Manual

Event-Message SPI Format
Each event message in this chapter includes:
• The number and name of the event message
• A description of the event-message cause
• A syntax box listing :
The tokens associated with the message◦
◦ Unconditional and conditional tokens that have specific values for the event message.
For a description of each token, see “Event Management” (page 163).
◦ The text version of the event message.
• A description of each event-message token listed in the syntax box in the same order in which
it appears in the box
• Effect and recovery information
The syntax box contains the text version of the event message, which is available through the
EMSTEXT procedure. When you use the EMSTEXT procedure to get the text version of an event
message, you request either the display format or the console compatible format, as described in
the EMS Manual. For the ACS subsystem event messages, both the versions are identical.
Listed Tokens
Conditional tokens and unconditional tokens that are specific to an event message are included
in the message descriptions.
Tokens specific to the ACS subsystem begin with the unique subsystem identifier ZACL- (the identifier
ZACS- is used by a different subsystem).
These unconditional tokens, which can have different values for each event message, are present
in each event message generated by the PATHMON process and are individually listed in the
syntax boxes and token descriptions:
• ZEMS-TKN-EMPHASIS (ZSPI-VAL-TRUE or ZSPI-VAL-FALSE)
• ZEMS-TKN-EVENTNUMBER
• ZEMS-TKN-SUBJECT-MARK
• Subject token for ZEMS-TKN-SUBJECT-MARK
• ZEMS-TKN-EVENTCLASS
Additionally, any conditional tokens, HP internal tokens, and nested tokens that are specific to an
event message are included in the syntax boxes and token descriptions.
NOTE: With the exception of ZEMS-TKN-SUBJECT-MARK and the subject token, the order of the
tokens in the box is not necessarily the order in which they appear in the event message. The token
ZEMS-TKN-SUBJECT-MARK always immediately precedes the subject token of an event message.
Unlisted Tokens
When a token is common to all event messages, it is not included in the message descriptions in
this chapter. For a description of all tokens not listed in this chapter, see the TS/MP Management
Programming Manual.
When a token is common to all event messages but is not specific to any one event message, it is
not listed in the syntax boxes and token descriptions in this section. For a description of all tokens
not listed in this section, see Table 26 (page 167) in “Event Management” (page 163).
268 ACS Subsystem Messages