t_snddis(3N)
NAME
t_snddis − send user-initiated disconnection request
SYNOPSIS
cc [ flag ... ] file ... −lnsl [ library ... ]
#include <xti.h>
int t_snddis(int fd, const struct t_call ∗call);
DESCRIPTION
This routine is part of the XTI interfaces which evolved from the TLI interfaces. XTI represents the future evolution of these interfaces. However, TLI interfaces are supported for compatibility. When using a TLI routine that has the same name as an XTI routine, a different header file, tiuser.h , must be used. Refer to the section, TLI COMPATIBILITY , for a description of differences between the two interfaces.
This function is used to initiate an abortive release on an already established connection or to reject a connection request. fd identifies the local transport endpoint of the connection, and call specifies information associated with the abortive release. call points to a t_call structure, which contains the following members:
struct netbufaddr;
struct netbufopt;
struct netbufudata;
intsequence;
netbuf is described in t_connect(3N). The values in call have different semantics, depending on the context of the call to t_snddis(). When rejecting a connection request, call must be non-null pointer and must contain a valid value of sequence to uniquely identify the rejected connection indication to the transport provider. The sequence field is only meaningful if the transport connection is in the T_INCON state.
The addr and opt fields of call are ignored. In all other cases, call need only be used when data is being sent with the disconnection request. The addr, opt, and sequence fields of the t_call structure are ignored. If the user does not wish to send data to the remote user, the value of call may be a null pointer.
udata specifies the user data to be sent to the remote user. The amount of user data must not exceed the limits supported by the transport provider as returned in the discon field of the info argument of t_open(3N) or t_getinfo(3N). If the len field of udata is zero, no data will be sent to the remote user.
VALID STATES
Legitimate states (see t_getstate(3N)) for a call to this routine are:
T_DATAXFER
T_INCON with outstanding connection count (ocnt) greater than zero
T_INREL
T_OUTCON
T_OUTREL
RETURN VALUES
t_snddis() returns:
0 On success.
−1 On failure.
On failure, t_errno is set to indicate the error, and possibly errno is set.
ERRORS
On failure, t_errno is set to one of the following:
TBADDATA The amount of user data specified was not within the bounds allowed by the transport provider.
TBADF The specified file descriptor does not refer to a transport endpoint.
TBADSEQ An invalid sequence number was specified, or a null call pointer was specified when rejecting a connection request.
TLOOK An asynchronous event has occurred on this transport endpoint, for which handling is required before any progress can be made.
TNOTSUPPORT This function is not supported by the underlying transport provider.
TOUTSTATE The communications endpoint referenced by fd or resfd is not in one of the states in which a call to this function is valid.
TPROTO This error indicates that a communication problem has been detected between XTI and the transport provider for which there is no other suitable XTI t_errno value.
TSYSERR A system error has occurred during execution of this function, errno will be set to the specific error.
TLI COMPATIBILITY
The XTI and TLI interface definitions have common names but use different header files. This, and other semantic differences between the two interfaces are described in the subsections below.
Interface Header
The XTI interfaces use the header file, xti.h . TLI interfaces should not use this header. They should use the header:
#include <tiuser.h>
Error Description Values
The t_errno value that can be set by the XTI interface and cannot be set by the TLI interface is:
TPROTO
Option Buffers
The format of the options in an opt buffer is dictated by the transport provider. Unlike the XTI interface, the TLI interface does not fix the buffer format.
For more information refer to the Transport Interfaces Programming Guide.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
| MT-Level | MT-Safe |
SEE ALSO
t_connect(3N), t_getinfo(3N), t_listen(3N), t_open(3N), attributes(5)
Transport Interfaces Programming Guide
NOTES
t_snddis() is an abortive disconnection. Therefore a t_snddis() issued on a connection endpoint may cause data previously sent using t_snd(), or data not yet received, to be lost (even if an error is returned).
SunOS 5.6 — Last change: 10 Feb 1997