Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ t_rcvcnt(S) — OpenDesktop Software Development System 3.0.0

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

netbuf(FP)


 t_rcvconnect(S)           (TLI/XTI) 6 January 1993           t_rcvconnect(S)


 Name

    t_rcvconnect - receive the confirmation from a connect request

 Syntax


    TLI syntax


    cc . . . -lnsls


    #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;


 Description

    This function enables a calling transport user to determine the status of
    a previously sent connect request and is used in conjunction with
    tconnect 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 esta-
    blished, and call contains information associated with the newly esta-
    blished connection.  call points to a tcall 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 mean-
    ing 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 trcvconnect.  By default, trcvconnect
    executes in synchronous mode and waits for the connection to be esta-
    blished before returning.  On return, the addr, opt, and udata fields
    reflect values associated with the connection.

    If ONONBLOCK is set (via topen or fcntl), trcvconnect executes in
    asynchronous mode and reduces to a poll for existing connect confirma-
    tions.  If none are available, trcvconnect fails and returns immediately
    without waiting for the connection to be established.  (See TNODATA
    below.)  trcvconnect must be re-issued at a later time to complete the
    connection establishment phase and retrieve the information returned in
    call.

 Return value

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

 Diagnostics

    On failure, terrno may be 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 argu-
                        ment 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.

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

    [TNODATA]           ONONBLOCK was set, but a connect confirmation has
                        not yet arrived.

    [TNOTSUPPORT]       This function is not supported by the underlying
                        transport provider.

    [TOUTSTATE]         (XTI only.)  The state was incorrect when this rou-
                        tine was called.

    [TSYSERR]           A system error has occurred during execution of this
                        function.

 See also

    netbuf(FP), taccept(S), tbind(S), tconnect(S), tlisten(S), topen(S)

 Standards conformance

    trcvconnect is conformant with:
    AT&T SVID Issue 2;
    X/Open Portability Guide, Issue 3, 1989;
    and Intel386 Binary Compatibility Specification, Edition 2 (iBCSe2).


Typewritten Software • bear@typewritten.org • Edmonds, WA 98026