t_rcvconnect(3)t_rcvconnect(3)NAMEt_rcvconnect() - receive the confirmation from a connect request
SYNOPSISDESCRIPTION
The function enables a calling transport user to determine the status
of a previously sent connect request. is also used in conjunction with
to establish a connection in asynchronous mode. The connection will be
established on successful completion of this function.
fd identifies the local transport endpoint where communication will be
established. call contains information associated with the newly
established connection. call points to a structure which contains the
following members:
The type structure is defined in the or header file. This structure,
which is used to define buffer parameters, has the following members:
maximum byte length of the data buffer
actual byte length of data written to buffer
points to buffer location
In call, addr returns the protocol address associated with the respond‐
ing transport endpoint. opt presents any protocol-specific information
associated with the connection. For XTI over the OSI transport
provider, struct should be used. For TLI, see the documentation for
the transport provider being used. udata points to optional user data
that may be returned by the destination transport user during connec‐
tion establishment. sequence has no meaning for this function.
The maxlen field of each argument must be set before issuing this func‐
tion to indicate the maximum size of the buffer for each. However,
call may be a null pointer, in which case no information is given to
the user on return from By default, 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 is set (via or executes in asynchronous mode, and reduces to a poll
for existing connect confirmations. If none are available, fails and
returns immediately without waiting for the connection to be estab‐
lished. (See [TNODATA] below.) must be re-issued at a later time to
complete the connection establishment phase and retrieve the informa‐
tion returned in call.
Valid States
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 trans‐
port endpoint.
[TBUFOVFLW] The number of bytes allocated for an incoming argu‐
ment is 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
[TNODATA] was set, but a connect confirmation has not yet
arrived.
[TLOOK] An asynchronous event has occurred on this trans‐
port endpoint and requires immediate attention.
[TNOTSUPPORT] This function is not supported by the underlying
transport provider.
[TOUTSTATE] This function was issued in the wrong sequence on
the transport endpoint referenced by fd.
[TSYSERR] A system error has occurred during execution of
this function.
[TPROTO] (XTI only) This error indicates that a communica‐
tion problem has been detected between XTI and the
transport provider for which there is no existing
XTI (
FILES
XTI data structure
TLI data structure
SEE ALSOfcntl(2), t_accept(3), t_alloc(3), t_bind(3), t_connect(3), t_lis‐
ten(3), t_open(3), thread_safety(5).
STANDARDS CONFORMANCEt_rcvconnect(3)