Receive the confirmation from a connect request.
X/Open Transport Interface Library (libxti.a)
int t_rcvconnect (fd, call) int fd; struct t_call *call;
The t_rcvconnect subroutine enables a calling transport user to determine the status of a previously sent connect request and is used in conjunction with the t_connect subroutine to establish a connection in asynchronous mode. The connection is established on successful completion of this subroutine.
|fd||Identifies the local transport endpoint where communication will be established.|
|call|| Contains information associated with the newly established connection. The call parameter points to a t_call structure which contains the following members:
struct netbuf addr; struct netbuf opt; struct netbuf udata; int sequence;
The fields of the t_call structure are:
The maxlen field of each t_call member must be set before issuing this subroutine to indicate the maximum size of the buffer for each. However, the vale of the call parameter may be a null pointer, in which case no information is given to the user on return from the t_rcvconnect subroutine. By default, the t_rcvconnect subroutine executes in synchronous mode and waits for the connection to be established before returning. On return, the addr, opt and udata fields reflect values associated with the connection.
If O_NONBLOCK is set (via the t_open subroutine or fcntl), the t_rcvconnect subroutine executes in asynchronous mode, and reduces to a poll for existing connect confirmations. If none are available, the t_rcvconnect subroutine fails and returns immediately without waiting for the connection to be established. (See TNODATA in "Error Codes" below.) In this case, the t_rcvconnect subroutine must be called again to complete the connection establishment phase and retrieve the information returned in the call parameter.
|-1||t_errno is set to indicate an error.|
On failure, t_errno is set to one of the following:
|TBADF||The specified file descriptor does not refer to a transport endpoint.|
|TBUFOVFLW||The number of bytes allocated for an incoming argument (maxlen) is greater than 0 but not sufficient to store the value of that argument, and the connect information to be returned in call will be discarded. The provider's state, as seen by the user, will be changed to T_DATAFER.|
|TLOOK||An asynchronous event has occurred on the transport connection and requires immediate attention.|
|TNODATA||O_NONBLOCK was set, but a connect confirmation has not yet arrived.|
|TNOTSUPPORT||This subroutine is not supported by the underlying transport provider.|
|TOUTSTATE||The subroutine was issued in the wrong sequence on the transport endpoint referenced by the fd parameter.|
|TPROTO||This error indicates that a communication problem has been detected between the X/Open Transport Interface and the transport provider for which there is no other suitable X/Open Transport Interface (t_errno).|
|TSYSERR||A system error has occurred during execution of this subroutine.|
The t_accept subroutine, t_alloc subroutine, t_bind subroutine, t_connect subroutine, t_listen subroutine, t_open subroutine, t_optmgmt subroutine.