HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
DEFINE_FOCAL_POINT
The supplied category name contained a character that was not valid.
AP_INVALID_FP_NAME
The fully qualified name or the application name 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.26.5 Returned Parameters: Function Not Supported
If the verb does not execute successfully because the local node configuration does not support it, SNAplus2 returns
the following parameters:
primary_rc
AP_FUNCTION_NOT_SUPPORTED
The local node does not support MS network management functions; this is defined by the
mds_supported parameter on the DEFINE_NODE verb.
3.26.6 Returned Parameters: Replaced
If the verb does not execute successfully because it is followed by another verb specifying a different focal point,
SNAplus2 returns the following parameters.
primary_rc
AP_REPLACED
Another DEFINE_FOCAL_POINT was issued to the same node while this verb was outstanding,
specifying a different focal point for the same MS category. This verb was abandoned; the node will
attempt to contact the focal point specified by the second verb.
3.26.7 Returned Parameters: Unsuccessful
If the verb does not execute successfully because the focal point relationship cannot be established, SNAplus2
returns the following parameters:
primary_rc
AP_UNSUCCESSFUL
secondary_rc
Possible values are:
AP_IMPLICIT_REQUEST_REJECTED
The specified focal point rejected the request.
AP_IMPLICIT_REQUEST_FAILED
The node could not send the request to the specified focal point; this may be because the specified
control point or application was not found.
3.26.8 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.
158