t_rcvconnect -- receive the confirmation from a connect request


TLI syntax

cc . . . -lnsl

#include <sys/tiuser.h>

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

XTI syntax

cc . . . -lxti

#include <xti.h>

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


The t_rcvconnect function enables a calling transport user to determine the status of a previously sent connect request and is used in conjunction with t_connect to establish a connection in asynchronous mode. The connection is established on successful completion of this function.

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

   struct netbuf addr;
   struct netbuf opt;
   struct netbuf udata;
   int sequence;
netbuf is described in netbuf(FP). In call, addr returns the protocol address associated with the responding transport endpoint, opt presents any protocol-specific information 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 (see netbuf in netbuf(FP)) field of each argument must be set before issuing this function to indicate the maximum size of the buffer for each. However, call may be NULL, in which case no information is given to the user on return from t_rcvconnect. 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 connect confirmations. If none are available, t_rcvconnect fails and returns immediately without waiting for the connection to be established. (See TNODATA below.) t_rcvconnect must be re-issued at a later time to complete the connection establishment phase and retrieve the information returned in call.

Return values

t_rcvconnect returns 0 on success and -1 on failure, and t_errno is set to indicate the error.


On failure, t_errno may be 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 is not sufficient to store the value of that argument and the connect information to be returned in call is discarded. The provider's state, as seen by the user, is changed to DATAXFER.

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

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

This function is not supported by the underlying transport provider.

The state was incorrect when this routine was called; XTI only.

A system error has occurred during execution of this function.

See also

Intro(NET), netbuf(FP), t_accept(NET), t_bind(NET), t_connect(NET), t_listen(NET), t_open(NET)

Standards conformance

t_rcvconnect is conformant with:

AT&T SVID Issue 3 ;
X/Open CAE Specification, Networking Services, Issue 4, 1994. ;
and Intel386 Binary Compatibility Specification, Edition 2 (iBCSe2) .

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003