49 
  50 
  51        By default, t_sndudata() operates in synchronous mode and may wait if
  52        flow control restrictions prevent the data from being accepted by the
  53        local transport provider at the time the call is made.  However, if
  54        O_NONBLOCK is set by means of t_open(3NSL) or fcntl(2), t_sndudata()
  55        will execute in asynchronous mode and will fail under such conditions.
  56        The process can arrange to be notified of the clearance of a flow
  57        control restriction by means of either t_look(3NSL) or the EM
  58        interface.
  59 
  60 
  61        If the amount of data specified in udata exceeds the TSDU size as
  62        returned in the tsdu field of the info argument of t_open(3NSL) or
  63        t_getinfo(3NSL), a TBADDATA error will be generated. If t_sndudata() is
  64        called before the destination user has activated its transport endpoint
  65        (see t_bind(3NSL)), the data unit may be discarded.
  66 
  67 
  68        If it is not possible for the transport provider to immediately detect
  69        the conditions that cause the errors TBADDADDR and TBADOPT, these
  70        errors will alternatively be returned by t_rcvuderr. Therefore, an
  71        application must be prepared to receive these errors in both of these
  72        ways.
  73 
  74 
  75        If the call is interrupted, t_sndudata() will return EINTR and the
  76        datagram will not be sent.
  77 
  78 RETURN VALUES
  79        Upon successful completion, a value of  0 is returned.  Otherwise, a
  80        value of  -1 is returned and t_errno is set to indicate an error.
  81 
  82 VALID STATES
  83        T_IDLE.
  84 
  85 ERRORS
  86        On failure, t_errno is set to one of the following:
  87 
  88        TBADADDR
  89                       The specified protocol address was in an incorrect
  90                       format or contained illegal information.
  91 
  92 

  49 
  50 
  51        By default, t_sndudata() operates in synchronous mode and may wait if
  52        flow control restrictions prevent the data from being accepted by the
  53        local transport provider at the time the call is made.  However, if
  54        O_NONBLOCK is set by means of t_open(3NSL) or fcntl(2), t_sndudata()
  55        will execute in asynchronous mode and will fail under such conditions.
  56        The process can arrange to be notified of the clearance of a flow
  57        control restriction by means of either t_look(3NSL) or the EM
  58        interface.
  59 
  60 
  61        If the amount of data specified in udata exceeds the TSDU size as
  62        returned in the tsdu field of the info argument of t_open(3NSL) or
  63        t_getinfo(3NSL), a TBADDATA error will be generated. If t_sndudata() is
  64        called before the destination user has activated its transport endpoint
  65        (see t_bind(3NSL)), the data unit may be discarded.
  66 
  67 
  68        If it is not possible for the transport provider to immediately detect
  69        the conditions that cause the errors TBADADDR and TBADOPT, these errors
  70        will alternatively be returned by t_rcvuderr. Therefore, an application
  71        must be prepared to receive these errors in both of these ways.

  72 
  73 
  74        If the call is interrupted, t_sndudata() will return EINTR and the
  75        datagram will not be sent.
  76 
  77 RETURN VALUES
  78        Upon successful completion, a value of  0 is returned.  Otherwise, a
  79        value of  -1 is returned and t_errno is set to indicate an error.
  80 
  81 VALID STATES
  82        T_IDLE.
  83 
  84 ERRORS
  85        On failure, t_errno is set to one of the following:
  86 
  87        TBADADDR
  88                       The specified protocol address was in an incorrect
  89                       format or contained illegal information.
  90 
  91