SNAX/XF and SNAX/APN Event Management Programming Manual

SNAX/XF Event Messages
SNAX/XF and SNAX/APN Event Management Programming Manual426859-001
3-45
42: ZSX1-EVT-PU-NOT-READY
ZSX1-TKN-STA-MODE
indicates whether the line is acting as a primary or a secondary station. This token is
described in Section 4, “Common Definitions” in the SNAX/XF Management
Programming Manual.
ZSX1-TKN-PU-STATE
indicates the PU state. This token is described in Section 4 of the SNAX/XF
Management Programming Manual.
ZSX1-TKN-TEST-STATE
indicates the current PU test state. This token is described in Section 4 of the
SNAX/XF Management Programming Manual.
ZSX1-TKN-ENV-RESID
is the protocol-level ID. This token is described in Section 4 of the SNAX/XF
Management Programming Manual.
Conditional Tokens
ZSX1-TKN-BASE-ALIAS-LU
is the name of the SNAX Connection Manager (SNAX/CM) alias LU name used.
This token is described in Section 4, “Common Definitions” in the SNAX/XF
Management Programming Manual.
ZSX1-TKN-ASSOC-SUBDEV
is the name of the X25AM SU object when using SNAX/CM on multiple X.25
lines.
Cause. A failure occurred in an attempt to contact or activate a PU, or a PU was
successfully disconnected by a deactivate request. This message is generated by the
level-3 protocol.
This event message appears along with SNAX/XF event message 24, which is also
described in this section.
Effect. The PU puname is no longer available for use. The line might be operational,
but the caller is disconnected.
177 Indicates a text overrun.
400 Indicates that the PU is not stopped.
401 Indicates that the PU is not started.
Note. On switched lines, this event is generated even though the message is typically a
normal event on a switched line not requiring the attention of a console operator. If the SCF
line attribute SWOPMSG is set to OFF, this event is not generated.