HP-UX Reference (11i v1 00/12) - 3 Library Functions N-Z (vol 7)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man3/nan.3m
________________________________________________________________
___ ___
t
t_optmgmt(3) t_optmgmt(3)
For each level, the option T_ALLOPT can be requested on input. All supported options of
this level with their default values are then returned. In this case, ret->opt.maxlen must
be given at least the value info->options (see t_getinfo(3), t_open(3)) before the call.
T_CURRENT This action enables the transport user to retrieve the currently effective option values.
The user specifies the options of interest in req->opt.buf. The option values are irrelevant
and will be ignored; it is sufficient to specify the t_opthdr part of an option only. The
default values are then returned in ret->opt.buf.
The status field returned is one of the following:
T_NOTSUPPORT if the protocol level does not support this option or if the transport
user illegally requested a privileged option.
T_READONLY if the option is read-only.
T_SUCCESS in all other cases.
The overall result of the request is returned in ret->flags. This field contains the worst
single result, whereby the rating is the same as for T_NEGOTIATE.
For each level, the option T_ALLOPT can be requested on input. All supported options of
this level with their currently effective values are then returned.
The option T_ALLOPT can only be used with t_optmgmt() and the actions
T_NEGOTIATE, T_DEFAULT, and T_CURRENT. It can be used with any supported
level and addresses all supported options of this level. The option has no value; it con-
sists of a t_opthdr only. Since in a t_optmgmt() call only options of one level may
be addressed, this option should not be requested together with other options. The func-
tion returns as soon as this option has been processed.
Options are independently processed in the order they appear in the input option buffer.
If an option is multiply input, it depends on the implementation whether it is multiply
output or whether it is returned only once.
Transport providers may not be able to provide an interface capable of supporting
T_NEGOTIATE and/or T_CHECK functionalities. When this is the case, the error
[T_NOTSUPPORT] is returned.
The function t_optmgmt() may block under various circumstances and depending on the implementa-
tion. The function will block, for instance, if the protocol addressed by the call resides on a separate con-
troller. It may also block due to flow control constraints, i.e. if data set previously across this transport
endpoint has not yet been fully processed. If the function is interrupted by a signal, the option negotiations
that have been done so far may remain valid. The behavior of the function is not changed if
O_NONBLOCK is set.
XTI-Level Options
XTI level options are not specific for a particular transport provider. An XTI implementation supports
none, all or any subset of the options defined below. An implementation may restrict the use of any of
these options by offering them only in the privileged or read-only mode, or if fd relates to specific transport
providers.
The subsequent options are not association-related. They may be negotiated in all XTI states except
T_UNINIT.
The protocol level is XTI_GENERIC. For this level, the following options are defined. A request for
XTI_DEBUG is an absolute requirement. A request to activate XTI_LINGER is an absolute requirement;
the timeout value to this option is not. XTI_RCVBUF, XTI_RECVLOWAT, XTI_SNDBUF, and
XTI_SNDLOWAT are not absolute requirements.
XTI_DEBUG This option enables debugging. The values of this option are implementation- defined.
Debugging is disabled if the option is specified with "no value", i.e. with an option header
only.
The system supplies utilities to process the traces. Note that an implementation may
also provide other means for debugging.
XTI_LINGER This option is used to linger the execution of a
t_close() or close() if send data is
still queued in the send buffer. The option value specifies the linger period. If a
close() or t_close() is issued and the send buffer is not empty, the system
HP-UX Release 11i: December 2000 − 3 − Section 3−−939
___
___