NetIPC 3000/XL Programmer's Reference Manual (5958-8600)

Chapter 3 77
NetIPC Intrinsics
IPCCONTROL
select facility has been used, the maximum
length is 128 bytes.
— code 145 — (X.25 only.) This option field defines
the part of the facility field to be appended to the
facility field built using the received facilities.
The maximum length of this field is 109 bytes.
This buffer has to follow the X.25
recommendation and is appended to the facility
field built based on the information contained in
the call request.
• 10 = Send a reset packet (X.25 only.) This request
is valid only over connection sockets. The
wrtdata
parameter (2 bytes) can contain the cause (byte 1)
and diagnostic (byte 2) fields to be included in the
reset packet sent by the X.25 protocol. The cause
field may be overwritten by the PDN. If configured
as a DTE, the cause will always be 0, irrespective of
the value entered. Suggested value for the cause
field is 0 (zero), DTE originated. No
readdata is
associated with this request.
• 11 = Send an interrupt packet (X.25 only.) This
request is valid only over connection sockets. The
wrtdata parameter can contain from 1 to 32 bytes
of user data that will be inserted in the interrupt
packet sent by the X.25 protocol.
• 12 = Reason for error or event (X.25 only.) This
request returns the reason for the NetIPC error or
event on an X.25 connection in the
readdata
parameter. The first byte of readdata contains the
type of packet that caused the error or the
unsolicited even (Clear, Reset, Interrupt). The
second byte contains the length of the clear user
data field or the length of the interrupt data field.
The third and fourth bytes contain the cause and
diagnostic fields.
Beginning with byte 5 there can be either clear user
data or interrupt data. There can be up to 128 bytes
of clear user data if the type of packet is clear and if
the fast select facility was used at the beginning of
the communication. There can be up to 32 bytes of
interrupt data if the type of packet is interrupt.
This request is valid only over an X.25 connection
socket after a communications line error has
occurred. Possible cause and diagnostic codes
generated by X.25 are listed in Appendix B , “Cause
and Diagnostic Codes.”