HP-UX SNAplus2 NOF Programmer's Guide

NOF API Verbs (REGISTER_INDICATION_SINK to UNREGISTER_INDICATION_SINK)

REGISTER_INDICATION_SINK

Chapter 51012

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 6, “NOF Indications.” The application speciﬁes

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 conﬁguration 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 ﬁle, may be returned to an application that has registered

for any type of indication. For more information, see

“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 “Asynchronous Entry Point: nof_async”). 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 ﬁle indications, the target must be the

sna.net ﬁle.

• To register for server indications, no target is required; the

application must specify a null target handle.

• To register for conﬁguration indications relating to domain

resources, the target must be the domain conﬁguration ﬁle.

• To registerfor conﬁguration 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.