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

t
t_getinfo(3) t_getinfo(3)
connect A value greater than or equal to zero specifies the maximum amount of data that may be
associated with the connection establishment functions
t_connect() and
t_rcvconnect()
.
A value of −1 specifies that there is no limit on the amount of data sent during connection
establishment.
A value of −2 specifies that the transport provider does not allow data to be sent with con-
nection establishment functions.
discon A value greater than or equal to zero specifies the maximum amount of data that may be
associated with the
t_snddis() and t_rcvdis() functions.
A value of −1 specifies that there is no limit on the amount of data sent with these abor-
tive release functions.
A value of −2 specifies that the transport provider does not allow data to be sent with the
abortive release functions.
servtype This field specifies the service type supported by the transport provider, as described
below.
flags This is a bit field used to specify other information about the transport provider. If the
T_SENDZERO bit is set in flags, this indicates that the underlying transport provider
supports the sending of zero-length TSDUs. See Appendix A, "ISO Transport Protocol
Information" of the CAE Specification X/Open Transport Interface (XTI) manual for a dis-
cussion of the separate issue of zero-length fragments within a TSDU. Note: HP
currently does not support
T_SENDZERO flag within the timod module.
If a transport user is concerned with protocol independence, the above sizes may be accessed to determine
how large the buffers must be to hold each piece of information. Alternatively, the
t_alloc() function
may be used to allocate these buffers. An error will result if a transport user exceeds the allowed data size
on any function. The value of each field may change as a result of option negotiation, and
t_getinfo()
enables a user to retrieve the current characteristics of the underlying transport protocol.
The servtype field of info specifies one of the following values on return:
T_COTS The transport provider supports a connection-mode service but does not support the
optional orderly release facility.
T_COTS_ORD The transport provider supports a connection-mode service with the optional orderly
release facility.
T_CLTS The transport provider supports a connectionless-mode service. For this service type,
t_open() will return −2 for etsdu, connect, and discon.
Thread-Safeness
The t_getinfo() 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.
Valid States
All - apart from T_UNINIT.
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 the following
[TBADF] The specified identifier does not refer to a transport endpoint.
[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).
500 Hewlett-Packard Company − 2 − HP-UX 11i Version 2: December 2007 Update