2 .\" Copyright 1994, The X/Open Company Ltd. All Rights Reserved Portions Copyright 1989 AT&T Portions Copyright (c) 1998, Sun Microsystems, Inc. All Rights Reserved
3 .\" Sun Microsystems, Inc. gratefully acknowledges The Open Group for permission to reproduce portions of its copyrighted documentation. Original documentation from The Open Group can be obtained online at
4 .\" http://www.opengroup.org/bookstore/.
5 .\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
6 .\" This notice shall appear on any product containing this material.
7 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
8 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
9 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
10 .TH T_SNDREL 3NSL "May 7, 1998"
12 t_sndrel \- initiate an orderly release
20 \fBint\fR \fBt_sndrel\fR(\fBint\fR \fIfd\fR);
26 This routine is part of the \fBXTI\fR interfaces which evolved from the
27 \fBTLI\fR interfaces. \fBXTI\fR represents the future evolution of these
28 interfaces. However, \fBTLI\fR interfaces are supported for compatibility. When
29 using a \fBTLI\fR routine that has the same name as an \fBXTI\fR routine, the
30 \fBtiuser.h\fR header file must be used. Refer to the \fBTLI\fR
31 \fBCOMPATIBILITY\fR section for a description of differences between the two
35 For transport providers of type \fBT_COTS_ORD,\fR this function is used to
36 initiate an orderly release of the outgoing direction of data transfer and
37 indicates to the transport provider that the transport user has no more data to
38 send. The argument \fIfd\fR identifies the local transport endpoint where the
39 connection exists. After calling \fBt_sndrel()\fR, the user may not send any
40 more data over the connection. However, a user may continue to receive data if
41 an orderly release indication has not been received. For transport providers of
42 types other than \fBT_COTS_ORD,\fR this function fails with error
47 Upon successful completion, a value of \fB0\fR is returned. Otherwise, a
48 value of -1 is \fBreturned\fR and \fBt_errno\fR is set to indicate an error.
52 \fBT_DATAXFER\fR, \fBT_INREL\fR.
56 On failure, \fBt_errno\fR is set to one of the following:
63 The specified file descriptor does not refer to a transport endpoint.
72 \fBO_NONBLOCK\fR was set, but the flow control mechanism prevented the
73 transport provider from accepting the function at this time.
82 An asynchronous event has occurred on this transport endpoint and requires
89 \fB\fBTNOTSUPPORT\fR\fR
92 This function is not supported by the underlying transport provider.
101 The communications endpoint referenced by \fIfd\fR is not in one of the states
102 in which a call to this function is valid.
111 This error indicates that a communication problem has been detected between XTI
112 and the transport provider for which there is no other suitable XTI error
122 A system error has occurred during execution of this function.
125 .SH TLI COMPATIBILITY
128 The \fBXTI\fR and \fBTLI\fR interface definitions have common names but use
129 different header files. This, and other semantic differences between the two
130 interfaces are described in the subsections below.
131 .SS "Interface Header"
134 The \fBXTI\fR interfaces use the header file, \fBxti.h\fR. \fBTLI\fR interfaces
135 should \fInot\fR use this header. They should use the header:
140 .SS "Error Description Values"
143 The \fBt_errno\fR values that can be set by the \fBXTI\fR interface and cannot
144 be set by the \fBTLI\fR interface are:
160 Whenever this function fails with \fBt_error\fR set to \fBTFLOW,\fR
161 \fBO_NONBLOCK\fR must have been set.
165 See \fBattributes\fR(5) for descriptions of the following attributes:
173 ATTRIBUTE TYPE ATTRIBUTE VALUE
181 \fBt_error\fR(3NSL), \fBt_getinfo\fR(3NSL), \fBt_open\fR(3NSL),
182 \fBt_rcvrel\fR(3NSL), \fBattributes\fR(5)