HP-UX SNAplus2 R7 NOF Programmer's Guide

Appendix BCommon Return Codes
AP_FILE_LOCK_FAILED
The application issued SET_PROCESSING_MODE to change to commit mode, but SNAplus2 failed
to get a lock on the configuration file. This can be because another NOF API application or SNAplus2
component is already accessing the file.
AP_FILE_UNLOCK_FAILED
The application issued SET_PROCESSING_MODE to change from commit mode to one of the other
modes, but SNAplus2 failed to release its lock on the configuration file. In order to free the file when
this error occurs, SNAplus2 closes the application’s handle to the file. The application must issue
OPEN_FILE again, to obtain a new file handle, before attempting to issue any more verbs to this file.
AP_FILE_UNAVAILABLE
The connection to the target file has been lost.
AP_NOT_MASTER
The target file is a copy of the domain configuration file, or of the sna.net file, on a server that is
not the master server. Verbs that modify these files must be issued to the master server’s copy of the
files.
AP_SYNC_PENDING
This verb was issued using the synchronous NOF API entry point, but another synchronous verb was
in progress. Only one synchronous verb can be in progress at any time.
B.7 System Error
If the verb does not execute because of an operating system error, SNAplus2 returns the following parameters:
primary_rc
AP_UNEXPECTED_SYSTEM_ERROR
An operating system call failed during processing of the verb.
secondary_rc
The secondary return code in this case is the return code from the operating system call.
UNIX
For the meaning of the operating system return code, see the file /usr/include/errno.h on the computer
where the error occurred. Typically, the return code will indicate a condition such as memory shortage.
WINDOWS
For the meaning of the operating system return code, refer to your operating system documentation.
If the problem persists, consult your System Administrator.
If the verb was issued to change the target configuration (such as DEFINE_* or DELETE_*), or to perform
an action (such as START_*), the application should issue the appropriate QUERY_* verb to determine
whether the change or action succeeded. In particular, if this error occurs while processing a DEFINE_* or
DELETE_* verb containing multiple data structures (such as DEFINE_EMULATOR_USER), the change can
be incomplete(for example, some but not all of the user’s sessions may have been defined).
824