Query: t_rcvudata
OS: hpux
Section: 3
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
t_rcvudata(3) Library Functions Manual t_rcvudata(3)NAMEt_rcvudata() - receive a data unit from remote transport provider userSYNOPSISDESCRIPTIONThe function is used in connectionless-mode to receive a data unit from a remote transport provider user. The argument fd identifies the local transport endpoint through which data will be received. unitdata holds information associated with the received data unit. flags is set on return to indicate that the complete data unit was not received. The argument unitdata points to a structure containing the follow- ing 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 The maxlen field of addr, opt and udata must be set before calling this function to indicate the maximum size of the buffer for each. On return from this call, addr specifies the protocol address of the sending user, opt identifies protocol-specific options that were asso- ciated with this data unit, and udata specifies the user data that was received. By default, executes in the synchronous operating mode. The function waits for data to arrive at the transport endpoint specified by fd before returning control to the transport user who called this function. However, when the transport endpoint, specified by the fd parame- ter, has the option set by or function, the function executes in asynchronous mode. In asynchronous mode, when a data unit is unavailable, control is immediately returned to the caller. If the buffer defined in the udata field of unitdata is not large enough to hold the current data unit, the buffer will be filled and T_MORE will be set in flags on return to indicate that another should be called to retrieve the rest of the data unit. Subsequent calls to will return zero for the length of the address and options until the full data unit has been received. Valid States Fork Safety is not fork-safe.RETURN VALUEUpon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and is set to indicate the error.ERRORSOn failure, is set to one of the following: [TBADF] The specified file descriptor does not refer to a transport endpoint. [TNODATA] was set, but no data units are currently available from the transport provider. [TBUFOVFLW] The number of bytes allocated for the incoming protocol address or protocol options is not sufficient to store the information. The unit data information normally returned in unitdata is discarded. [TLOOK] An asynchronous event has occurred on this transport endpoint required immediate attention. [TNOTSUPPORT] This function is not supported by the underlying transport provider. [TOUTSTATE] (XTI only) The function was issued in the wrong sequence on the transport endpoint referenced by fd. [TSYSERR] A system error occurred during execution of this function. [TPROTO] (XTI only) This error indicates that a communication problem has been detected between XTI and the transport provider for which there is no other suitable XTI (SEE ALSOfcntl(2), t_alloc(3), t_open(3), t_optmgmt(3), t_rcvuderr(3), t_sndudata(3), thread_safety(5).STANDARDS CONFORMANCEt_rcvudata(3)
Related Man Pages |
---|
t_rcvudata(3nsl) - opensolaris |
t_rcvudata(3nsl) - mojave |
t_rcvudata(3nsl) - minix |
t_rcvudata(3nsl) - debian |
t_rcvudata(3nsl) - plan9 |
Similar Topics in the Unix Linux Community |
---|
Unix File Permissions |
How to list file size on HPUX? |
How to extract every repeated string between two specific string? |
Thank you members and admins |
Shopt -s histappend |