t_rcvrel(3)t_rcvrel(3)NAMEt_rcvrel() - acknowledge receipt of an orderly release indication at a
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 end‐
point 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. How‐
ever, the transport user may continue to send data across the connec‐
tion until a release is sent by the transport user by invoking the
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).
HP OSI XTI does not support
is not fork-safe.
Upon successful completion, a value of 0 is returned. Otherwise, a
value of −1 is returned and is set to indicate the error.
On failure, is set to one of the following:
[TBADF] The specified identifier does not refer to a trans‐
[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
[TLOOK] An asynchronous event has occurred on the trans‐
port endpoint referenced by fd and requires immedi‐
[TSYSERR] A system error has occurred during execution of
[TPROTO] (XTI only) This error indicates that a communica‐
tion 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
SEE ALSOt_getinfo(3), t_open(3), t_sndrel(3), thread_safety(5).