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-68
48: ZSX1-EVT-XID-FAIL
1016 0013 The data-link control (DLC) Type field in the sent and received
negotiation-proceeding XID3s were not the same.
1016 0014 The adjacent NRM link station sent an XID3 indicating it contained a
negotiable link station after having indicated it contained a link station with a
nonnegotiable role.
1016 0015 The adjacent node supports adaptive BIND pacing as a sender but not as a
receiver.
1016 0016 The local node attempted to activate a TG with a predefined number, but the
adjacent node attempted to use a nonzero number that was different from the
one the local node used to represent the TG.
1016 0017 After two negotiation-proceeding XID exchanges, two negotiable link stations
still had equal values in the Node Identification fields of their XID3s.
1016 0018 The adjacent node is an advanced peer-to-peer networking (APPN) node, but
does not support adaptive BIND pacing as a sender and receiver.
1016 001A On two different TGs, the adjacent node was inconsistent in its support of
parallel TGs.
1016 001B The adjacent node provides or requests CP services but does not support
CP-CP sessions on this TG.
1016 001C The adjacent node sent a reserved value in the XID3 field defining its link
station role.
1016 001D The adjacent node has only two-way alternation transmit-receive capability,
but this node supports only two-way simultaneous.
1016 001E The adjacent node does not include the Network Name (X'0E', CP name)
control vector in its XID3 but indicates support of CP-CP sessions.
1016 0020 The value sent in the Type of the XID Sending Node in XID3 indicated a node
type with which the receiving node cannot activate a TG (that is, T2.1 nodes
cannot activate TGs with T1 nodes).
Table 4-1. Sense Data Values for Event Message 48 (page 4 of 4)
Sense
Data Value Description