HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
QUERY_LU_0_TO_3
Fully qualified name of the partner LU.
wildcard_fqplu
Flag indicating whether the fq_partner_lu parameter contains a full or partial wildcard. Possible values are:
AP_YES
The fq_partner_lu parameter contains a full or partial wildcard.
AP_NO
The fq_partner_lu parameter does not contain a full or partial wildcard.
ls_name
Name of the link station used for sessions between the LU specified in the lu_name parameter and the partner
LU specified in the fq_plu_name parameter.
3.130.4 Returned Parameters: Parameter Check
If the verb does not execute because of a parameter error, SNAplus2 returns the following parameters:
primary_rc
AP_PARAMETER_CHECK
secondary_rc
Possible values are:
AP_INVALID_LU_NAME
The list_options parameter was set to
AP_LIST_INCLUSIVE, but the value specified for the lu_name
paraemter did not match any exisiting LS routing data record.
AP_INVALID_PARTNER_LU_NAME
The list_options parameter was set to AP_LIST_INCLUSIVE, but the value specified by the
fq_partner_lu parameter did not match any existing LS routing data record for the specified partner LU
name.
AP_INVALID_WILDCARD_NAME
The wildcard_fqplu parameter was set to AP_YES, but the fq_partner_lu parameter was not a valid
wildcard name.
AP_INVALID_LIST_OPTION
The list_options parameter was not set to a valid value.
Appendix B, Common Return Codes lists further secondary return codes associated with
AP_PARAMETER_CHECK,
which are common to all NOF verbs.
3.130.5 Returned Parameters: Other Conditions
Appendix B, Common Return Codes lists further combinations of primary and secondary return codes that are
common to all NOF verbs.
3.131 QUERY_LU_0_TO_3
QUERY_LU_0_TO_3 returns information about local LUs of type 0, 1, 2, or 3. This information is structured as
“determined data” (data gathered dynamically during execution, returned only if the node is active) and “defined
data” (the data supplied by the application on DEFINE_LU_0_TO_3).
514