t_open.3 (2010 09)

t
t_open(3) t_open(3)
A value of zero specifies that the transport provider does not support the concept of
TSDU, although it does support the sending of a data stream with no logical boundaries
preserved across a connection.
A value of − 1 specifies that there is no limit on the size of a TSDU.
A value of −2 specifies that the transfer of normal data is not supported by the transport
provider.
etsdu A value greater than zero specifies the maximum size of an expedited transport service
data unit (ETSDU).
A value of zero specifies that the transport provider does not support the concept of
ETSDU, although it does support the sending of an expedited data stream with no logical
boundaries preserved across a connection.
A value of − 1 specifies that there is no limit on the size of an ETSDU.
A value of −2 specifies that the transfer of expedited data is not supported by the tran-
sport provider.
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 and 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 the underlying transport provider supports
the sending of zero-length TSDUs. See Appendix A, "ISO Transport Protocol Informa-
tion," of the CAE Specification X/Open Transport Interface (XTI) manual from X/Open
Company Limited for a discussion of the separate issue of zero-length fragments within a
TSDU.
If a transport user is concerned with protocol independence, the above sizes may be accessed to determine
how large the buffer 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 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 .
A single transport endpoint may support only one of the above services at one time.
If info is set to a null pointer by the transport user, no protocol information is returned by
t_open().
Obsolescent Interfaces
When using TCP and UDP through HP XTI, name can be
/dev/inet_cots and /dev/inet_clts,
respectively. These names are supported for backward-compatibility purposes. They might not be
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2010