HP-UX SNAplus2 R7 Administration Guide
Administering SNAplus2
Overview of SNAplus2 Administration
administration commands from a client if you specify -n with a server name. A command issued from a client
using -n has the same effect as if it were issued at the named server.
You can get help for command-line administration by using any of the following commands:
•
snapadmin -h provides basic help for command-line administration and usage information for command-line
help.
• snapadmin -h -d provides a list of commands that can be supplied to the
snapadmin program.
• snapadmin -h
command provides help for the named command.
• snapadmin -h -d command provides detailed help for the named command, including a list of the
configuration parameters that can be specified with the command.
Refer to HP-UX SNAplus2 Administration Command Reference for more information.
Remote Command Facility
The remote command facility (RCF) provides the following facilities to support the administration of SNAplus2
from a NetView console on a host:
• Service point command facility (SPCF) enables an operator at a host NetView console to manage SNAplus2
from NetView by issuing SNAplus2 administration commands.
• UNIX command facility (UCF) enables the NetView operator to issue standard HP-UX commands on the
SNAplus2 computer.
For more information about RCF, see Chapter 10, Managing SNAplus2 from NetView.
Configuration Files
Configuration information for the SNAplus2 system is held in the following text files:
Node configuration file
The /etc/opt/sna/sna_node.cfg file contains information about SNAplus2 node resources for a
specific node. This file resides on the computer where the node runs. It includes information about the node’s
resources and specifies which resources are active when SNAplus2 is started on the node.
This file provides an initial definition of the resources that are available; you can then use the other admin-
istration tools to modify the running node’s resources as your requirements change. Any modifications you
make are automatically saved to the file, so that the modified configuration can be used again when the node
is stopped and restarted.
Domain configuration file
The /etc/opt/sna/sna_domn.cfg file contains information about SNAplus2 domain resources (re-
sources not associated with a particular local node). The master copy of this file resides on the master server.
Invokable TP data file
The /etc/opt/sna/sna_tps file contains information that SNAplus2 needs to start invokable (target)
TPs, and can also provide other information (such as the level of security required to access the TP). This
file resides on the computer where the TPs run.
For more information about this file, see Section 7.4, Defining TPs.
You can modify the configuration using the Motif administration program, the command-line administration program,
or the NOF API. All of these tools make the required changes to the node configuration file or domain configuration
file as appropriate. Because configuration information is stored as plain text, you can also modify the file directly
using a standard ASCII text editor such as vi, or by means of a shell script using HP-UX utilities such as awk
or sed. Any changes to configuration files using a text editor must be made before starting SNAplus2. Refer
to HP-UX SNAplus2 Administration Command Reference for more information about SNAplus2 configuration file
format.
62