SNAX/HLS Management Programming Manual

Event Message Descriptions
Event Management
104708 Tandem Computers Incorporated 8–3
Event Management
Programming
Considerations
All SNAX/HLS event messages are reported to EMS and none are reported to the
Tandem maintenance and diagnostic system (TMDS). When the standard token
ZEMS–TKN–CONSOLE–PRINT contains the value ZSPI–VAL–TRUE, messages are
also displayed on the operator console controlled by the compatibility distributor
($Z0).
The SNAX/HLS subsystem does not report any events as action events (events that
require operator intervention).
Event Management
Strategies
Event messages and their collection and interpretation, are described in detail in the
Event Management Service (EMS) Manual.
Event Message
Descriptions
On the following pages, each event message that can be issued by the SNAX/HLS
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 are always present in the event message.
Conditional tokens might be present in the event message.
Volatile tokens are subject to change from release to release.
Tandem internal tokens are 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.
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.