HP-UX SNAplus2 R7 NOF Programmer's Guide

Introduction to the NOF API
NOF Verbs to Manage Specic SNAplus2 Functions
SET_PROCESSING_MODE
To register for indications when the target conguration changes, use the following verb:
REGISTER_INDICATION_SINK
To unregister when indications are no longer required, use the following verb:
UNREGISTER_INDICATION_SINK
To release the target node or le when you have nished issuing NOF verbs, use one of the following verbs:
DISCONNECT_NODE, CLOSE_FILE
You can issue OPEN_FILE, CONNECT_NODE, DISCONNECT_NODE, and CLOSE_FILE verbs, and NOF
QUERY verbs, from an application running on a client, as well as from an application running on a server. You
cannot issue any other NOF verbs from the client
1.5.2 Getting Started
The rst step is to dene the SNAplus2 node that runs on each computer, and its communications links to other
computers. To dene these components, use the following verbs:
DEFINE_NODE
DEFINE_DLC, DEFINE_PORT, DEFINE_LS
After dening these components, activate them to establish the link to the remote system. (DLCs, ports, and LSs
can be dened to be initially active using the DEFINE_* verbs described previously, so that they are started
automatically when the node is started; in this case, it is not necessary to start them manually.) To activate
components, use the following verbs:
INIT_NODE
START_DLC, START_PORT, START_LS
The components must be started in the order shown because each component relies on the one before it.
To stop these components when access to the remote system is no longer required, use the following verbs:
STOP_LS, STOP_PORT, STOP_DLC
To obtain information about the conguration or current status of these components, use the following verbs:
QUERY_NODE
QUERY_DLC, QUERY_PORT, QUERY_LS
To obtain information about the usage of an LS or port, use the following verb:
QUERY_STATISTICS
To delete connectivity components when they are no longer required, use the following verbs:
DELETE_DLC, DELETE_PORT, DELETE_LS
If you are communicating with many nodes on the same shared-access transport facility (SATF), you can set up
a connection network (CN) to represent these nodes, instead of having to dene explicit LSs to each node. CNs
cannot be used if the local node is a LEN node.
To set up the CN, you rst dene a DLC and port to access each of the nodes on the SATF.
You then dene a CN that includes all these ports; you do not need to dene any LSs because a dynamic LS to the
CN will be set up as required. To dene the CN, or to add ports to an existing CN, use the following verb:
DEFINE_CN
To obtain information about dened CNs, or about the ports on a CN, use the following verbs:
50