The SNAplus2 NOF API provides access to a standard set of
commands, called NOF verbs, that can be used to administer the SNAplus2
system from within an application program. These verbs enable you
to define and delete resources, specify SNAplus2 parameters such
as diagnostics levels and file names, start and stop defined resources,
query the definition or current status of resources, and manage
which servers on the SNAplus2 LAN can act as backup masters if the
master configuration file server is not available.
The NOF verbs provide the same functions as commands issued
to the command-line administration program snapadmin, or as records in a SNAplus2 configuration file. For
example, the NOF verb DEFINE_LOCAL_LU is equivalent both to a define_local_lu command issued to the snapadmin program, and to a define_local_lu record
in a configuration file; all three of them perform the same function,
which is to specify the parameters of a SNAplus2 local APPC LU.
You can use the Motif administration program xsnapadmin to perform the same function as a NOF verb or an administration
command (for example, you can use the program to define a local
APPC LU). However, this program does not provide access to the full
range of parameters included in some NOF verbs. For more information
about using the Motif administration program, refer to the HP-UX
SNAplus2 Administration Guide.
You can issue NOF verbs to any of the following targets:
A running SNAplus2 node (to manage
its resources or to monitor its operation)
A server where the node is not running (to query
the stored configuration or to modify it for use when the node is
next started)
The SNAplus2 domain as a whole-to define, modify,
or query the configuration of domain resources (resources used to
support particular user programs, such as 3270 diagnostics parameters
and CPI-C side information entries, which are not associated with
a particular node).
The NOF API enables you to do the following:
Develop your own application programs
to manage the SNAplus2 system
Develop application programs that use the other
SNAplus2 APIs so that they can also manage their own resources (for
example, an APPC application can check that the communications link
to its partner TP is active before attempting to allocate a conversation
or can define the remote LU where its partner TP is located).
Node
Configuration File |
 |
Configuration information for each SNAplus2 node is held in
a text file on the computer where the node runs. This file includes
information about the node's resources, and specifies which resources
will be active when SNAplus2 is started. When you start the node,
the file provides an initial definition of the resources that are
available; you can then use the NOF API or the SNAplus2 administration
tools to modify the running node's resources as your requirements
change.
You can set up multiple configuration files, to store different
SNAplus2 configurations for use at different times, and select which
of these files to use when starting the SNAplus2 software.
Configuration in an APPN network is a dynamic process; you
can add, delete, or modify resources as necessary while the SNAplus2
software is running. The configuration file provides an initial
definition of the available resources and stores the current definition
so that you can use it again when you need to restart the node,
but it is not necessary to define the entire configuration before
starting the SNAplus2 software.
Domain
Configuration File |
|
Configuration information for SNAplus2 domain resources is
held in a single text file on the master server. You can set up
multiple domain configuration files, to store different SNAplus2
configurations for use at different times, and select which of these
files to use when starting the SNAplus2 software on the master server.
Configuration in an APPN network is a dynamic process; you
can add, delete, or modify resources as necessary while the system
is running. The domain configuration file provides an initial definition
of the available domain resources and enables you to store the current
definition so that you can use it again when you need to restart
the system, but it is not necessary to define the entire domain
configuration before starting the SNAplus2 software or to restart
the software when you make changes.
Printable version
