ACC Error Guide

X.25 Status and Completion Messages
Introduction
Chapter 4 81
ST25PKLNG (102) VC interrupt or data packet too long. The remote
end of the link sent a data packet which exceeded the
X.25 level 3 packet size or an interrupt packet larger
than 32 bytes for 1984 X.25 or larger than 1 byte for
1980 X.25. This will cause the VC to be reset.
ST25BADQB (103) Inconsistent Q-bit usage detected in VC data
packets. This indicates the inbound data packets of a
complete packet sequence did not ALL contain the
same Q-bit value. This will cause the VC to be reset.
ST25NVGFI (104) An invalid GFI was received on the Virtual Circuit.
Most likely the modulo 128 bit was set (bit 6). The ACC
does not support modulo 128 sequence numbering. This
will cause the VC to be reset or cleared as appropriate.
ST25ILLDB (105) Illegal use of D-bit detected in packets for the VC.
This indicates a data packet was received with the
D-bit set when D-bit use has not been negotiated in the
call setup (non-1980 X.25). This will cause the VC to be
reset.
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) An X.25 level three packet was received that is too
short. This will cause the VC to be reset.
ST25ILINT (109) An illegal interrupt packet was received. 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.