HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
DEFINE_DSPU_TEMPLATE
primary_rc
AP_PARAMETER_CHECK
secondary_rc
Possible values are:
AP_INVALID_TEMPLATE_NAME
The name specified for the template_name parameter was not valid.
AP_INVALID_NAU_ADDRESS
The min_nau or max_nau parameter was not valid.
AP_INVALID_NAU_RANGE
The address specified on the min_nau or max_nau parameters was not in the valid range.
AP_CLASHING_NAU_RANGE
The range of addresses specified by the min_nau parameter through the max_nau parameter in a
dslu_template
subrecord clashes with a range specified by another
dslu_template subrecord in the template
named by the template_name parameter.
AP_INVALID_NUM_DSPU_TEMPLATES
The value specified for the num_of_dslu_templates parameter was not in the valid range.
AP_INVALID_ALLOW_TIMEOUT
The value specified for the allow_timeout parameter was not valid.
AP_INVALID_DELAYED_LOGON
The value specified for the delayed_logon parameter was not valid.
AP_INVALID_MODIFY_TEMPLATE
The value specified for the modify_template parameter was not valid.
Appendix B, Common Return Codes lists further secondary return codes associated with
AP_PARAMETER_CHECK,
which are common to all NOF verbs.
3.24.5 Returned Parameters: State Check
If the verb does not execute because of a state error, SNAplus2 returns the following parameters.
primary_rc
AP_STATE_CHECK
secondary_rc
Possible values are:
AP_INVALID_HOST_LU_NAME
The specified host_lu_name parameter value was not valid.
Appendix B, Common Return Codes lists further secondary return codes associated with
AP_STATE_CHECK, which
are common to all NOF verbs.
3.24.6 Returned Parameters: Function Not Supported
If the verb does not execute successfully because the local node’s configuration does not support it, SNAplus2
returns the following parameters:
primary_rc
AP_FUNCTION_NOT_SUPPORTED
149