hpux man page for t_rcvrel

Query: t_rcvrel

OS: hpux

Section: 3

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

t_rcvrel(3)						     Library Functions Manual						       t_rcvrel(3)

NAME
t_rcvrel() - acknowledge receipt of an orderly release indication at a transport endpoint
SYNOPSIS
DESCRIPTION
The function is used in connection-oriented mode to acknowledge receipt of an orderly release indication at a transport endpoint. The released endpoint is specified by fd, which is a file descriptor previously returned by the function. After receipt of this orderly release indication at the transport endpoint specified by fd, the transport user should not try to receive additional data from that transport endpoint. Any attempt to receive more data from a released transport endpoint blocks continuously. However, the transport user may continue to send data across the connection until a release is sent by the transport user by invoking the function call. The function should not be used unless the servtype type-of-service returned by the or functions is (supports connection-mode service with the optional orderly release facility). Valid States Note HP OSI XTI does not support Fork Safety is not fork-safe.
RETURN VALUE
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and is set to indicate the error.
ERRORS
On failure, is set to one of the following: [TBADF] The specified identifier does not refer to a transport endpoint. [TNOREL] No orderly release indication currently exists on the specified transport endpoint. [TBUFOVFLW] The number of bytes allocated for incoming data is not sufficient to store the data. [TNOTSUPPORT] This function is not supported by the underlying transport provider. [TLOOK] An asynchronous event has occurred on the transport endpoint referenced by fd and requires immediate attention. [TSYSERR] A system error has occurred during execution of this function. [TPROTO] (XTI only) This error indicates that a communication problem has been detected between XTI and the transport provider for which there is no other suitable XTI ( [TOUTSTATE] (XTI only) The function was issued in the wrong sequence on the transport endpoint referenced by fd.
SEE ALSO
t_getinfo(3), t_open(3), t_sndrel(3), thread_safety(5).
STANDARDS CONFORMANCE
t_rcvrel(3)
Related Man Pages
t_look(3) - hpux
t_rcvrel(3) - hpux
t_rcvrel(3nsl) - sunos
t_sndrel(3nsl) - sunos
t_rcvrel(3nsl) - opensolaris
Similar Topics in the Unix Linux Community
GREP in Bourne
Simutrans: 102-0 (stable) released
What is the difference between softerrors,harderrors,transport errors?