SNAX/XF and SNAX/APN Event Management Programming Manual

SNAX/APN Event Messages
SNAX/XF and SNAX/APN Event Management Programming Manual—426859-001
4-67
48: ZSX1-EVT-XID-FAIL
1015 0001 There were too few bytes in XID3.
1015 0002 The length specified in the Length field in XID3 was different from the
number of bytes received.
1016 0001 In the received XID3, a value of 0 was assigned to the field that specifies the
maximum number of I-frames that can be received by the XID sender before
acknowledgment.
1016 0002 The value of the activate PU (ACTPU) Suppression indicator has changed
from that sent during link activation.
1016 0003 In the received XID3, a value of less than 99 was assigned to the field that
specifies the maximum basic transmission unit (BTU) length that the sender
can receive.
1016 0004 The received XID was not XID format 3.
1016 0005 An adjacent node supports BIND segment reassembly but not BIND segment
generation.
1016 0006 The adjacent node is not a network node, does not support BIND segment
reassembly, and has a maximum BTU receive size of less than 265.
1016 0007 The adjacent node is a network node, does not support BIND segment receipt,
and has a maximum BTU receive size of less than 521.
1016 0008 The adjacent node has changed from a network node to an end node, or vice
versa.
1016 0009 The adjacent node is a network node that does not provide CP services but
supports CP-CP sessions on this TG; this is an invalid combination.
1016 000A In a nonactivation exchange, the adjacent node changed the TG number
negotiated during link activation.
1016 000B The adjacent node is the TG number negotiation winner but has selected a
number that this node cannot use for the TG.
1016 000C The adjacent node is a network node that does not support BIND segment
generation, and this node’s maximum BTU receive size is less than 521.
1016 000D The adjacent node does not support the synchronous data-link control (SDLC)
command response profile.
1016 000E Two different Product Set ID (X'10') control vectors were received from the
adjacent node.
1016 000F Link station roles were not compatible.
1016 0010 The support of ABM in sent and received negotiation-proceeding XID3s is not
compatible.
1016 0011 The adjacent node attempted to activate parallel TGs when parallel TGs were
not supported between these two nodes.
1016 0012 (Retired) The adjacent node sent the Network Name (X'0E', CP name) control
vector but did not support the Exchange State indicators.
Table 4-1. Sense Data Values for Event Message 48 (page 3 of 4)
Sense
Data Value Description