High Availability Monitors Version A.03.02 Release Notes

Writing NOF Applications
Description of the NOF API Entry Points
Chapter 298
described in “Using the Callback Routine for Indications”). The callback
routine can perform all the necessary processing on the returned
parameters, or it can simply set a variable to inform the NOF application
that the verb has completed.
Returned Values
The callback function does not return any values.
Using the Callback Routine for Indications
Although the application allocates the VCBs for NOF verbs, SNAplus2
allocates the VCBs for indications. Therefore, the application has access
to the VCB information only from within the callback routine; the VCB
pointer that SNAplus2 supplies to the callback routine is not valid
outside the callback routine. The application must either complete all the
required processing from within the callback routine, or it must make a
copy of any VCB data that it needs to use outside this routine.
In the event that the NOF application needs to make a copy of the data
supplied on the callback routine and the NOF application is using a
signal-based scheduling mode, an operating system limitation may
prohibit memory allocation. In this case, some memory must be
preallocated before the REGISTER_INDICATION_SINK verb is issued.
For more information about signal-based scheduling mode, see
“Signal-Based Scheduling Mode”.
Scope of Target Handle
Each application that needs to use NOF must issue the
CONNECT_NODE verb to obtain its own handle. No two NOF
applications can use the same NOF target handle.
In particular, if the application that issued CONNECT_NODE later
forks to create a child process, the child process cannot issue any NOF
verbs that use the target handle obtained by the parent process.
However, the child process can issue another CONNECT_NODE to
obtain its own target handle.