The remainder of this chapter contains a detailed description
of each of the ACC X.25 related Application Programming Interface
routines provided with the ACC X.25 protocol accessory. Note that
these routines may not be used with ZLUs that are associated with
a port or subchannel being used by the X.25/ACC product. That is,
the J2793B X.25/9000 product.
Applications that call these routines should link with the
libraries libzx25.a and libzcom_c.a in that order, respectively.
Their location is /opt/acc/lib which
can be specified by preceding the -l option to cc or ld with "-L<dir>" as
-L/opt/acc/lib -lzx25 -lzcom_c.
Library libzx25d.a must be searched before libzcom_c.a.
 |
| |
|
 | NOTE: All "Include" files formerly under /usr/include/zcom have been relocated
to /opt/acc/include/zcom. Users
should add "-I/opt/acc/include" to their "make" files, to direct
the preprocessor to also include any files in the directory specified. |
|
| |
|
The following ZCOM API routines are provided specifically
for use with the X.25 protocol.
- x25stat
Return a ZCOM generic or X.25 status message
- zx25callacc
Acknowledge incoming call
- zx25callout
Make an outgoing call request
- zx25callrej
Clear (reject) a call
- zx25close
Clean up information data from previous zx25info
call
- zx25info
Set up information data for subsequent zx25... calls
- zx25l2stat_rcvr
Request level 2 status messages (supports shared receivers)
- zx25reset
Request a virtual circuit reset
- zx25reset_conf
Confirms an inbound VC Reset Indication
- zx25dbit_ack
Send D-bit acknowledgment (RR) for inbound data.
- zx25int_conf
Send Interrupt Confirmation for inbound interrupt data.
X.25 Manual Pages |
|
These X.25 application routines are described in detail in
the man pages that follow.
Facility Handling |
|
The ACC X.25 API routines provide a low-level interface to
the ACC X.25 subsystem. These low-level routines do not provide
any facilities checking or negotiation. All handling of facilities
data must be performed by the application, including flow control
and throughput class negotiation. Note that the X.25 subsystem will
recognize and use the correct negotiated level 3 window size and
packet size parameters.
Printable version
