 |
» |
|
|
|
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. - 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_NODE_NOT_CONFIGURED
The system has just been installed, and a DEFINE_NODE
verb has not yet been issued (or the Motif or ascii administration
tools have not yet been used to configure the node). You must do
this before issuing any other verbs. - 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.
|
Printable version
