HP-UX SNAplus2 R7 NOF Programmer's Guide

Introduction to the NOF API
SNAplus2 Components
1.1.1 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.
1.1.2 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.
1.1.3 Invokable TP Data File
Information that SNAplus2 needs to start invokable (target) TPs is held in the file /etc/opt/sna/sna_tps.
This file can also provide other information (such as the level of security required to access the TP). The invokable
TP data file resides on the computer where the TPs run.
1.2 SNAplus2 Components
SNAplus2 implements an APPN node to communicate with other nodes on the SNA network. This provides logical
unit (LU) 6.2 support for APPC and CPI-C capabilities and for 5250 emulation, as well as LU 0, 1, 2, and 3 support
for 3270, RJE and LUA communications.
SNAplus2 can operate as any of the APPN node types LEN, end, network, or branch network node, depending on its
configuration. Certain functions are supported only on particular node types, as defined by the APPN architecture.
These differences are indicated where necessary in this manual; where no differences are indicated, the information
applies to all node types.
Figure 1–1,
SNAplus2 Components, shows the components of SNAplus2 and how they work together.
43