SNAX/APC Management Programming Manual

Potentially Critical Events
Event Management
6–8 111813 Tandem Computers Incorporated
Potentially Critical
Events
Events reported by the SNAX/APC subsystem are divided into two classes:
potentially critical events and noncritical events. Potentially critical events are those
for which the consequences could be serious, such as the loss of a session or the
termination of the SNAX/APC process. Noncritical events are less serious events that
are likely handled by well–written application programs, such as the sending or
receiving of a negative response.
To determine whether 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 potentially critical event. If the value is
ZSPI–VAL–FALSE, the event is not critical.
Event Management
Programming
Considerations
All SNAX/APC event messages are reported to EMS; 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). However, the SNAX/APC message file may be used to inhibit the display of
messages on the operator console. (Refer to the SNAX/APC Planning and Configuration
Manual for more information about inhibiting message displays.)
The SNAX/APC subsystem does not report any events as action events (events that
require operator intervention).
Event messages, their collection, and their interpretation are described in detail in the
Event Management Service (EMS) Manual.