SNAX/XF and SNAX/APN Event Management Programming Manual

SNAX/XF and SNAX/APN Event Management Programming Manual—426859-001
4-1
4
SNAX/APN Event Messages
The event messages that the SNAX/APN subsystem can issue (ZSX1 event messages)
are described in this section. For general information about event messages and their
collection and interpretation, refer to the EMS Manual. For information about event
messages from subsystems that use the SPI common extensions (ZCOM) tokens, refer
to the SPI Common Extensions Manual.
In this section, event-message tokens and their values are represented in the Compaq
Data Definition Language (DDL). For a brief explanation of DDL, see the appendix
about DDL in the SPI Programming Manual. First, ZCOM-EVT-IO-FATAL-ERROR is
described in relation to SNAX/APN. Then, descriptions of all ZSX1 event messages are
given in ascending order by event number: that is, in ascending order by the ZSX1-EVT-
values.
A box within each event-message description lists all the tokens, in addition to those
listed in Section 2, Standard Definitions
, that can appear in the event message. The
header tokens ZEMS-TKN-EVENTNUMBER, ZEMS-TKN-EMPHASIS, and ZEMS-
TKN-CONSOLE-PRINT, which appear in Table 2-2, are also included in the box
because their values vary depending on the message. The data-portion token ZEMS-
TKN-SUBJECT-MARK is also included to show its relationship to the subject token,
ZCOM-TKN-SUBJ-objtype.
Tokens in SNAX/APN event messages are divided into three categories:
•
Unconditional tokens, which are always present in the event message
•
Conditional tokens, which might be present in the event message
•
Compaq internal tokens, which are intended for Compaq use only
If none of the tokens in an event message fall into a particular category, that category
does not appear in the box.
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 on
the subject token, refer to the EMS Manual.
The box also 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. In the case of most SNAX/APN
event messages, there is no difference between the two versions, and the two versions
are also identical to the corresponding console message. Some SNAX/APN event
messages offer text versions only in display format.
The notation used in the box for simple tokens is a shorthand version of the essential
information given in the DDL TOKEN-CODE statement.
Following the box, the parameters in the text version of the event message are identified
in terms of tokens. Then the event-message tokens are described in the same order in