HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
QUERY_LS
ls_detail.def_data.react_timer_retry
Retry count for reactivating a failed LS. This parameter is used to specify whether SNAplus2 should attempt
to reactivate the LS if it fails while in use (or if an attempt to start the LS fails).
Zero indicates that SNAplus2 should not attempt to reactivate the LS; a nonzero value specifies the number
of retries to be made. A value of
65,535 indicates that SNAplus2 should retry indefinitely until the LS is
activated.
SNAplus2 waits for the time specified by the react_timer parameter above between successive retries. If the
retry count is reached without successfully reactivating the LS, or if a STOP_LS is issued while SNAplus2 is
retrying the activation, no further retries are made; the LS remains inactive unless START_LS is issued for it.
If the auto_act_supp parameter is set to
AP_YES, the reactivation timer fields are ignored; if the link fails,
SNAplus2 does not attempt to reactivate it until the user application that was using the session attempts to
restart the session.
ls_detail.def_data.restart_on_normal_deact
Specifies whether SNAplus2 should attempt to reactivate the LS if it is deactivated normally by the remote
system. Possible values are:
AP_YES
If the remote system deactivates the LS normally, SNAplus2 attempts to reactivate it, using the same
retry timer and count values as for reactivating a failed LS (the react_timer and react_timer_retry
parameters above).
AP_NO
If the remote system deactivates the LS normally, SNAplus2 does not attempt to reactivate it.
If the LS is a host link (specified by the adj_cp_type parameter), or is automatically started when the node is
started (the initially_active parameter is set to AP_YES), this parameter is ignored; SNAplus2 always attempts
to reactivate the LS if it is deactivated normally by the remote system (unless react_timer_retry is zero).
ls_detail.def_data.port_name
Name of the port associated with this link station. This is an 8-byte ASCII string, padded on the right with
spaces if the name is shorter than 8 characters. If the link is to a VRN, this field specifies the name of the
actual port used to connect to the VRN (as specified in the DEFINE_CN verb).
ls_detail.def_data.adj_cp_name
Fully qualified name of the adjacent control point. This parameter is used only if adj_cp_type specifies that
the adjacent node is an APPN node or a back-level LEN node.
The name is a 17-byte EBCDIC string, padded on the right with EBCDIC spaces. It consists of a network ID
of 1–8 A-string characters, an EBCDIC dot (period) character, and a network name of 1–8 A-string characters.
ls_detail.def_data.adj_cp_type
Adjacent node type. This is one of the following:
AP_APPN_NODE
APPN-capable node; the node type will be learned during XID exchange.
AP_NETWORK_NODE
Network node, or Branch Network Node acting as a Network Node from the local node’s perspective.
AP_END_NODE
End node, Branch Network Node acting as an End Node from the local node’s perspective, or up-level
LEN node (one that includes the Network Name CV in its XID3).
AP_BACK_LEVEL_LEN_NODE
Back-level LEN node (one that does not include the Network Name CV in its XID3).
503