ACC X.25 Protocol User's Guide

X.25 Status and Completion Messages
Unsolicited Status Messages
Appendix A136
sending large contiguous messages and/or using a
TTGEN configuration file with a Port-Limit parameter
that is too large. Try reducing the port limit and insure
that no applications are sending large contiguous
messages. If an application is sending a large
contiguous message, it is recommended that the
message be broken up and sent in 4,096 byte blocks
using the M-bit where appropriate.
ST25RSTRT (85) X.25 link Restart processing complete. The X.25
packet layer (level 3) is now up. Note that SVC and
PVC ZLUs can not be used until the packet layer is up.
Miscellaneous and Protocol Error Status Messages
The following unsolicited status messages are delivered only to those
applications (and the X.25 protocol driver) which have set themselves up
as receivers on the X.25 link ZLU. Note that status codes 90 through 106
pertain to specific Virtual Circuits and always have a single data byte
associated with them. This data byte contains the MUX terminal number
of the associated virtual circuit. This terminal number corresponds to the
ptterm and ltterm fields in the Physical and Logical Terminal Tables,
respectively.
ST25L2STAT (88) Level-2 statistics upload. The data buffer contains
the data structure x25l2stat_type (defined in
zcomx25.h). Note that the values in this structure are
not absolute values, but the number of occurrences of
each type of condition since the last time the statistics
were uploaded.
ST25REVCD (89) X.25 and HDLC/LAP-B firmware implementation
revision codes upload.
ST25LCENF (90) Virtual Circuit ZLU ENABLE failed. Check the
configuration for the VC ZLU. Pay particular attention
to the poll, select, and device type fields.
ST25LCERQ (91) VC ZLU enable requested. This indicates a zcntl()
request to enable the Virtual Circuit ZLU has been
issued.
ST25LCDRQ (92) VC ZLU disable requested. This indicates a zcntl()
request to disable the Virtual Circuit ZLU has been
issued.