HPlogo HP-UX Reference Volume 4 of 5 > t

t_getstate(3)

» 

Technical documentation

Complete book in PDF

 » Table of Contents

 » Index

NAME

t_getstate() — get the current state

SYNOPSIS

#include <xti.h> /* for X/OPEN Transport Interface - XTI */ /* or */ #include <tiuser.h> /* for Transport Layer Interface - TLI */ int t_getstate (fd); int fd;

DESCRIPTION

The t_getstate() function returns the current state of the provider as seen by the application associated with the transport endpoint specified by fd.

Thread-Safeness

The t_getstate() 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-signal safe. Finally, it is not fork-safe.

RETURN VALUE

State is returned upon successful completion. Otherwise, a value of -1 it returned and t_errno is set to indicate the error. The current state is one of the following:

T_UNBND

unbound

T_IDLE

idle

T_OUTCON

outgoing connection pending

T_INCON

incoming connection pending

T_DATAXFER

data transfer

T_OUTREL

outgoing orderly release (waiting for an orderly release indication).

T_INREL

incoming orderly release (waiting for an orderly release request).

If the provider is undergoing a state transition when t_getstate() is called, the function will fail.

ERRORS

On failure, t_errno is set to the following:

[TBADF]

The specified identifier does not refer to a transport endpoint.

[TSTATECHNG]

The transport provider is undergoing a transient state change.

[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 suitable XTI (t_errno).

SEE ALSO

t_open(3).

STANDARDS CONFORMANCE

t_getstate(): SVID2, XPG3, XPG4

© Hewlett-Packard Development Company, L.P.