HP-UX SNAplus2 NOF Programmer's Guide

Introduction to the NOF API
NOF Verbs to Manage Specific SNAplus2 Functions
Chapter 166
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 define explicit LSs to each
node. CNs cannot be used if the local node is a LEN node.
To set up the CN, you first define a DLC and port to access each of the
nodes on the SATF.
You then define a CN that includes all these ports; you do not need to
define any LSs because a dynamic LS to the CN will be set up as
required. To define the CN, or to add ports to an existing CN, use the
following verb:
• DEFINE_CN
To obtain information about defined CNs, or about the ports on a CN, use
the following verbs:
• QUERY_CN, QUERY_CN_PORT
To delete a CN when it is no longer required, or to remove ports from a
CN without deleting the CN, use the following verb:
• DELETE_CN
To stop the node, which deactivates all resources associated with it, use
the following verb:
• TERM_NODE
To define default parameters used by the node, or to query the definition
of these parameters, use the following verbs:
• DEFINE_DEFAULTS, QUERY_DEFAULTS
To query the options and limits permitted by your SNAplus2 license for
the node, use the following verb:
• QUERY_NODE_LIMITS
3270 Communications
If SNAplus2 users will be using 3270 emulation to communicate with
host systems, you need to define the communications link to the host. For
more information, see “Getting Started”. The definition of the LS to the
host must include the name of a local PU to own the LUs required for
3270 emulation and must have the solicit_sscp_sessions parameter
set to AP_YES.