1t_sndrel(3NSL) Networking Services Library Functions t_sndrel(3NSL)
2
3
4
6 t_sndrel - initiate an orderly release
7
9 #include <xti.h>
10
11
12
13 int t_sndrel(int fd);
14
15
17 This routine is part of the XTI interfaces which evolved from the TLI
18 interfaces. XTI represents the future evolution of these interfaces.
19 However, TLI interfaces are supported for compatibility. When using a
20 TLI routine that has the same name as an XTI routine, the tiuser.h
21 header file must be used. Refer to the TLI COMPATIBILITY section for
22 a description of differences between the two interfaces.
23
24
25 For transport providers of type T_COTS_ORD, this function is used to
26 initiate an orderly release of the outgoing direction of data transfer
27 and indicates to the transport provider that the transport user has no
28 more data to send. The argument fd identifies the local transport end‐
29 point where the connection exists. After calling t_sndrel(), the user
30 may not send any more data over the connection. However, a user may
31 continue to receive data if an orderly release indication has not been
32 received. For transport providers of types other than T_COTS_ORD, this
33 function fails with error TNOTSUPPORT.
34
36 Upon successful completion, a value of 0 is returned. Otherwise, a
37 value of -1 is returned and t_errno is set to indicate an error.
38
40 T_DATAXFER, T_INREL.
41
43 On failure, t_errno is set to one of the following:
44
45 TBADF The specified file descriptor does not refer to a trans‐
46 port endpoint.
47
48
49 TFLOW O_NONBLOCK was set, but the flow control mechanism pre‐
50 vented the transport provider from accepting the func‐
51 tion at this time.
52
53
54 TLOOK An asynchronous event has occurred on this transport
55 endpoint and requires immediate attention.
56
57
58 TNOTSUPPORT This function is not supported by the underlying trans‐
59 port provider.
60
61
62 TOUTSTATE The communications endpoint referenced by fd is not in
63 one of the states in which a call to this function is
64 valid.
65
66
67 TPROTO This error indicates that a communication problem has
68 been detected between XTI and the transport provider for
69 which there is no other suitable XTI error (t_errno).
70
71
72 TSYSERR A system error has occurred during execution of this
73 function.
74
75
77 The XTI and TLI interface definitions have common names but use differ‐
78 ent header files. This, and other semantic differences between the two
79 interfaces are described in the subsections below.
80
81 Interface Header
82 The XTI interfaces use the header file, xti.h. TLI interfaces should
83 not use this header. They should use the header:
84 #include <tiuser.h>
85
86 Error Description Values
87 The t_errno values that can be set by the XTI interface and cannot be
88 set by the TLI interface are:
89 TPROTO
90 TLOOK
91 TOUTSTATE
92
93 Notes
94 Whenever this function fails with t_error set to TFLOW, O_NONBLOCK must
95 have been set.
96
98 See attributes(5) for descriptions of the following attributes:
99
100
101
102
103 ┌─────────────────────────────┬─────────────────────────────┐
104 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
105 ├─────────────────────────────┼─────────────────────────────┤
106 │MT Level │Safe │
107 └─────────────────────────────┴─────────────────────────────┘
108
110 t_error(3NSL), t_getinfo(3NSL), t_open(3NSL), t_rcvrel(3NSL),
111 attributes(5)
112
113
114
115SunOS 5.11 7 May 1998 t_sndrel(3NSL)