t_sndrel(3N) t_sndrel(3N)
NAME
t_sndrel - initiate an orderly release
SYNOPSIS
cc [options] file -lnsl
#include <xti.h>
int t_sndrel(int fd);
Parameters
fd the file descriptor for the transport endpoint where the
connection exists.
DESCRIPTION
This function is a TLI/XTI connection release routine used to
initiate an orderly release of a transport connection
associated with the transport endpoint specified by fd.
t_sndrel indicates to the transport provider that the
transport user has no more data to send.
This function is an optional service of the transport provider
and is only supported if the transport provider returned
service type T_COTS or T_COTS_ORD on t_open or t_getinfo.
Return Values
t_sndrel returns 0 on success and -1 on failure and t_errno is
set to indicate the error.
Errors
On failure, t_errno may be set to one of the following:
TBADF The specified file descriptor does not refer to a
transport endpoint.
TFLOW O_NONBLOCK was set, but the flow control mechanism
prevented the transport provider from accepting the
function at this time.
TNOTSUPPORT
This function is not supported by the underlying
transport provider.
TSYSERR A system error has occurred during execution of this
function.
Copyright 1994 Novell, Inc. Page 1
t_sndrel(3N) t_sndrel(3N)
TLOOK An asynchronous even has occurred on the transport
endpoint referenced by fd and requires immediate
attention.
TOUTSTATE The function was issued in the wrong sequence on the
transport endpoint referenced by fd.
TPROTO A communication problem has been detected with the
transport provider and there is no other value of
t_errno to describe the error condition.
State Transitions
T_DATAXFER on entry and T_OUTREL on exit; or T_INREL on entry
and T_IDLE on exit.
Files
/usr/lib/libxti.so
X/Open Transport Interface Library (shared
object)
/usr/lib/libnsl.so
Network Services Library (shared object)
USAGE
After issuing t_sndrel, the user may not send any more data
over the connection. However, a user may continue to receive
data if an orderly release indication has not been received.
If t_sndrel is issued from an invalid state, the provider will
generate an EPROTO protocol error; however, this error may not
occur until a subsequent reference to the transport endpoint.
REFERENCES
intro(3), t_getinfo(3N), t_open(3N), t_rcvrel(3N)
Copyright 1994 Novell, Inc. Page 2