High Availability Monitors Version A.03.02 Release Notes

Writing NOF Applications
Target For NOF Verbs
Chapter 2 107
• START_* and STOP_* verbs, to start and stop node resources, must
be issued to a running node.
• Verbs associated with domain resources, such as
DEFINE_EMULATOR_USER, must be issued to the domain
configuration file.
• Different QUERY_* verbs return information about the definition of a
resource, on its current status, or on both definition and status.
Status information can only be obtained from a running node. Verbs
that return only status information cannot be issued to an inactive
node, and verbs that return both definition and status will return
only definition information when issued to an inactive node. For
example, QUERY_PARTNER_LU_DEFINITION can be issued either
to an inactive node (to determine the stored configuration) or to a
running node (to determine the current definition). However,
QUERY_PARTNER_LU (which returns information about the LU's
current sessions) can be issued only to a running node. QUERY_LS
(which returns both the definition of the LS and its current status)
can be issued either to an inactive node or to a running node, but
status information is not returned if you issue it to an inactive node.
The description of each QUERY_* verb in Chapter 3, “NOF API Verbs
(ACTIVATE_SESSION to OPEN_FILE),” includes information about
the valid target types for the verb.
• Verbs associated with managing backup master servers
(ADD_BACKUP, DELETE_BACKUP, QUERY_SNA_NET,
REGISTER_INDICATION_SINK and
UNREGISTER_INDICATION_SINK for SNA network file
indications) must be issued to the sna.net file.
Processing Modes
Each target handle used by an application has an associated processing
mode that can be modified with the NOF verb
SET_PROCESSING_MODE. The mode controls file locking and access
permissions for the application. The following modes are available:
AP_READ_ONLY Only QUERY_* verbs are enabled in this mode. All
other verbs, which modify the configurationor status of
a resource, will be rejected.
This is the default mode when the target handle is first
assigned; it enables the application to check the
configuration or status of a resource but not to change