HP-UX Reference (11i v1 00/12) - 3 Library Functions N-Z (vol 7)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

461

462

463

464

465

466

467

468

469

470

__________________________________________________________________________________________________________________________________________________________________________________________________

STANDARD Printed by: Nora Chuang [nchuang] STANDARD

/build/1111/BRICK/man3/nan.3m

________________________________________________________________

___ ___

t_sndrel(3) t_sndrel(3)

NAME

t_sndrel() - initiate an orderly release

SYNOPSIS

#include <xti.h> /* for X/OPEN Transport Interface - XTI */

/* or */

#include <tiuser.h> /* for Transport Layer Interface - TLI */

int t_sndrel (fd);

int fd;

DESCRIPTION

The t_sndrel() function is used in connection-oriented mode to initiate an orderly release at a tran-

sport endpoint speciﬁed by fd, which is a ﬁle descriptor previously returned by the t_open() function.

After this orderly release is indicated, the transport user should not try to send more data through that

transport endpoint. An attempt to send more data to a released transport endpoint may block continu-

ously. However, the transport user may continue to receive data over the connection until an orderly

release indication is received. This function is an optional service of the transport provider and is only sup-

ported if the transport provider returned service type T_COTS_ORD

on t_open() or t_getinfo().

Thread-Safeness

The

t_sndrel() function is safe to be called by multithreaded applications, and it is thread-safe for both

POSIX Threads and DCE User Threads. It has a cancellation point. It is neither async-cancel safe nor

async-signalsafe. Finally, it is not fork-safe.

Note

HP OSI XTI does not support t_sndrel() .

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.

ERRORS

On failure,

t_errno is set to one of the following:

[TBADF] The speciﬁed identiﬁer does not refer to a transport endpoint.

[TFLOW] Asynchronous mode is indicated because O_NONBLOCK was set, but the transport

provider cannot accept a release because of ﬂow-control restrictions.

[TLOOK] An asynchronous event has occurred on this transport endpoint and requires immedi-

ate attention.

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

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

[TPROTO] (XTI only) 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).