HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
REGISTER_INDICATION_SINK
primary_rc
AP_PARAMETER_CHECK
secondary_rc
Possible values are:
AP_INVALID_USERID
The list_options parameter was set to AP_LIST_INCLUSIVE to list all entries starting from the
supplied user ID, but the user_id parameter was not valid.
AP_INVALID_LIST_OPTION
The list_options parameter was not set to a valid value.
Appendix B, Common Return Codes lists further secondary return codes associated with
AP_PARAMETER_CHECK
,
which are common to all NOF verbs.
3.169.5 Returned Parameters: Other Conditions
Appendix B, Common Return Codes lists further combinations of primary and secondary return codes that are
common to all NOF verbs.
3.170 REGISTER_INDICATION_SINK
REGISTER_INDICATION_SINK registers the NOF application to receive indications of a particular type; for
details of the SNAplus2 NOF indications, see Chapter 4, NOF Indications. The application specifies the required
type of indication by its opcode parameter; an application can register more than once to accept multiple indication
types. Each time an event occurs for which the application has requested indications (for example a change in the
configuration of the application’s target node or a change in the status of a DLC), SNAplus2 sends the appropriate
indication message to the application.
A NOF_STATUS_INDICATION, which indicates status changes for the target node or file, may be returned
to an application that has registered for any type of indication. For more information, see Section 4.18,
NOF_STATUS_INDICATION.
This verb must always be issued using the asynchronous NOF API entry point, including a callback routine (for
more information about the NOF API entry points, see Section 2.1.1, NOF API Entry Points for HP-UX ). SNAplus2
uses this callback routine to return the requested indications to the application.
This verb may be issued to different targets depending on the type of indications required, as follows:
• To register for SNA network file indications, the target must be the sna.net file.
• To register for server indications, no target is required; the application must specify a null target handle.
• To register for configuration indications relating to domain resources, the target must be the domain configuration
file.
• To register for configuration indications relating to node resources, or to register for any other indications, the
target may be either a running node or an inactive node on a computer where the SNAplus2 software is running.
3.170.1 VCB Structure
typedef struct register_indication_sink
{
AP_UINT16 opcode; /* verb operation code */
unsigned char reserv2; /* reserved */
697