Previous section.

Technical Standard: Networking Services (XNS), Issue 5.2 Draft 2.0
Copyright © 1999 The Open Group


t_rcvconnect - receive the confirmation from a connection request


#include <xti.h>

int t_rcvconnect(int fd, struct t_call *call);


Parameters Before call After call

fd x /
call->addr.maxlen x =
call->addr.len / x
call->addr.buf ? (?)
call->opt.maxlen x =
call->opt.len / x
call->opt.buf ? (?)
call->udata.maxlen x =
call->udata.len / x
call->udata.buf ? (?)
call->sequence = =

This function enables a calling transport user to determine the status of a previously sent connection request and is used in conjunction with t_connect() to establish a connection in asynchronous mode, and to complete a synchronous t_connect() call that was interrupted by a signal. The connection will be established on successful completion of this function.

The argument fd identifies the local transport endpoint where communication will be established, and call contains information associated with the newly established connection. The argument call points to a t_call structure which contains the following members:

struct netbuf addr; struct netbuf opt; struct netbuf udata; int sequence;

In call, addr returns the protocol address associated with the responding transport endpoint, opt presents any options associated with the connection, udata points to optional user data that may be returned by the destination transport user during connection establishment, and sequence has no meaning for this function.

The maxlen field of each argument must be set before issuing this function to indicate the maximum size of the buffer for each. However, maxlen can be set to zero, in which case no information to this specific argument is given to the user on the return from t_rcvconnect(). If call is set to NULL, no information at all is returned. By default, t_rcvconnect() 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 t_open() or fcntl()), t_rcvconnect() executes in asynchronous mode, and reduces to a poll for existing connection confirmations. If none are available, t_rcvconnect() fails and returns immediately without waiting for the connection to be established. (See [TNODATA] below.) In this case, t_rcvconnect() must be called again to complete the connection establishment phase and retrieve the information returned in call.




On failure, t_errno is set to one of the following:

The specified file descriptor does not refer to a transport endpoint.

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 connection information to be returned in call will be discarded. The provider's state, as seen by the user, will be changed to T_DATAXFER.

An asynchronous event has occurred on this transport connection and requires immediate attention.

O_NONBLOCK was set, but a connection confirmation has not yet arrived.

This function is not supported by the underlying transport provider.

The communications endpoint referenced by fd is not in one of the states in which a call to this function is valid.

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).

A system error has occurred during execution of this function.


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.


t_accept(), t_alloc(), t_bind(), t_connect(), t_listen(), t_open(), t_optmgmt().


Issue 4

The SYNOPSIS section is placed in the form of a standard C function prototype.

Contents Next section Index