 |
» |
|
|
|
As the SNAplus2 administrator, you are responsible for installing
the SNAplus2 software and for managing its resources. Before beginning SNAplus2 administration, you must understand
the main features of the SNAplus2 product. This section describes
the administration tasks you must perform and the tools you can
use to perform them. Administration Responsibilities | |
To
administer the SNAplus2 system, you need to do the following: Define the resources
of the SNAplus2 system, as required by the user programs that will
be running. Work with the administrators of the host or peer computers
with which SNAplus2 communicates, to ensure that the SNAplus2 configuration
matches that of the remote system. Initialize the SNAplus2 software. Optionally,
modify the configuration dynamically as your requirements change—by
adding or removing resources, or by activating and deactivating
the defined resources. Monitor
the status of active resources and gather diagnostics information
to diagnose any problems that occur. Optionally, create application
programs or shell scripts to automate standard management operations.
These tasks are normally performed by a System Administrator
at the site where the SNAplus2 system is installed. However, SNAplus2
also provides the service point command facility (SPCF), which enables
an operator using the NetView program to perform Steps 3 and 4 remotely
by issuing management commands at the NetView console. For more
information about SPCF, see Chapter 10, "Managing SNAplus2
from NetView." Administration Tools | |
SNAplus2
provides a range of tools for administering the system. Depending
on your requirements, you may not need to use all of them. This
section summarizes the functions provided by each of these tools. | | | |  | NOTE: This document provides general information about SNAplus2
administration, which you can perform using any of the tools described
in this section. For most purposes, the Motif administration program
is recommended, because it provides context-sensitive guidance for
node configuration and management. | | | | |
SNAplus2 includes the following administration tools: All of the SNAplus2 administration tools use the NOF API.
You can also use that API to write your own administration tools.
For more information, see “NOF Applications”. Motif Administration
ProgramThe
easiest way to define and modify the SNAplus2 configuration is to
use the Motif administration program (xsnapadmin).
This program provides a graphical user interface from which you
can view and manage SNAplus2 resources. The following management operations are available: Defining SNAplus2 resources Starting and stopping a node and its connectivity
resources Changing the configuration of defined resources Querying the configuration of defined resources
and their current status if they are active
The Motif administration program can be used to manage both
node resources (for any server on the LAN, as long as the SNAplus2
software is running on that server) and domain resources. For each
type of communications (such as 3270 or APPC), the program guides
you in setting up the configuration of the required resources. | | | | | NOTE: The windows and dialogs in the Motif administration
program may differ from those shown in this guide, depending on
the functions included with your installation of SNAplus2 and the
choices you make on a particular dialog. | | | | |
The Motif administration program includes help screens that
provide overview information for SNA and SNAplus2, reference information
for SNAplus2 dialogs, and guidance for performing specific tasks. Before starting the Motif administration program, make sure
the SNAplus2 software is enabled. For more information, see Chapter
3, "Administering SNAplus2." To start the Motif administration program in the background,
issue the following command: xsnapadmin & All started SNAplus2 servers are shown on the main screen.
For those that have already been configured, the program enables
you to select a node, and then displays the selected node's configuration.
Otherwise, the program prompts you to select a node and leads you
through the required steps to define it. For more information about how to use the Motif administration
program to define and manage SNAplus2 resources, see "Invoking
the Motif Administration Program", or refer to the help
screens provided by the program. | | | | | NOTE: The Motif administration program enables you to set
up all required parameters for standard SNAplus2 configurations.
For advanced parameters, the Motif administration program supplies
default values. You need to supply only the essential configuration
information, which enables you to set up SNA communications quickly
and easily. The other SNAplus2 administration tools, including command-line
configuration, and NOF application programs, provide access to a
wider range of configuration parameters and options than those shown
in the Motif administration program. In most cases, however, you
can perform all needed configuration from the Motif administration
program, because it exposes the key fields you need to configure
and hides the fields that most users should not modify. The default
values supplied by command-line configuration may differ from those
supplied by the Motif administration program, because the Motif
program can choose values more intelligently based on the context
of the configuration task you are performing. If you need to use these additional functions, you can still
use the Motif administration program to set up the basic configuration,
and use the other administration tools to specify the additional
functions. When you later use the Motif administration program to
manage the modified configuration, the program retains the changes
you made using the other tools, although the additional functions
you have configured are not displayed in the Motif program. | | | | |
Command-Line Administration
ProgramThe
command-line administration program, snapadmin,
enables you to issue commands to manage individual SNAplus2 resources.
You can use snapadmin
either directly from the HP-UX command prompt or from within a shell
script. Commands can be issued to a specific SNAplus2 node to manage
the node's resources, to the SNA network data file to manage master
and backup servers, or to the domain configuration file to manage
domain resources. Some commands can be issued from SNAplus2 clients, provided
the command includes the -n option to specify a
server name. Such a command 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 commandprovides
help for the named command. snapadmin -h -d commandprovides
detailed help for the named command,
including a list of the configuration parameters that can be specified
with the command.
Refer to the HP-UX SNAplus2 Administration Command
Reference for more information. 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
information for the SNAplus2 system is held in the following text
files: - Node
configuration file
The sna_node.cfg
file contains information about SNAplus2 node resources for a specific
node. This file resides on the computer where the node runs. This
file 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 administration 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
sna_domn.cfg file contains
information about SNAplus2 domain resources (resources
not associated with a particular local node). The master copy of
this file resides on the master server. - Invokable TP data file
The
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 "Defining
TPs".
You can modify the node and domain 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 the HP-UX SNAplus2 Administration
Command Reference for more information about SNAplus2
configuration file format. | | | | | NOTE: SNAplus2 configuration is a dynamic process; it is not
necessary to define the entire configuration before starting the
SNAplus2 software. The configuration file provides an initial definition
of the available resources, but you can add, delete, or modify resources
as necessary while the SNAplus2 software is running. SNAplus2 stores
the current definition so that you can use it again when you need
to restart the system. | | | | |
The following files contain information about the SNAplus2
client/server network: - SNA network
data file
The sna.net
file contains information about which server is the master, and
which servers can act as backup servers. This binary file resides
on the master server. You can modify the contents of this file using
the administration programs or the NOF API. For more information about this file, refer to the HP-UX
SNAplus2 Administration Command Reference. - Client network data file
The sna_clnt.net
file contains information about how to access SNAplus2 servers,
required by a client computer. This text file resides on the client
computer. You can modify the contents of this file using a standard
ASCII text editor. For more information about this file, refer to the HP-UX
SNAplus2 Administration Command Reference.
The following files control the operation of user applications: - 3270
emulation program style file
Information
about a user's customization of the 3270 emulation program is held
in a style file, which can be set up either by the System Administrator
(as a standard version for multiple users) or by the user (to create
his or her own customization). The information in this file can
be modified using the menu interface of the 3270 emulation program. For more information about 3270 style files, refer to the
HP-UX SNAplus2 3270/3179G Users Guide. - RJE workstation style file
Information about the customization
of the RJE workstation is held in a style file, which can be set
up either by the System Administrator or by the users of the workstation.
The information in this file is in ASCII text, and can be modified
using a standard text editor; SNAplus2 also provides a character-based
menu interface program that you can use to modify the file. For more information about RJE style files, refer to the HP-UX
SNAplus2 RJE Users Guide.
The SNAplus2 NOF API provides the same management functions
as the command-line administration program, enabling you to define
and manage SNAplus2 resources. This means that you can write your
own application programs to administer SNAplus2. Refer to the HP-UX
SNAplus2 NOF Programmers Guide for more information. SNAplus2
provides several diagnostics tools to help you diagnose and correct
problems encountered during SNAplus2 operation: Any component detecting a problem
or an exception (an abnormal condition that may indicate the cause
of a problem) writes an entry to an error log file.
In addition, all significant system events can be recorded in an
audit log file. You can determine which types of
events (problems, exceptions, or audits) are recorded. In a client/server
network configuration, you can specify global settings for the types
of events to record on all servers, and then override these on individual
servers if necessary. You can specify the names and directories of the
files used to hold error and audit log information; if preferred,
you can send both types of information to the same file. On a client/server
system, you can send messages from all servers to a central log
file on one server (central logging), or send log messages to separate
files on each server. Log files are generated as text files, and can be
viewed using a standard ASCII text editor such as vi. You can choose full logging
(which includes details of the cause of the log, and any action
required, in the log file for each message), or succinct logging
(which includes only a summary of the source of the log and the
message text). When using succinct logging, you can use the snaphelp
command-line utility to obtain the full cause and action text for
a particular message number if you need further information. For some error conditions, SNAplus2 sends a message
to the HP-UX console to warn the operator, in addition to writing
a problem message to the error log file. Many components can produce a trace file
that records the activity of that component. Tracing degrades the
performance of SNAplus2 components, and so is normally disabled. Using command-line utilities, you can filter trace
files to extract or interpret specific information or to produce
a summary of message flows. The resulting output files can be viewed
using a standard ASCII text editor such as vi. SNAplus2 can generate alerts and send them to the
NetView program at a host computer. These alerts can be any of the
following: Link alerts from connectivity components,
to provide information about connection problems 3270 user alerts from the emulation program Alerts supplied by an application program using
the MS API
Refer to the HP-UX SNAplus2 Diagnostics Guide
for information about SNAplus2 log messages, using SNAplus2 trace
facilities, and interpreting trace files. For information about using the MS API, refer to the HP-UX
SNAplus2 MS Programmers Guide. Simple Network Management Protocol
SupportThe Simple Network Management Protocol (SNMP)
is an industry-standard management protocol. SNAplus2 includes an
SNMP subagent
to provide support for the APPN Management Information Base (MIB)
database maintained by AIX. For a more detailed discussion of SNMP and for a list of the
APPN MIB objects that are supported by the SNAplus2 SNMP subagent,
see Appendix B, "APPN Network Management Using the Simple
Network Management Protocol." |
Printable version
