SNAX/APC Management Programming Manual

Event Message Descriptions
Event Management
111813 Tandem Computers Incorporated 6–9
Event Message
Descriptions
On the following pages, each event message that can be issued by the SNAX/APC
subsystem is described in detail.
Within each event message description, there is a box that lists all the tokens that can
appear in the event message. An application can filter on any token. These tokens are
divided into four categories:
Unconditional tokens, which are always present in the event message.
Conditional tokens, which might be present in the event message.
Volatile tokens, which are subject to change from release to release.
Tandem internal tokens, which are intended for Tandem use only.
If a token in an event message does not fall into a particular category, then that token
does not appear in the box.
The order of the tokens in the box is not necessarily the order in which they 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 Event Management Service (EMS) Manual.
The box also contains the text version of the event message, which can be obtained by
using the EMSTEXT procedure. When you use EMSTEXT, you request either the
display format or the console–compatible format, as described in the Event
Management Service (EMS) Manual. In the case of most SNAX/APC event messages,
there is no difference between the two versions. The two versions are also identical to
the corresponding console message.
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 event message tokens are described in the same order in which
they appeared in the box.