NAME
zx25send_int - Send Interrupt data on a Virtual Circuit
SYNOPSIS
#include <zcom/zcomsys.h>
#include <zcom/zcomx25.h>
int zx25send_int (zxip, vzap, ibuf, len)
zx25info_type *zxip;
zaddr_type *vzap;
char *ibuf;
int len;
DESCRIPTION
Routine zx25send_int requests
that an Interrupt packet be sent on a Virtual Circuit. This function
should only be called if the Virtual Circuit has already been setup.
If the Link is configured for 1980 operations, you can send only
1 byte of data. If the LINK is configured for 1984 operations, you
can send up to 32 bytes of data. You are not allowed to send another
Interrupt packet until you receive an Interrupt Confirmation OR the Confirmation
times out.
The libraries libzx25.a, libzcom_c.a, and libpthread.a must
be linked into the calling program by giving the "-lzx25
-lzcom_c -lpthread" options to cc(1) or ld(1).
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.
PARAMETERS:
- zxip
ZCOM X.25 access data structure (from zx25info call).
- vzap
ZCOM address of the Virtual Circuit terminal.
- ibuf
Buffer to send (character array).
- len
Length in Bytes to be sent
RETURN VALUE
Routine zx25send_int 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 zx25int_conf 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.
- ZxeINVALID_STATE (06)
The ZLU specified is not in the data transfer state.
- ZxeLINK_IS_DOWN (11)
The X.25 link is down. Unable to send acknowledgment
to D-bit data packet.
- ZxeUNKNOWN_VC_ZLU (13)
The ZLU specified is not an X.25 Virtual Circuit
ZLU.
- ZxeMUST_CALL_ZX25INFO
(17)
The zx25info() routine
has not been called. You must call zx25info before issuing
any other zx25...() calls.
- ZxeBAD_ZX25INFO_ADDR
(18)
The pointer to the zx25info_type structure does
not contain the same address that was passed to the zx25info() routine.
- ZxeX25_NOT_INITIALIZED
(98)
The ACC X.25 subsystem has not been initialized.
You must run zx25d_init before
issuing any zx25...() calls.
- ZxeX25_TBL_FULL (99)
The X.25 routines maintain an internal table for
accessing remote ZCOM nodes. This table has room to access up to
20 different ZCOM nodes (including the local node). This request
attempted to access the 21st ZCOM remote node and the internal table
used had insufficient space to save the routing data.
NOTES
The calling program (or thread) must call zx25info before calling this routine.
In a multi-threaded application, each thread must make a separate
call to zx25info using a per-thread
ZCOM X.25 access data buffer zxip.
The per-thread data buffer can then be used to call this routine.
EXAMPLE
#include <zcom/zcomsys.h>
#include <zcom/zcomx25.h>
int ierr;
zx25info_type *zxi;
zaddr_type *vzaddr;
char ibuf[32]
int len;
if (ierr = zx25send_int (zxi, vzaddr, ibuf, len))) {
/* error return code */
}
else {
/* good return code */
}
FILES
- /opt/acc/include/zcom/zcomsys.h
ZCOM system general include file, containing data
types, data structures, constants, error codes, masks, etc. Note
that this must be the first include file before any other ZCOM include
files.
- /opt/acc/include/zcom/zcomx25.h
ZCOM X.25 access data structure declarations.
SEE ALSO
zx25info(3x), zx25int_conf(3x)
Printable version
