Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

t_sndrel(3) [osf1 man page]

t_sndrel(3)						     Library Functions Manual						       t_sndrel(3)

NAME
t_sndrel - Initiates an endpoint connect orderly release LIBRARY
XTI Library (libxti.a) SYNOPSIS
#include <xti.h> int t_sndrel( int fd) ; STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: t_sndrel(): XNS4.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. PARAMETERS
The following table summarizes the relevance of input parameter data before and after t_sndrel() is called: Parameter Before Call After Call ------------------------------------- fd y n Notes to Table: y This is a meaningful parameter. n This is not a meaningful parameter. fd Specifies a file descriptor returned by the t_open() function that identifies a local transport endpoint where an orderly release is wanted. VALID STATES
The t_sndrel() function can be called only in the T_DATAXFER and T_INREL transport provider states. DESCRIPTION
The t_sndrel() XTI function is used in connection-oriented mode to initiate an orderly release at a transport endpoint specified by a file descriptor previously returned by the t_open() function. After this orderly release is indicated, the transport user should not try to send more data through that transport endpoint; an attempt to send more data to a released transport endpoint may block continuously. However, a transport user may continue to receive data over the connection until an orderly release indication is received. The t_sndrel() function should not be used unless the servtype type-of-service returned by the t_open() or t_getinfo() function is T_COTS_ORD (supports connection-mode service with the optional orderly release facility). RETURN VALUES
Upon successful completion, a value of 0 (zero) is returned. Otherwise, a value of -1 is returned and t_errno is set to indicate an error. ERRORS
If the t_sndrel(|) function fails, t_errno may be set to one of the following values: [TBADF] File descriptor fd does not refer to a valid transport endpoint. [TFLOW] Asynchronous mode is indicated because O_NONBLOCK was set, but the transport provider cannot accept a release because of flow-control restrictions. [TLOOK] An asynchronous event has occurred on this transport endpoint and requires immediate attention. [TNOTSUPPORT] This function is not supported by the underlying transport provider. [TOUTSTATE] The t_sndrel() function was issued in the wrong sequence at the transport endpoint specified by the fd parameter. [TSYSERR] A system error occurred during execution of this function. [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(t_errno). RELATED INFORMATION
Functions: t_getinfo(3), t_open(3), t_rcvrel(3) delim off t_sndrel(3)

Check Out this Related Man Page

t_rcvrel(3)						     Library Functions Manual						       t_rcvrel(3)

NAME
t_rcvrel - Acknowledges receipt of an orderly release indication LIBRARY
XTI Library (libxti.a) SYNOPSIS
#include <xti.h> int t_rcvrel( int fd) ; STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: t_rcvrel(): XNS4.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. PARAMETERS
The following table summarizes the relevance of input parameter data before and after t_rcvrel() is called: Parameter Before Call After Call ------------------------------------- fd y n Notes to Table: y This is a meaningful parameter. n This is not a meaningful parameter. fd Specifies a file descriptor returned by the t_open() function that identifies a local transport endpoint that has been released. VALID STATES
The t_rcvrel() function can be called only in the T_DATAXFER and T_OUTREL transport provider states. DESCRIPTION
The t_rcvrel() XTI function is used in connection-oriented mode to acknowledge receipt of an orderly release indication at a transport end- point. The released endpoint is specified by a file descriptor previously returned by the t_open() function. After receipt of this orderly release indication, at the transport endpoint specified by the file descriptor, a 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, a transport user may continue to send data across the connection until a release is sent by a transport user who invokes a t_sndrel() function call. The t_rcvrel() function should not be used unless the servtype type-of-service returned by the t_open() or t_getinfo() functions is T_COTS_ORD (supports connection-mode service with the optional orderly release facility). RETURN VALUE
Upon successful completion, a value of 0 (zero) is returned. Otherwise, a value of -1 is returned and t_errno is set to indicate the error. ERRORS
If the t_rcvrel() function fails, t_errno may be set to one of the following values: [TBADF] File descriptor fd does not refer to a valid transport endpoint. [TNOREL] No orderly release indication currently exists at the transport endpoint specified by the fd parameter. [TLOOK] An asynchronous event has occurred on the transport endpoint specified by the fd parameter and requires immediate attention. [TSYSERR] A system error occurred during execution of this function. [TOUTSTATE] The t_rcvrel() function was issued in the wrong sequence at the transport endpoint referenced by the fd parameter. [TNOTSUPPORT] This function is not supported by the underlying transport provider. [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(t_errno). RELATED INFORMATION
Functions: t_getinfo(3), t_open(3), t_sndrel(3) delim off t_rcvrel(3)
Man Page