|T_GETINFO(3NSL)||Networking Services Library Functions||T_GETINFO(3NSL)|
t_getinfo - get protocol-specific service information
#include <xti.h> int t_getinfo(int fd, struct t_info *info);
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, the tiuser.h header file must be used. Refer to the TLI COMPATIBILITY section for a description of differences between the two interfaces.
This function returns the current characteristics of the underlying transport protocol and/or transport connection associated with file descriptor fd. The info pointer is used to return the same information returned by t_open(3NSL), although not necessarily precisely the same values. This function enables a transport user to access this information during any phase of communication.
This argument points to a t_info structure which contains the following members:
t_scalar_t addr; /*max size in octets of the transport protocol address*/ t_scalar_t options; /*max number of bytes of protocol-specific options */ t_scalar_t tsdu; /*max size in octets of a transport service data unit */ t_scalar_t etsdu; /*max size in octets of an expedited transport service*/
/*data unit (ETSDU) */ t_scalar_t connect; /*max number of octets allowed on connection */
/*establishment functions */ t_scalar_t discon; /*max number of octets of data allowed on t_snddis() */
/*and t_rcvdis() functions */ t_scalar_t servtype; /*service type supported by the transport provider */ t_scalar_t flags; /*other info about the transport provider */
The values of the fields have the following meanings:
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(3NSL) 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 protocol option negotiation during connection establishment (the t_optmgmt(3NSL) call has no effect on the values returned by t_getinfo()). These values will only change from the values presented to t_open(3NSL) after the endpoint enters the T_DATAXFER state.
The servtype field of info specifies one of the following values on return:
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and t_errno is set to indicate an error.
ALL - apart from T_UNINIT.
On failure, t_errno is set to one of the following:
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.
The XTI interfaces use the header file, xti.h. TLI interfaces should not use this header. They should use the header:
The t_errno value TPROTO can be set by the XTI interface but not by the TLI interface.
For TLI, the t_info structure referenced by info lacks the following structure member:
t_scalar_t flags; /* other info about the transport provider */
This member was added to struct t_info in the XTI interfaces.
When a value of -1 is observed as the return value in various t_info structure members, it signifies that the transport provider can handle an infinite length buffer for a corresponding attribute, such as address data, option data, TSDU (octet size), ETSDU (octet size), connection data, and disconnection data. The corresponding structure members are addr, options, tsdu, estdu, connect, and discon, respectively.
See attributes(7) for descriptions of the following attributes:
|ATTRIBUTE TYPE||ATTRIBUTE VALUE|
|February 17, 2023||OmniOS|