Command Reference Guide

Appendix BConfiguration Files
pads Node1 with 123 blank characters so that the value in the node configuration record has the maximum
length allowed for this parameter.
• If you enter hexadecimal digits A, B, C, D, E, and F on a Motif screen, SNAplus2 changes them to a, b, c, d,
e, and f in the configuration file.
• If you do not enter a value on a Motif screen for a parameter that defaults to a null string, SNAplus2 adds a
null string for that parameter’s value in the configuration file.
• SNAplus2 substitutes some command names. For example, if you define an adjacent LEN node with a Motif
screen, SNAplus2 substitutes a [define_directory_entry] record in the configuration file. For more
information about the relationship between defining an adjacent LEN node and defining a directory entry, see
Section 2.16,
define_directory_entry.
B.4 File Input to the snapadmin Program
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 re-
sources; 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.
B.4.1 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:
1. 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.
2. 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.
3. In the directory /etc/opt/sna, check that the node configuration file sna_node.cfg is not present, and
that the domain configuration file sna_domn.cfg contains no configuration records other than the header
record. An empty version of the domain configuration file is delivered with SNAplus2. If you have created
your own configuration files or added records to the delivered empty file, save a copy of your modifications,
631