SNAX/XF and SNAX/APN Event Management Programming Manual

SNAX/XF Event Messages
SNAX/XF and SNAX/APN Event Management Programming Manual426859-001
3-23
8: ZSX1-EVT-BKUP-NOTUP
ZCOM-TKN-SUBJ-SUBSYS
is the fully qualified name of the service-manager process: that is, the SUBSYS
object name, as described in Section 3 of the SNAX/XF Management Programming
Manual, qualified by the name of the system.
ZCOM-TKN-SUBJ-LINE
is the fully qualified name of the line-handler process for the line on which the event
occurred.
ZEMS-TKN-EMPHASIS
contains the value ZSPI-VAL-FALSE, indicating that this event is not a critical
event. This token is described in the EMS Manual.
ZEMS-TKN-CONSOLE-PRINT
contains the value ZSPI-VAL-TRUE. This token is described in the EMS Manual.
ZSPI-TKN-MANAGER
is the name of the service-manager process (the SUBSYS object name), as described
in Section 3 of the SNAX/XF Management Programming Manual.
ZEMS-TKN-LDEVNUMBER
identifies the logical device number. This is the 32-bit equivalent of
ZEMS-TKN-LDEV.
ZEMS-TKN-XLDEVNAME
is the string equivalent of the logical device number.
ZEMS-TKN-LDEV
is a standard EMS token described in the EMS Manual.
ZSPI-TKN-BKUP-NOTUP-CAUSE
indicates the reason why the backup process could not be started.
A token value of ZSX-VAL-BKUP-NOTUP-IOGET-ERR means that the backup
CPU number specified in the programmatic or SCF ADD DEVICE command could
not be found.
A token value of ZSX-VAL-BKUP-NOTUP-LAUNCH-ERR means that although
the backup CPU number was found, the process could not be launched because of a
system error.
ZSX1-TKN-ERRCODE
is the code for the error. If the error is generated by the line-handler or
service-manager process, the error codes can be found in the Guardian Procedure
Errors and Messages Manual. If the error is generated by a WAN shared driver, the