ACC X.25 Protocol User's Guide

X.25 Status and Completion Messages
Unsolicited Status Messages
Appendix A 139
ST25SHMPK (106) Invalid short data packet received on Virtual
Circuit. This indicates a data packet was received with
the M-bit set whose length was less than the X.25 level
3 packet size for this VC. This will cause the VC to be
reset.
ST25RNRFL (107) X.25 link port break has been issued. This is used
for internal purposes.
ST25PKSHT (108) Packet too short. This will cause the VC to be reset.
ST25ILINT (109) Illegal interrupt packet. The remote system sent an
interrupt packet while there was an unconfirmed
incoming interrupt packet pending. This will cause the
VC to be reset.
Virtual Circuit Status Messages
Finally, the following X.25 specific unsolicited statuses may be received
directly from a Virtual Circuit ZLU by application programs which have
set themselves up as the receiver for that VC ZLU. Status codes 110
through 117 are always delivered to the appropriate applications. Status
codes 118 through 127 are only delivered to an application if the CNT bit
is set in the VC ZLU’s option word.
ST26INTPT (110) The VC has received an Interrupt Packet. The data
buffer contains up to 32 bytes worth of interrupt data.
ST26ICONF (111) Interrupt Confirmation packet received for this
Virtual Circuit. The remote DTE has confirmed the
Interrupt packet which was sent.
ST26LCENB (112) VC ZLU has been enabled. This indicates that the
VC ZLU is now in the enabled state. At this point, the
ZLU is available to place a call (SVC) or for
transferring data (PVC).
ST26LCTPA (113) VC ZLU has been activated. If the virtual circuit was
in a flow control state (RNR sent), then an RR has been
sent and inbound data will now be accepted by this
virtual circuit.
ST26LCUP (114) The Virtual Circuit is now in the UP state. That is, it
is available for data transfer operations. For SVCs this
status message indicates that the call setup processing
is complete. You should not attempt to send data until