43 .\" Portions Copyright 1989 AT&T
44 .\" Copyright 1994, The X/Open Company Ltd. All Rights Reserved.
45 .\" Portions Copyright (c) 1998, Sun Microsystems, Inc. All Rights Reserved.
46 .\"
47 .TH T_SNDVUDATA 3NSL "Aug 23, 2001"
48 .SH NAME
49 t_sndvudata \- send a data unit from one or more noncontiguous buffers
50 .SH SYNOPSIS
51 .LP
52 .nf
53 #include <xti.h>
54
55
56
57
58 \fBint\fR \fBt_sndvudata\fR(\fBint\fR \fIfd\fR, \fBstruct t_unitdata *\fR\fIunitdata\fR, \fBstruct t_iovec *\fR\fIiov\fR,
59 \fBunsigned int\fR \fIiovcount\fR);
60 .fi
61
62 .SH DESCRIPTION
63 .sp
64 .LP
65 This function is used in connectionless mode to send a data unit to another
66 transport user. The argument \fIfd\fR identifies the local transport endpoint
67 through which data will be sent, \fIiovcount\fR contains the number of
68 non-contiguous \fIudata\fR buffers and is limited to an implementation-defined
69 value given by \fBT_IOV_MAX\fR which is at least 16, and \fIunitdata\fR
70 points to a \fBt_unitdata\fR structure containing the following members:
71 .sp
72 .in +2
73 .nf
74 struct netbuf addr;
75 struct netbuf opt;
76 struct netbuf udata;
77 .fi
78 .in -2
79
80 .sp
81 .LP
82 If the limit on \fIiovcount\fR is exceeded, the function fails with
83 \fBTBADDATA\fR.
114 .LP
115 By default, \fBt_sndvudata()\fR operates in synchronous mode and may wait if
116 flow control restrictions prevent the data from being accepted by the local
117 transport provider at the time the call is made. However, if \fBO_NONBLOCK\fR
118 is set by means of \fBt_open\fR(3NSL) or \fBfcntl\fR(2), \fBt_sndvudata()\fR
119 executes in asynchronous mode and will fail under such conditions. The process
120 can arrange to be notified of the clearance of a flow control restriction by
121 means of either \fBt_look\fR(3NSL) or the EM interface.
122 .sp
123 .LP
124 If the amount of data specified in \fIiov\fR\fB0\fR\fI\fR through \fIiov
125 [iovcount-1]\fR exceeds the TSDU size as returned in the \fItsdu\fR field of
126 the \fIinfo\fR argument of \fBt_open\fR(3NSL) or \fBt_getinfo\fR(3NSL), or is
127 zero and sending of zero octets is not supported by the underlying transport
128 service, a \fBTBADDATA\fR error is generated. If \fBt_sndvudata()\fR is
129 called before the destination user has activated its transport endpoint (see
130 \fBt_bind\fR(3NSL)\|), the data unit may be discarded.
131 .sp
132 .LP
133 If it is not possible for the transport provider to immediately detect the
134 conditions that cause the errors \fBTBADDADDR\fR and \fBTBADOPT\fR, these
135 errors will alternatively be returned by \fBt_rcvuderr\fR(3NSL). An
136 application must therefore be prepared to receive these errors in both of these
137 ways.
138 .SH RETURN VALUES
139 .sp
140 .LP
141 Upon successful completion, a value of \fB0\fR is returned. Otherwise, a value
142 of -1 is returned and \fBt_errno\fR is set to indicate an error.
143 .SH VALID STATES
144 .sp
145 .LP
146 \fBT_IDLE\fR.
147 .SH ERRORS
148 .sp
149 .LP
150 On failure, \fBt_errno\fR is set to one of the following:
151 .sp
152 .ne 2
153 .na
154 \fB\fBTBADADDR\fR\fR
155 .ad
156 .RS 15n
157 The specified protocol address was in an incorrect format or contained illegal
158 information.
159 .RE
160
161 .sp
162 .ne 2
163 .na
164 \fB\fBTBADDATA\fR\fR
165 .ad
166 .RS 15n
167 Illegal amount of data.
168 .RS +4
242 .ne 2
243 .na
244 \fB\fBTPROTO\fR\fR
245 .ad
246 .RS 15n
247 This error indicates that a communication problem has been detected between XTI
248 and the transport provider for which there is no other suitable XTI error
249 \fB(t_errno)\fR.
250 .RE
251
252 .sp
253 .ne 2
254 .na
255 \fB\fBTSYSERR\fR\fR
256 .ad
257 .RS 15n
258 A system error has occurred during execution of this function.
259 .RE
260
261 .SH TLI COMPATIBILITY
262 .sp
263 .LP
264 In the \fBTLI\fR interface definition, no counterpart of this routine was
265 defined.
266 .SH ATTRIBUTES
267 .sp
268 .LP
269 See \fBattributes\fR(5) for descriptions of the following attributes:
270 .sp
271
272 .sp
273 .TS
274 box;
275 c | c
276 l | l .
277 ATTRIBUTE TYPE ATTRIBUTE VALUE
278 _
279 MT Level Safe
280 .TE
281
282 .SH SEE ALSO
283 .sp
284 .LP
285 \fBfcntl\fR(2), \fBt_alloc\fR(3NSL), \fBt_open\fR(3NSL),
286 \fBt_rcvudata\fR(3NSL), \fBt_rcvvudata\fR(3NSL) \fBt_rcvuderr\fR(3NSL),
287 \fBt_sndudata\fR(3NSL), \fBattributes\fR(5)
|
43 .\" Portions Copyright 1989 AT&T
44 .\" Copyright 1994, The X/Open Company Ltd. All Rights Reserved.
45 .\" Portions Copyright (c) 1998, Sun Microsystems, Inc. All Rights Reserved.
46 .\"
47 .TH T_SNDVUDATA 3NSL "Aug 23, 2001"
48 .SH NAME
49 t_sndvudata \- send a data unit from one or more noncontiguous buffers
50 .SH SYNOPSIS
51 .LP
52 .nf
53 #include <xti.h>
54
55
56
57
58 \fBint\fR \fBt_sndvudata\fR(\fBint\fR \fIfd\fR, \fBstruct t_unitdata *\fR\fIunitdata\fR, \fBstruct t_iovec *\fR\fIiov\fR,
59 \fBunsigned int\fR \fIiovcount\fR);
60 .fi
61
62 .SH DESCRIPTION
63 .LP
64 This function is used in connectionless mode to send a data unit to another
65 transport user. The argument \fIfd\fR identifies the local transport endpoint
66 through which data will be sent, \fIiovcount\fR contains the number of
67 non-contiguous \fIudata\fR buffers and is limited to an implementation-defined
68 value given by \fBT_IOV_MAX\fR which is at least 16, and \fIunitdata\fR
69 points to a \fBt_unitdata\fR structure containing the following members:
70 .sp
71 .in +2
72 .nf
73 struct netbuf addr;
74 struct netbuf opt;
75 struct netbuf udata;
76 .fi
77 .in -2
78
79 .sp
80 .LP
81 If the limit on \fIiovcount\fR is exceeded, the function fails with
82 \fBTBADDATA\fR.
113 .LP
114 By default, \fBt_sndvudata()\fR operates in synchronous mode and may wait if
115 flow control restrictions prevent the data from being accepted by the local
116 transport provider at the time the call is made. However, if \fBO_NONBLOCK\fR
117 is set by means of \fBt_open\fR(3NSL) or \fBfcntl\fR(2), \fBt_sndvudata()\fR
118 executes in asynchronous mode and will fail under such conditions. The process
119 can arrange to be notified of the clearance of a flow control restriction by
120 means of either \fBt_look\fR(3NSL) or the EM interface.
121 .sp
122 .LP
123 If the amount of data specified in \fIiov\fR\fB0\fR\fI\fR through \fIiov
124 [iovcount-1]\fR exceeds the TSDU size as returned in the \fItsdu\fR field of
125 the \fIinfo\fR argument of \fBt_open\fR(3NSL) or \fBt_getinfo\fR(3NSL), or is
126 zero and sending of zero octets is not supported by the underlying transport
127 service, a \fBTBADDATA\fR error is generated. If \fBt_sndvudata()\fR is
128 called before the destination user has activated its transport endpoint (see
129 \fBt_bind\fR(3NSL)\|), the data unit may be discarded.
130 .sp
131 .LP
132 If it is not possible for the transport provider to immediately detect the
133 conditions that cause the errors \fBTBADADDR\fR and \fBTBADOPT\fR, these
134 errors will alternatively be returned by \fBt_rcvuderr\fR(3NSL). An
135 application must therefore be prepared to receive these errors in both of these
136 ways.
137 .SH RETURN VALUES
138 .LP
139 Upon successful completion, a value of \fB0\fR is returned. Otherwise, a value
140 of -1 is returned and \fBt_errno\fR is set to indicate an error.
141 .SH VALID STATES
142 .LP
143 \fBT_IDLE\fR.
144 .SH ERRORS
145 .LP
146 On failure, \fBt_errno\fR is set to one of the following:
147 .sp
148 .ne 2
149 .na
150 \fB\fBTBADADDR\fR\fR
151 .ad
152 .RS 15n
153 The specified protocol address was in an incorrect format or contained illegal
154 information.
155 .RE
156
157 .sp
158 .ne 2
159 .na
160 \fB\fBTBADDATA\fR\fR
161 .ad
162 .RS 15n
163 Illegal amount of data.
164 .RS +4
238 .ne 2
239 .na
240 \fB\fBTPROTO\fR\fR
241 .ad
242 .RS 15n
243 This error indicates that a communication problem has been detected between XTI
244 and the transport provider for which there is no other suitable XTI error
245 \fB(t_errno)\fR.
246 .RE
247
248 .sp
249 .ne 2
250 .na
251 \fB\fBTSYSERR\fR\fR
252 .ad
253 .RS 15n
254 A system error has occurred during execution of this function.
255 .RE
256
257 .SH TLI COMPATIBILITY
258 .LP
259 In the \fBTLI\fR interface definition, no counterpart of this routine was
260 defined.
261 .SH ATTRIBUTES
262 .LP
263 See \fBattributes\fR(5) for descriptions of the following attributes:
264 .sp
265
266 .sp
267 .TS
268 box;
269 c | c
270 l | l .
271 ATTRIBUTE TYPE ATTRIBUTE VALUE
272 _
273 MT Level Safe
274 .TE
275
276 .SH SEE ALSO
277 .LP
278 \fBfcntl\fR(2), \fBt_alloc\fR(3NSL), \fBt_open\fR(3NSL),
279 \fBt_rcvudata\fR(3NSL), \fBt_rcvvudata\fR(3NSL) \fBt_rcvuderr\fR(3NSL),
280 \fBt_sndudata\fR(3NSL), \fBattributes\fR(5)
|