NonStop Operations Guide for H-Series and J-Series RVUs

SCF accepts commands from a workstation, a disk file, or an application process. It sends display
output to a workstation, a file, a process, or a printer. Some SCF commands are available only to
some subsystems. For complete information, see the SCF Reference Manual for J-Series and H-Series
RVUs. Subsystem-specific information appears in a separate manual for each subsystem. For a
partial list of these manuals, refer to “Related Reading for Tools and Utilities” (page 227).
More details about the functions of SCF appear in “Subsystem Control Facility (SCF) ” (page 225).
SCF System Naming Conventions
SCF object names usually follow a consistent set of naming conventions defined for each installation.
HP preconfigures some of the naming conventions to create the logical device names for many
SCF objects.
System planning and configuration staff at your site likely will change or expand on the
preconfigured file-naming conventions that HP provides, typically by establishing naming conventions
for configuring such objects as storage devices, communication processes, and adapters. These
conventions should simplify your monitoring tasks by making process or object functions intuitively
obvious to someone looking at the object name. For example, in your environment, tape drives
might be named $TAPEn, where n is a sequential number.
The SCF Reference Manual for J-Series and H-Series RVUs lists naming conventions for SCF objects,
as well as HP reserved names that cannot be changed or used for other objects or processes in
your environment.
SCF Configuration Files
Your system is delivered with a standard set of configuration files:
• The $SYSTEM.SYSnn.CONFBASE file contains the minimal configuration required to load the
system.
• The $SYSTEM.ZSYSCONF.CONFIG file contains a standard system configuration created by
HP. This basic configuration includes such objects as disk drives, tape drives, ServerNet
adapters, the local area network (LAN) and wide area network (WAN) subsystem manager
processes, the OSM server processes, and so on. You typically use this file to load the system.
• The $SYSTEM.ZSYSCONF.CONFIG file is also saved on your system as the
ZSYSCONF.CONF0000 file.
All subsequent changes to the system configuration are made using SCF. The system saves
configuration changes on an ongoing basis in the ZSYSCONF.CONFIG file. You have the option
to save a stable copy of your configuration at any time in ZSYSCONF.CONFxxyy using the SCF
SAVE command. For example:
-> SAVE CONFIGURATION 01.02
You can save multiple system configurations by numbering them sequentially based on a meaningful
convention that reflects, for example, different hardware configurations. Each time you load the
system from CONFBASE or CONFxxyy, the system automatically saves in a file called
ZSYSCONF.CONFSAVE a copy of the configuration file used for the system load.
For guidelines on how to recover if your system configuration files are corrupted, refer to
“Troubleshooting and Recovery Operations ” (page 193).
For certain SCF subsystems, configuration changes are persistent. The changes persist through
processor and system loads unless you load the system with a different configuration file. Examples
of these subsystems are the Kernel, ServerNet LAN Systems Access (SLSA), the storage subsystem,
and WAN. For other SCF subsystems, the changes are not persistent. You must reimplement them
after a system or processor load. Examples of these subsystems are General Device Support (GDS),
Open System Services (OSS), and SQL communication subsystem (SCS).
40 Determining Your System Configuration