(TLI/XTI)
t_rcvrel(NET)
t_rcvrel --
acknowledge receipt of an orderly release indication
Syntax
TLI syntax
cc . . . -lnsl
#include <sys/tiuser.h>
t_rcvrel (fd)
int fd;
XTI syntax
cc . . . -lxti
#include <xti.h>
t_rcvrel (fd)
int fd;
Description
The t_rcvrel function is used to acknowledge receipt of
an orderly release indication.
fd
identifies the local transport endpoint where the connection exists.
After receipt of this indication, the user may not attempt to
receive more data because such an attempt will block forever.
However, the user may continue to send data over the connection if
t_sndrel has not been issued by the user.
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_rcvrel 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.
[TLOOK]-
An asynchronous event has occurred on this transport endpoint and requires
immediate attention.
[TNOREL]-
No orderly release indication currently exists on the specified
transport endpoint.
[TNOTSUPPORT]-
Without the T_COTS_ORD service type being set, this
function is not supported by the underlying transport
provider.
[TOUTSTATE]-
The state was incorrect when this routine was called; XTI only.
[TSYSERR]-
A system error occurred during execution of this function.
One possibility is an I/O error and is indicated by
errno being set to EIO.
Another is a
protocol error and is indicated by errno being set to
EPROTO.
See also
Intro(NET),
t_open(NET),
t_sndrel(NET)
Standards conformance
t_rcvrel 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