t_snddis(3)

NAME

t_snddis − send user-initiated disconnect request

SYNOPSIS

#include <xti.h> (for XTI)

#include <tiuser.h> (for TLI)

int t_snddis (fd, call)
int fd;
struct t_call *call;

DESCRIPTION

This function is used to initiate an abortive release on an already established connection or to reject a connect 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 netbuf addr;
struct netbuf opt;
struct netbuf udata;
int sequence;

The type netbuf structure is defined in the <xti.h> or <tiuser.h> header file. This structure, which is used to define buffer parameters, has the following members:

unsigned int maxlen maximum byte length of the data buffer

unsigned int len actual byte length of data written to buffer

char *buf points to buffer location

The values in call have different semantics, depending on the context of the call to t_snddis. When rejecting a connect request, call must be a non-null pointer and contain a valid value of sequence to uniquely identify the rejected connect indication to the transport provider. The sequence parameter is only meaningful, if the transport connection is in the T_INCON state (see t_getstate ). 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 disconnect 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(3) or t_getinfo(3). If the len field of udata is zero, no data will be sent to the remote user.

ERRORS

On failure, t_errno is set to one of the following:

[TBADF] The specified identifier does not refer to a transport endpoint.

[TOUTSTATE] This function was issued in the wrong sequence on the transport endpoint referenced by fd.

[TBADDATA] (XTI only) The amount of user data specified was not within the bounds allowed by the transport provider. Some outbound data queued for this endpoint may be lost.

[TBADSEQ] An invalid sequence was specified, or a null call pointer was specified when rejecting a connect request. Some outbound data queued for this endpoint may be lost.

[TLOOK] An asynchronous event has occurred on this transport endpoint and requires immediate attention.

[TNOTSUPPORT] This function is not supported by the underlying transport provider.

[TSYSERR] A system error has occurred during execution of this function.

RETURN VALUE

Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and t_errno is set to indicate the error.

NOTE

In HP-UX 9.0, XTI (X/Open Transport Interface) supports only OSI as a transport provider, and is available only as part of the OSI Transport Services 9000 product. Users of this product can access XTI versions of the t_* routines by linking with /usr/lib/libxti.a. For more information on XTI, see "HP-UX/9000 XTI Programmer’s Guide".

In HP-UX 9.0, TLI (Transport Layer Interface) supports any transport provider which is compliant with TPI (Transport Provider Interface). TLI is available only as part of the STREAMS product. Users of this product can access TLI versions of the t_* routines by linking with /usr/lib/libnsl_s.a. For more information on TLI, see the TLI section of "STREAMS/UX for HP 9000 Reference Manual".

Museum

Related Articles