SNAX Connection Manager (SNAX/CM) Manual

Event-Management Programming Considerations
SNAX/CM Event Messages
A–2 097842 Tandem Computers Incorporated
36: ZSXC-EVT-CALL-ACCEPT-FAILED
37: ZSXC-EVT-NOT-IN-DATABASE
38: ZSXC-EVT-BUFFER-DEPLETION
39: ZSXC-EVT-DISABLE-FAILED
40: ZSXC-EVT-OPERATION-TIMED-OUT
41: ZSXC-EVT-ALIAS-LU-NAME-BAD
46: ZSXC-EVT-BACKUP-TAKEOVER
Event-Management
Programming
Considerations
SNAX/CM event messages are encoded as individual tokens, each containing one
piece of information about the event.
All SNAX/CM 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 displayed on the
operator console controlled by the compatibility distributor ($Z0).
The SNAX/CM subsystem does not report any events as action events (events that
require operator intervention).
Standard Tokens Certain tokens are included in every EMS event message and have values set or
defaulted to by the EMSINIT procedure, or set by the EMS collector. Instead of
repeating descriptions of these tokens for each event in this section, the tokens are
summarized in Table A-1.
Table A-1. Standard Tokens
Token Code Token Value
ZEMS-TKN-GENTIME Set by EMSINIT
ZEMS-TKN-LOGTIME Set by EMS Collector
ZEMS-TKN-SYSTEM Set by EMSINIT
ZEMS-TKN-CPU Set by EMSINIT
ZEMS-TKN-PIN Set by EMSINIT
ZEMS-TKN-CRTPID Set by EMSINIT
ZEMS-TKN-USERID Set by EMSINIT
ZEMS-TKN-CONSOLE-PRINT Defaults to FALSE
ZEMS-TKN-EMPHASIS Defaults to FALSE
ZEMS-TKN-REDUNDANT Defaults to FALSE
Potentially Critical Events Events reported by the SNAX/CM 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 device or the occurrence of an
error. Noncritical events are more mundane events, such as a line becoming ready.