HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
REGISTER_INDICATION_SINK
unsigned char format; /* reserved */
AP_UINT16 primary_rc; /* primary return code */
AP_UINT32 secondary_rc; /* secondary return code */
AP_UINT32 proc_id; /* reserved */
AP_UINT16 queue_id; /* reserved */
AP_UINT16 indication_opcode; /* opcode of indication to be sunk */
} REGISTER_INDICATION_SINK;
3.170.2 Supplied Parameters
The application supplies the following parameters:
opcode
AP_REGISTER_INDICATION_SINK
indication_opcode
The opcode parameter of the indication to be returned. SNAplus2 will send this indication to the application’s
callback routine every time the indication is generated.
To receive configuration indications, specify the value AP_CONFIG_INDICATION. If the target handle
specified on the REGISTER_INDICATION_SINK verb identifies the domain configuration file, this value
requests an indication each time the file is updated; if the target handle identifies a node, this value requests
an indication each time the node’s configuration is updated.
To receive SNA network file indications, issue the verb using a target handle that identifies the sna.net
file, and specify the value AP_SNA_NET_INDICATION. This value requests an indication each time the file
is updated.
For all other indications, specify the opcode value for the required indication. For more information, see the
descriptions of individual indications in Chapter 4, NOF Indications.
3.170.3 Returned Parameters: Successful Execution
If the verb executes successfully, SNAplus2 returns the following parameters:
primary_rc
AP_OK
secondary_rc
Not used.
3.170.4 Returned Parameters: Parameter Check
If the verb does not execute because of a parameter error, SNAplus2 returns the following parameters:
primary_rc
AP_PARAMETER_CHECK
secondary_rc
Possible values are:
AP_INVALID_OP_CODE
One of the following has occurred:
• The indication_opcode parameter did not match the opcode of any of the SNAplus2 NOF API
indications.
698