ACC X.25 Protocol User's Guide

X.25 Application Programming
ZX25DBIT_ACK (3X) — ACC X.25
Chapter 4 105
Threads
Considerations
This routine may be called from a multi-threaded application using the
POSIX (1003.1c) kernel threads API package. It has the following
characteristics when called by multi-threaded applications:
cancellation point Thread cancellation can occur when a
thread calls this routine.
async-cancel unsafe The calling thread’s cancelability
type must be
PTHREAD_CANCEL_DEFERRED if
cancellation is enabled.
async-signal unsafe It cannot be called from a signal
handler.
fork unsafe It cannot be called by a child process
after fork(2) but before exec(2).
See the NOTES section that follows for more information on using this
routine in a multi-threaded application.
PAR A ME TER S : zxip ZCOM X.25 access data structure (from zx25info call).
vzap ZCOM address of the Virtual Circuit terminal.
RETURN VALUE Routine zx25dbit_ack returns a 0 when successful. If there was a ZCOM
error, it returns a negative value. See
/opt/acc/include/zcom/zcomsys.h for the list of ZCOM error codes and
their meanings. If zx25dbit_ack itself failed, one of the following
positive error codes is returned:
ZxeUNKNOWN_L2_ZLU (02) Unable to find the X.25 link ZLU for
this SVC ZLU.
ZxeREQ_TIMEOUT (04) The remote ZCOM system did not
respond within 30 seconds.
ZxeINVALID_STATE (06) The ZLU specified is not in the data
transfer state.
ZxeLINK_IS_DOWN (11) Unable to send acknowledgment to
D-bit data packet.
ZxeUNKNOWN_VC_ZLU (13) The ZLU specified is not an X.25
Virtual Circuit ZLU.