(TLI/XTI)
t_sndrel(NET)
t_sndrel --
initiate an orderly release
Syntax
TLI syntax
cc . . . -lnsl
#include <sys/tiuser.h>
int t_sndrel (fd)
int fd;
XTI syntax
cc . . . -lxti
#include <xti.h>
int t_sndrel (fd)
int fd;
Description
The t_sndrel
function is used to initiate an orderly release of a transport connection
and indicates to the transport provider that
the transport user has no more data to send.
fd
identifies the local transport endpoint where the connection exists.
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 been received.
This function is an optional service of the transport provider
and is only supported if the transport provider returned service
type 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.
Diagnostics
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.
[TLOOK]-
A disconnect event has occurred on this transport endpoint.
[TOUTSTATE]-
The state was incorrect when this routine was called; XTI only.
[TNOTSUPPORT]-
This error is generated if the T_COTS_ORD service type
is not returned by a previous call to the
t_open(NET)
or
t_getinfo(NET)
routine.
[TSYSERR]-
A system error has occurred during execution of this function.
See also
Intro(NET),
t_getinfo(NET),
t_open(NET),
t_rcvrel(NET)
Standards conformance
t_sndrel is conformant with:
AT&T SVID Issue 3
;
X/Open CAE Specification, Networking Services, Issue 4, 1994.
;
and
Intel386 Binary Compatibility Specification, Edition 2 (iBCSe2)
.
© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003