SNAX/APC Configuration and Management Manual

Event Management
SNAX/APC Configuration and Management Manual—138787
E-7
Potentially Critical Events
ZAPC-EVT-INV-OP
ZAPC-EVT-INVALID-LOGON
ZAPC-EVT-LU-CONNECT-ERR
ZAPC-EVT-LU-DEVINFO-ERR
ZAPC-EVT-LU-OPEN-ERR
ZAPC-EVT-NEG-RSP-RCVD
ZAPC-EVT-NEG-RSP-SENT
ZAPC-EVT-RCVD-RU-XCEED-MAXSIZE
ZAPC-EVT-SEC-SERVER-ERR
ZAPC-EVT-SNAX-FILE-ERR
Information Events
ZAPC-EVT-BID-REJECT
ZAPC-EVT-BKP-TAKEOVER
ZAPC-EVT-INIT-INFO
ZAPC-EVT-TPREADY-REJECT
ZAPC-EVT-UNXP-PAC-RQ
ZAPC-EVT-UNKNOWN-IPC
CNOS Operation Error Events
ZAPC-EVT-CNOS-CMD-RACE
ZAPC-EVT-CNOS-CMD-REJECTED
ZAPC-EVT-CNOS-CONV-FAIL
CNOS Operation Information Events
ZAPC-EVT-RCVD-RMT-CNOS-CMD
ZAPC-EVT-CNOS-CMD-NEGOTIATED
ZAPC-EVT-SESS-LIMIT-CHANGED
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-