xti.3.man

This a separate release of the OpenSS7 X/Open XTI/TLI library, TLI modules (timod, tirdwr) and the I

If and when the amount of accumulated receive data exceeds the low-water
mark, a T_DATA event is created, an event mechansm (for example,
.BR poll "(2) or " select (2))
indicates the data, and the data can be read by
.BR t_rcv "(3) or " t_rcvudata (3).
.RS
.PP
This option is formatted as a
.BR t_uscalar_t .
This request is not an
.IR "absolute requirement" .
The implementation may place upper and lower limits on the option value.
Requests that fall short of the lower limit are negotiated to the lower limit.
Legal values are all positive numbers.
.PP
This option can be negotiated in any XTI/TLI state; however, the negotiated value
will not be effective until the
.B T_DATAXFER
state is acheived.  This option can be negotiated using the
.BR t_optmgmt "(3), " t_connect "(3) or " t_accept (3)
XTI/TLI library calls.
.RE
.\"
.TP
.B XTI_SNDBUF
This option is used to adjust the internal buffer size allocated for the
send buffer.
.RS
.PP
This option is formatted as a
.BR t_uscalar_t .
This request is not an
.IR "absolute requirement" .
The implementation may place upper and lower limits on the option value.
Requests that fall short of the lower limit are negotiated to the lower limit.
Legal values are all positive numbers.
.PP
This option can be negotiated in any XTI/TLI state; however, the negotiated value
will not be effective until the
.B T_DATAXFER
state is acheived.  This option can be negotiated using the
.BR t_optmgmt "(3), " t_connect "(3) or " t_accept (3)
XTI/TLI library calls.
.RE
.\"
.TP
.B XTI_SNDLOWAT
This option is used to set a low-water mark in the send buffer.  The
option value gives the minimal number of bytes that must have accumulated
in the send buffer before they are sent.
.RS
.PP
This option is formatted as a
.BR t_uscalar_t .
This request is not an
.IR "absolute requirement" .
The implementation may place upper and lower limits on the option value.
Requests that fall short of the lower limit are negotiated to the lower limit.
Legal values are all positive numbers.
.PP
This option can be negotiated in any XTI/TLI state; however, the negotiated value
will not be effective until the
.B T_DATAXFER
state is acheived.  This option can be negotiated using the
.BR t_optmgmt "(3), " t_connect "(3) or " t_accept (3)
XTI/TLI library calls.
.RE
.\"
.\"
.SH FUNCTIONS
.PP
.\"
.\"
.SS "Local Transport Endpoint Management"
.HP
.B Local Endpoint Management
functions are applicable to all transport service provider service types and
include functions to open and close a file descriptor associated, bind and
unbind a file descriptor from a local transport endpoint, manage options and
get information about the state, bound and connecting addresses, protocol
parameter limits of a local transport endpoint.
.RS
.sp
.BR t_open "(3) - open an endpoint"
.br
.BR t_close "(3) - close an endpoint"
.br
.BR t_bind "(3) - bind to an address"
.br
.BR t_unbind "(3) - unbind from an address"
.br
.BR t_optmgmt "(3) - manage options"
.br
.BR t_getinfo "(3) - return protocol information"
.br
.BR t_getprotaddr "(3) - get protocol addresses"
.br
.BR t_getstate "(3) - return the current state"
.RE
.HP
.B Local Event Management
functions are responsible for handling asynchronous events of the underlying
transport service provider and resynchronizing the XTI/TLI library with the
underlying transport service provider.
.RS
.sp
.BR t_sync "(3) - synchronize library with provider"
.br
.BR t_look "(3) - look at the current event"
.RE
.\"
.\"
.SS "Connection Oriented Endpoints"
A set of XTI/TLI Library calls are provided for performing protocol functions on
local transport endpoints for which the transport service provider is of a
connection oriented service type.  Connection oriented services have three
phases as follows:
.HP
.B Connection Establishement Phase
consists of either invoking outgoing connections or listening for and
accepting incoming connections.  Valid states for this phase are:
.BR T_IDLE ", " T_INCON ", and " T_OUTCON .
XTI/TLI Library calls used in the Connection Establishment Phare are as follows:
.RS
.sp
.BR t_listen "(3) - get a connection request"
.br
.BR t_accept "(3) - accept a connection request"
.br
.BR t_connect "(3) - establish a connection"
.br
.BR t_rcvconnect "(3) - receive connect request confirmation"
.br
.BR t_addleaf "(3) - add a point to a point to multipoint connection"
.br
.BR t_removeleaf "(3) - remove point from point to multipoint connection"
.br
.BR t_rcvleafchange "(3) - receive point added to point to multipoint connection"
.RE

