 |
» |
|
|
|
The command-line administration program snapadmin, can take its input from a text file instead of directly
from the command line. The file format used for a snapadmin input file is the same as the SNAplus2 configuration
file format; the information in this section applies to snapadmin as well as to configuration files used when starting
the SNAplus2 software. The only differences between the format of configuration files
and snapadmin input files are: A configuration file used at startup
can include only records corresponding to define_* and set_* commands; the snapadmin input file can include records corresponding to all the
different types of administration commands (define_*, set_*, start_*, stop_*, query_*, and delete_*). The records for the additional commands are included
in the snapadmin file using the same format as for [define_*] and [set_*] records.
For information about the usage of these commands, see Chapter 1 “Introduction to SNAplus2 Administration Commands” The configuration file contains the complete configuration
of a SNAplus2 node or of SNAplus2 domain resources; the snapadmin input file can contain either complete information or
partial information (to modify or query an existing configuration). The [define_node_config_file] and [define_domain_config_file] header
records are not required in the snapadmin input file.
Sample snapadmin Input Files | |
SNAplus2 provides a series of sample files that can be used
as input to the snapadmin program. These files contain the administration commands
necessary to set up a series of typical SNAplus2 configurations. Because the input file format is the same as the configuration
file format, you can use these files as examples of how to specify
various configuration file records. However, these files are intended
for use as input files to the snapadmin program, rather than as initial configuration files.
In particular, some of them contain both node records and domain
records, which is valid in an input file but not in a configuration
file. To use one of the files, take the following steps: Check the contents of the file, and modify
the records as necessary to suit your configuration requirements.
For example, if you are using one of the files that define host
connectivity, you will need to modify the adjacent CP name and LU
names to match the host configuration. Stop the SNAplus2 software if it is running. For information
about how to stop the SNAplus2 software, refer to the HP-UX
SNAplus2 Administration Guide. Check that the files sna_node.cfg and sna_domn.cfg, in the directory /etc/opt/sna contain no configuration records other than the header records.
Empty versions of these files are delivered with SNAplus2. If you
have modified these files, save a copy of your modifications, and
then delete all records from the files except for the header records. Start the SNAplus2 software. Use the following command to define the configuration: snapadmin -i new.cfg The value new.cfg stands for the name of the input file you are using (with
the modifications that you made in step 1). Use the following command to start the node (this also
starts any resources that are defined in the file as being initially
active): snapadmin init_node
Sample Files Delivered with SNAplus2 | |
The sample files are delivered in the directory /opt/sna/samples. The sample files are: - config1.cfg
Configuration for a LEN node, supporting 3270 emulation
over an SDLC leased line (initially active) to a host that issues
format 3 XIDs. The configuration includes two users, each with one
3270 session. - config2.cfg
Configuration for an end node, supporting 5250 emulation
over an SDLC switched line (operator-started, with CP-CP session
support) to an AS/400. The configuration includes two users, each with
one 5250 session using the default local LU. - config3.cfg
Configuration for a LEN node, supporting RJE over QLLC
to a host that issues format 3 XIDs. The configuration includes
a single RJE workstation with one LU. - config4.cfg
Configuration for a LEN node, supporting dependent APPC
communications over an SDLC switched outgoing line (activated on
demand) to an APPN end node. The configuration includes a single
local LU. - config5.cfg
Configuration for a LEN node, supporting 3270 emulation
with LU pools, using both Token Ring and Ethernet to a host that
issues format 3 XIDs. The configuration includes a pool of LUs (some
defined on each of the two host links), and two users each with
two 3270 sessions using the pool. - config6.cfg
Configuration for a LEN node, supporting PU concentration.
The upstream link is an SDLC leased line (initially active) to a
host that issues format 3 XIDs; there are two downstream links over
Token Ring. The configuration includes four downstream LUs used for
3270 emulation, mapped to four host LUs. - config7a.cfg, config7b.cfg
Configurations for a network node and an end node, communicating
peer-to-peer using APPC over Ethernet. The configuration includes
one local LU on each node.
|
Printable version
