t_rcvrel(3) [hpux man page]
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)
Check Out this Related Man Page
t_rcvrel(3NSL) Networking Services Library Functions t_rcvrel(3NSL) NAME
t_rcvrel - acknowledge receipt of an orderly release indication SYNOPSIS
#include <xti.h> int t_rcvrel(int fd); DESCRIPTION
This routine is part of the XTI interfaces which evolved from the TLI interfaces. XTI represents the future evolution of these interfaces. However, TLI interfaces are supported for compatibility. When using a TLI routine that has the same name as an XTI routine, the tiuser.h header file must be used. Refer to the TLI COMPATIBILITY section for a description of differences between the two interfaces. This function is used to receive an orderly release indication for the incoming direction of data transfer. The argument fd identifies the local transport endpoint where the connection exists. After receipt of this indication, the user may not attempt to receive more data by means of t_rcv(3NSL) or t_rcvv(). Such an attempt will fail with t_error set to TOUTSTATE. However, the user may continue to send data over the connection if t_sndrel(3NSL) has not been called 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(3NSL) or t_getinfo(3NSL). Any user data that may be associated with the orderly release indication is discarded when t_rcvrel() is called. RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and t_errno is set to indicate an error. VALID STATES
T_DATAXFER, T_OUTREL. ERRORS
On failure, t_errno is 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 This function is not supported by the underlying transport provider. TOUTSTATE The communications endpoint referenced by fd is not in one of the states in which a call to this function is valid. TPROTO This error indicates that a communication problem has been detected between XTI and the transport provider for which there is no other suitable XTI error (t_errno). TSYSERR A system error has occurred during execution of this function. TLI COMPATIBILITY
The XTI and TLI interface definitions have common names but use different header files. This, and other semantic differences between the two interfaces are described in the subsections below. Interface Header The XTI interfaces use the header file, xti.h. TLI interfaces should not use this header. They should use the header: #include<tiuser.h> Error Description Values The t_errno values that can be set by the XTI interface and cannot be set by the TLI interface are: TPROTO TOUTSTATE ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |MT Level |Safe | +-----------------------------+-----------------------------+ SEE ALSO
t_getinfo(3NSL), t_open(3NSL), t_sndrel(3NSL), attributes(5) SunOS 5.10 7 May 1998 t_rcvrel(3NSL)