IPX/SPX Configuration and Management Manual

Event Messages for NonStop™ IPX/SPX
IPX/SPX Configuration and Management Manual—425731-001
B-3
Event-Message Descriptions
Refer to the SPI Programming Manual for descriptions of the ZSPI tokens and the EMS
Manual for descriptions of the ZEMS tokens.
Event-Message Descriptions
The following pages explain in detail each event message that can be issued by the
NonStop™ IPX/SPX subsystem. The descriptions appear in ascending order by event
number; that is, in ascending order by the ZIPX-EVT- values.
Each description includes a syntax box containing the tokens that NonStop™ IPX/SPX
can place in the message buffer in addition to the common data communications tokens.
Tokens appear in the box if they are not present in all NonStop™ IPX/SPX event
messages or if their values differ from one event message to another.
Tokens in NonStop™ IPX/SPX event messages are unconditional, conditional, or
NonStop™ Himalaya S-series internal. In the event-message descriptions in this section,
all tokens are unconditional unless labeled otherwise. An unconditional token is a token
that is always present in a particular event message. A conditional token is one that is
sometimes, but not always, present in a particular event message. Internal tokens are
listed in the syntax box, because your programs can encounter them when scanning the
buffer; however, they are not described, because your application programs should not
use their values. (All internal tokens are also conditional.) If an unusual event occurs,
you may need to furnish the values of internal tokens to your Compaq representative.
The ZEMS-TKN-SUBJECT-MARK token always immediately precedes the subject
token of an event message. For more information on the subject token, refer to the EMS
Manual.
The notation used for simple tokens is a shorthand version of the essential information
given in the DDL TOKEN-CODE statement.
The syntax box also contains the text version of the event message, as provided by the
EMSTEXT procedure and displayed on the operator console. For NonStop™ IPX/SPX
event messages, there is no difference between the display format and the console-
compatible format of the text. For further information on the EMSTEXT procedure,
event-message text formats, and the standard event-message header, refer to the EMS
Manual.
Following the syntax box, the event-message tokens are described in the same order in
which they appear in the box. Descriptions of simple tokens in this section do not
identify the token numbers of the tokens. However, the symbolic names of the token
numbers can be derived from the token names by simply replacing -TKN- with -TNM-.
For example, the token number of the ZSPI-TKN-EMPHASIS token is ZSPI-TNM-
EMPHASIS.
Some event messages contain error lists that report operating system errors. Although
these error lists contain operating system (ZGRD) and file system (ZFIL) tokens, the
error lists themselves are defined and created by NonStop™ IPX/SPX.