HP-UX SNAplus2 R7 NOF Programmer's Guide

Appendix BCommon Return Codes
AP_INVALID_VERB_SEGMENT
The verb control block extended beyond the end of a data segment. The verb did not execute.
A secondary return code is not returned.
B.5 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
One of the following:
AP_INVALID_FORMAT
The reserved parameter format was not set to zero.
AP_INVALID_TARGET_HANDLE
The supplied target handle is not valid.
AP_INVALID_TARGET
The verb cannot be issued to the specified target. For example, QUERY_PARTNER_LU, which returns
information about an LU’s current usage, can be issued only to a running node; it is not valid when
issued to a file.
AP_INVALID_TARGET_MODE
The verb cannot be issued in the current mode. For example, only QUERY_* verbs can be issued in
read-only mode; DEFINE_*, DELETE_*, START_*, and STOP_* verbs are not valid in this mode.
AP_NOT_SERVER
This return code occurs only when you are running the NOF application program on a client. The verb
that you issued is not valid on a client; it can be issued only on a server.
AP_SYNC_NOT_ENABLED
The application issued this verb within a callback routine, using the synchronous NOF entry point. Any
verb issued from a callback routine must use the asynchronous entry point.
B.6 State Check
If the verb does not execute because of a state check, SNAplus2 returns the following parameters.
primary_rc
AP_STATE_CHECK
secondary_rc
One of the following:
AP_CANT_MODIFY_VISIBILITY
You have attempted to define a resource with a name that is reserved for use internally by SNAplus2.
Please choose a different name.
823