.HP
.B Data Transfer Phase
consist of transfering data between connected transport endpoints.  Valid
states for this phase are:
.BR T_DATAXFER ", " T_OUTREL
(for incoming data) and
.BR T_INREL
(for outgoing data).
XTI/TLI Library calls used in the Data Transfer Phare are as follows:
.RS
.sp
.BR t_snd "(3) - send data"
.br
.BR t_sndv "(3) - gather and send data"
.br
.BR t_rcv "(3) - receive data"
.br
.BR t_rcvv "(3) - receive data and scatter"
.RE

.HP
.B Connection Release Phase
consists of either abortive or orderly release of the transport connection,
with or without user data.  Valid states for this phase are:
.BR T_DATAXFER ", " T_OUTREL ", and " T_INREL .
XTI/TLI Library calls used in the Connection Release Phare are as follows:
.RS
.sp
.BR t_rcvdis "(3) - receive abortive disconnect"
.br
.BR t_snddis "(3) - send abortive disconnect request"
.br
.BR t_rcvrel "(3) - acknowledge orderly release request"
.br
.BR t_sndrel "(3) - send orderly release request"
.br
.BR t_rcvreldata "(3) - acknowledge orderly release request with data"
.br
.BR t_sndreldata "(3) - send orderly release request with data"
.RE
.\"
.\"
.SS "Connectionless Endpoints"
A set of XTI/TLI Library calls are provided for performing protocol functions on
local transport endpoints for which the transport service provider is of a
connectionless service type.  Connectionless service has one phase as follows:
.HP
.B Data Transfer Phase
consists of transferring data between disconnected transport endpoints.  Valid
states for this phase are:
.BR T_IDLE .
XTI/TLI Library calls used in the Data Transfer Phase are as follows:
.RS
.sp
.BR t_rcvudata "(3) - receive unitdata"
.br
.BR t_rcvvudata "(3) - receive unitdata and scatter"
.br
.BR t_sndudata "(3) - send unitdata"
.br
.BR t_sndvudata "(3) - gather and send unitdata"
.RE
.\"
.\"
.SS "XTI/TLI Library functions"
A set of XTI/TLI Library calls are provided for error handling and utility.
These functions do not operate directly on a transport endpoint.
.HP
.B Error Handling
consists of the global external variable
.I t_errno
which holds all XTI/TLI Library call error numbers in a similar fashion to
.BR errno (3).
The following Error Handling functions are provided:
.RS
.sp
.BR t_errno "(3) - error number"
.br
.BR t_error "(3) - print an error message"
.br
.BR t_strerror "(3) - describe an XTI/TLI library error"
.RE

.HP
.B Utility Functions
provide for the allocation and deallocation of XTI/TLI library datastructures, and
equiry concerning XTI/TLI system confiruation parameters.
The following Utility Functions are provided:
.RS
.sp
.BR t_alloc "(3) - allocate a library structure"
.br
.BR t_free "(3) - free a library structure"
.br
.BR t_sysconf "(3) - configure XTI/TLI system parameters"
.RE
.\"
.\"
.SH "RETURN VALUES"
.PP
Upon success,
most XTI/TLI library functions return zero (0) or a positive integer reflecting a
returned paramter value.
Upon failure,
XTI/TLI library functions return -1 and set
.IR t_errno (3)
to an applicable error number.
.\"
.\"
.SH ERRORS
.PP
The errors that can be returned by XTI/TLI Library calls are detailed
in
.IR t_errno (3).
.\"
.\"
.SH "SEE ALSO"
.PP
.BR t_accept (3),
.BR t_addleaf (3),
.BR t_alloc (3),
.BR t_bind (3),
.BR t_close (3),
.BR t_connect (3),
.BR t_errno (3),
.BR t_error (3),
.BR t_free (3),
.BR t_getinfo (3),
.BR t_getprotaddr (3),
.BR t_getstate (3),
.BR t_listen (3),
.BR t_look (3),
.BR t_open (3),
.BR t_optmgmt (3),
.BR t_rcv (3),
.BR t_rcvconnect (3),
.BR t_rcvdis (3),
.BR t_rcvleafchange (3),
.BR t_rcvrel (3),
.BR t_rcvreldata (3),
.BR t_rcvudata (3),
.BR t_rcvuderr (3),
.BR t_rcvv (3),
.BR t_rcvvudata (3),
.BR t_removeleaf (3),
.BR t_snd (3),
.BR t_snddis (3),
.BR t_sndrel (3),
.BR t_sndreldata (3),
.BR t_sndudata (3),
.BR t_sndv (3),
.BR t_sndvudata (3),
.BR t_strerror (3),
.BR t_sync (3),
.BR t_sysconf (3),
.BR t_unbind (3).
.\"
.\"
.SH "CONFORMING TO"
.PP
The Open Group XNS Issue 5.2.
.[
xns
.]
.\"
.\"
.[
$LIST$
.]
.T4