HP-UX SNAplus2 NOF Programmer's Guide

Introduction to the NOF API
NOF Verbs to Manage Specific SNAplus2 Functions
Chapter 170
To obtain information about the PU that owns an LU, use the following
verb:
• QUERY_PU
If you want to provide LU pools (groups of LUs that can be assigned to
applications as required, rather than having LUs explicitly defined for
each application), use the following verbs to define a pool, to obtain
information about the definition, or to delete a pool or remove LUs from
it when no longer required:
• DEFINE_LU_POOL, QUERY_LU_POOL, DELETE_LU_POOL
APPC Communications
If applications running on SNAplus2 will be using APPCto communicate
with applications running on host or peer computers, you need to define
LUs that can be used for APPC.
APPC configuration in an APPN network is much simpler than in a
pre-APPN SNA network. Many of the required components, and the
interactions between them, can be defined or determined dynamically
when sessions are started and do not need to be specified explicitly in the
initial configuration.
Each node includes a default APPC local LU (the “control point LU”). An
APPC application can use this LU, or you can define additional LUs so
that different applications can use different LUs. To define the LUs, use
the following verb:
• DEFINE_LOCAL_LU
To obtain information about the configuration or current status of LUs,
including the control point LU, use the following verb:
• QUERY_LOCAL_LU
Because APPN can locate a partner LU dynamically when a local
application needs to start a session to it, normally you do not need to
define partner LUs. However, you may need to define partner LUs if you
need to enforce the use of particular APPC features such as conversation
security. To define a partner LU, use the following verb:
• DEFINE_PARTNER_LU
To obtain information about the current status of a partner LU or about
its definition if it was explicitly defined, use the following verbs: