SNAX Connection Manager (SNAX/CM) Manual

SNAX/CM Event-Message Descriptions
SNAX/CM Event Messages
097842 Tandem Computers Incorporated A–3
To determine whether or not an event message reports a potentially critical event,
examine the value of the event-message token ZEMS-TKN-EMPHASIS:
If the value is ZSPI-VAL-TRUE, the event message reports a critical event.
If the value is ZSPI-VAL-FALSE, the event is not critical.
Format of SNAX/CM
Event Messages
Within each event-message description, a box lists all the tokens that can appear in the
event message. Header tokens are listed here, because an application can filter event
messages on header tokens as well as on other tokens.
Tokens are divided into four categories:
Unconditional tokens (tokens that are always present in the event message)
Conditional tokens (tokens that might be present in the event message)
Volatile tokens (those that are subject to change from release to release)
Tandem internal tokens (those intended for Tandem use only)
If none of the tokens in an event message fall into a particular category, that category
does not appear in the box. Because Tandem internal tokens are intended for Tandem
use only, they are not listed.
With the exception of the token ZEMS-TKN-SUBJECT-MARK and the token listed
after it, the order of the tokens in the box is not necessarily the order in which they will
actually appear in an event message. The token ZEMS-TKN-SUBJECT-MARK always
immediately precedes the subject token of an event message. For more information
about the subject token, refer to the Event Management Service (EMS) Manual.
Following the box, the event-message tokens are described in the same order in which
they appeared in the box.
The symbolic names for all SNAX/CM definitions begin with the string ZSXC-. The
names for all SNAX/CM simple tokens have the form ZSXC-TKN-name; the symbolic
name for the corresponding token number has the form ZSXC-TNM-name, where the
string name is the same in both names.
SNAX/CM Event-
Message Descriptions
The descriptions of all SNAX/CM (Connection Manager) event messages are given in
ascending order by event number; that is, in ascending order by the ZXSC-EVT-
values.