Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

t_rcvconnect(3xti) [ultrix man page]

t_rcvconnect(3xti)														t_rcvconnect(3xti)

       t_rcvconnect - receive the confirmation from a connect request

       #include <xti.h>

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

       fd	 Identifies the local transport endpoint where communications is established.

       call	 Contains  information associated with the newly established connection.  Call points to a t_call structure that contains the fol-
		 lowing members:
		 struct netbuf addr;
		 struct netbuf opt;
		 struct netbuf udata;
		 int sequence;

		 The members of the t_call structure have the following meanings:

		 addr	     Returns the protocol address associated with the responding transport endpoint.

		 opt	     Presents any protocol-specific information associated with the transport endpoint.

		 udata	     Points to any optional user data that may be returned by the destination transport user during connection	establish-

		 sequence    Has no meaning for this function.

       This function enables a calling transport user to determine the status of a previously sent connect request. Is used in conjunction with to
       establish a connection in asynchronous mode. The connection is established on successful completion of 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,
       call  can  be NULL, 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  connec-

       Parameters	    Before Call   After Call
       fd		    x		  /
       call->addr.maxlen    x		  /
       call->addr.len	    /		  x
       call->addr.buf	    x		  (x)
       call->opt.maxlen     x		  /
       call->opt.len	    /		  x
       call->opt.buf	    x		  (x)
       call->udata.maxlen   x		  /
       call->udata.len	    /		  x
       call->udata.buf	    x		  (?)
       call->sequence	    /		  /

       If  O_NONBLOCK  is  set	by  means of or executes in asynchronous mode and reduces to a poll for existing connect confirmations. If none is
       available, fails and returns immediately without waiting for the connection to be established. The function must be  reissued  at  a  later
       time to complete the connection establishment phase and retrieve the information returned to call.

Return Values
       Upon successful completion, a value of 0 is returned. On failure, a value of -1 is returned, and t_errno is set to indicate the error.

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

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

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

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

       [TOUTSTATE]	   The 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.

See Also
       t_accept(3xti), t_alloc(3xti), t_bind(3xti), t_connect(3xti), t_listen(3xti), t_open(3xti), t_optmgmt(3xti)

Man Page