HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
QUERY_LS
/* received */
AP_UINT32 out_session_control_frames; /* number of control frames */
/* sent */
AP_UINT32 echo_rsps; /* reserved */
AP_UINT32 current_delay; /* reserved */
AP_UINT32 max_delay; /* reserved */
AP_UINT32 min_delay; /* reserved */
AP_UINT32 max_delay_time; /* reserved */
AP_UINT32 good_xids; /* successful XID on LS count */
AP_UINT32 bad_xids; /* unsuccessful XID on LS count */
} LS_STATS;
For more details of the link-specific data, see Section 3.29, DEFINE_LS. The data structure for this data follows
the
ls_def_data
structure, but is padded to start on a 4-byte boundary.
3.129.2 Supplied Parameters
The application supplies the following parameters:
opcode
AP_QUERY_LS
buf_ptr
A pointer to a data buffer that SNAplus2 will use to return the requested information.
buf_size
Size of the supplied data buffer.
num_entries
Maximum number of LSs for which data should be returned. To request data for a specific LS rather than a
range, specify the value 1. To return as many entries as possible, specify zero; in this case, SNAplus2 will
return the maximum number of entries that can be accommodated in the supplied data buffer.
list_options
The position in the list from which SNAplus2 should begin to return data, and the level of information required
for each entry. Specify the level of information with one of the following values:
AP_SUMMARY
Summary information only.
AP_DETAIL
Detailed information.
Combine this value using a logical OR operation with one of the following values:
AP_FIRST_IN_LIST
Start at the first entry in the list.
AP_LIST_INCLUSIVE
Start at the entry specified by the ls_name parameter.
AP_LIST_FROM_NEXT
Start at the entry immediately following the entry specified by the ls_name parameter.
For more information about how the list is ordered and how the application can obtain specific entries from
it, see Section 2.7, List Options For QUERY_* Verbs.
493