1t_sndreldata(3NSL) Networking Services Library Functions t_sndreldata(3NSL)
2
6 t_sndreldata - initiate or respond to an orderly release with user data
7
9 #include <xti.h>
10 int t_sndreldata(int fd, struct t_discon *discon);
15
18 This function is used to initiate an orderly release of the outgoing
19 direction of data transfer and to send user data with the release. The
20 argument fd identifies the local transport endpoint where the connec‐
21 tion exists, and discon points to a t_discon structure containing
22 the following members:
23 struct netbuf udata;
25 int reason;
26 int sequence;
27 After calling t_sndreldata(), the user may not send any more data over
31 the connection. However, a user may continue to receive data if an
32 orderly release indication has not been received.
33 The field reason specifies the reason for the disconnection through a
36 protocol-dependent reason code, and udata identifies any user data
37 that is sent with the disconnection; the field sequence is not used.
38 The udata structure specifies the user data to be sent to the remote
41 user. The amount of user data must not exceed the limits supported by
42 the transport provider, as returned in the discon field of the info
43 argument of t_open(3NSL) or t_getinfo(3NSL). If the len field of
44 udata is zero or if the provider did not return T_ORDRELDATA in the
45 t_open(3NSL) flags, no data will be sent to the remote user.
46 If a user does not wish to send data and reason code to the remote
49 user, the value of discon may be a null pointer.
50 This function is an optional service of the transport provider, only
53 supported by providers of service type T_COTS_ORD. The flag T_ORDREL‐
54 DATA in the info→flag field returned by t_open(3NSL) or t_get‐
55 info(3NSL) indicates that the provider supports orderly release user
56 data.
57 This function may not be available on all systems.
60
62 Upon successful completion, a value of 0 is returned. Otherwise, a
63 value of -1 is returned and t_errno is set to indicate an error.
64
66 T_DATAXFER, T_INREL.
67
69 On failure, t_errno is set to one of the following:
70 TBADDATA The amount of user data specified was not within the
72 bounds allowed by the transport provider, or user data
73 was supplied and the provider did not return T_ORDREL‐
74 DATA in the t_open(3NSL) flags.
75 TBADF The specified file descriptor does not refer to a trans‐
78 port endpoint.
79 TFLOW O_NONBLOCK was set, but the flow control mechanism pre‐
82 vented the transport provider from accepting the func‐
83 tion at this time.
84 TLOOK An asynchronous event has occurred on this transport
87 endpoint and requires immediate attention.
88 TNOTSUPPORT Orderly release is not supported by the underlying
91 transport provider.
92 TOUTSTATE The communications endpoint referenced by fd is not in
95 one of the states in which a call to this function is
96 valid.
97 TPROTO This error indicates that a communication problem has
100 been detected between XTI and the transport provider for
101 which there is no other suitable XTI error (t_errno).
102 TSYSERR A system error has occurred during execution of this
105 function.
106
109 In the TLI interface definition, no counterpart of this routine was
110 defined.
111
113 See attributes(5) for descriptions of the following attributes:
114 ┌─────────────────────────────┬─────────────────────────────┐
119 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
120 ├─────────────────────────────┼─────────────────────────────┤
121 │MT Level │Safe │
122 └─────────────────────────────┴─────────────────────────────┘
123
125 t_getinfo(3NSL), t_open(3NSL), t_rcvrel(3NSL), t_rcvreldata(3NSL),
126 t_sndrel(3NSL), attributes(5)
127
129 The interfaces t_sndreldata() and t_rcvreldata(3NSL) are only for use
130 with a specific transport called "minimal OSI," which is not available
131 on the Solaris platform. These interfaces are not available for use in
132 conjunction with Internet Transports (TCP or UDP).
133SunOS 5.11 7 May 1998 t_sndreldata(3NSL)