61
62 By default, t_sndvudata() operates in synchronous mode and may wait if
63 flow control restrictions prevent the data from being accepted by the
64 local transport provider at the time the call is made. However, if
65 O_NONBLOCK is set by means of t_open(3NSL) or fcntl(2), t_sndvudata()
66 executes in asynchronous mode and will fail under such conditions. The
67 process can arrange to be notified of the clearance of a flow control
68 restriction by means of either t_look(3NSL) or the EM interface.
69
70
71 If the amount of data specified in iov0 through iov [iovcount-1]
72 exceeds the TSDU size as returned in the tsdu field of the info
73 argument of t_open(3NSL) or t_getinfo(3NSL), or is zero and sending of
74 zero octets is not supported by the underlying transport service, a
75 TBADDATA error is generated. If t_sndvudata() is called before the
76 destination user has activated its transport endpoint (see
77 t_bind(3NSL)), the data unit may be discarded.
78
79
80 If it is not possible for the transport provider to immediately detect
81 the conditions that cause the errors TBADDADDR and TBADOPT, these
82 errors will alternatively be returned by t_rcvuderr(3NSL). An
83 application must therefore be prepared to receive these errors in both
84 of these ways.
85
86 RETURN VALUES
87 Upon successful completion, a value of 0 is returned. Otherwise, a
88 value of -1 is returned and t_errno is set to indicate an error.
89
90 VALID STATES
91 T_IDLE.
92
93 ERRORS
94 On failure, t_errno is set to one of the following:
95
96 TBADADDR
97 The specified protocol address was in an incorrect
98 format or contained illegal information.
99
100
101 TBADDATA
102 Illegal amount of data.
103
104 o A single send was attempted specifying a TSDU
|
61
62 By default, t_sndvudata() operates in synchronous mode and may wait if
63 flow control restrictions prevent the data from being accepted by the
64 local transport provider at the time the call is made. However, if
65 O_NONBLOCK is set by means of t_open(3NSL) or fcntl(2), t_sndvudata()
66 executes in asynchronous mode and will fail under such conditions. The
67 process can arrange to be notified of the clearance of a flow control
68 restriction by means of either t_look(3NSL) or the EM interface.
69
70
71 If the amount of data specified in iov0 through iov [iovcount-1]
72 exceeds the TSDU size as returned in the tsdu field of the info
73 argument of t_open(3NSL) or t_getinfo(3NSL), or is zero and sending of
74 zero octets is not supported by the underlying transport service, a
75 TBADDATA error is generated. If t_sndvudata() is called before the
76 destination user has activated its transport endpoint (see
77 t_bind(3NSL)), the data unit may be discarded.
78
79
80 If it is not possible for the transport provider to immediately detect
81 the conditions that cause the errors TBADADDR and TBADOPT, these errors
82 will alternatively be returned by t_rcvuderr(3NSL). An application
83 must therefore be prepared to receive these errors in both of these
84 ways.
85
86 RETURN VALUES
87 Upon successful completion, a value of 0 is returned. Otherwise, a
88 value of -1 is returned and t_errno is set to indicate an error.
89
90 VALID STATES
91 T_IDLE.
92
93 ERRORS
94 On failure, t_errno is set to one of the following:
95
96 TBADADDR
97 The specified protocol address was in an incorrect
98 format or contained illegal information.
99
100
101 TBADDATA
102 Illegal amount of data.
103
104 o A single send was attempted specifying a TSDU
|