NonStop S-Series Hardware Installation and FastPath Guide (G06.29+)

Online Configuration Tasks
HP NonStop S-Series Hardware Installation and FastPath Guide—541880-002
12-6
Types of System Configuration Files
Types of System Configuration Files
On systems running G-series RVUs:
•
Most I/O processes are not prebuilt by SYSGENR. Rather, the subsystems send
information about these processes into the system configuration database.
•
The SYSnn.OSCONFIG file contains only Software Problem Isolation and Fix
Facility (SPIFF) and Software ID (SWID) records.
•
The system configuration database files are stored on the $SYSTEM.ZSYSCONF
subvolume, independent of the SYSnn subvolume on which the operating system
is running.
The system configuration files used on systems running G-series RVUs are:
See the TSM Configuration Guide or the OSM User’s Guide for instructions on how to
select a system configuration file during system load.
File Type File Name Description
On the $SYSTEM.SYSnn subvolume:
Base
CONFIG
CONFBASE Contains the minimal configuration to load the system. You
use this file when you want to rebuild the system
configuration from the absolute minimum configuration.
File Type File Name Description
On the $SYSTEM.ZSYSCONF subvolume:
Input to
initial
CONFIG
SCF0000 Is used to create the CONF0000 file, which HP uses to
configure and test a standard system before shipment.
Current
CONFIG
CONFIG Contains the current system configuration.
Saved
CONFIG
CONFxxyy Contains a copy of a CONFIG file, saved for future use. You
can use one of these files to return to an earlier, stable
configuration. The file-naming convention is to let xx indicate
a major configuration change and yy indicate a minor
change.
Autosaved
CONFIG
CONFSAVE Contains a saved version of the current CONFIG file that the
operating system automatically creates when you load the
system from a saved CONFIG file.
If you load the system from CONFBASE or a CONFxxyy file
to abandon a corrupt configuration, HP can analyze the
corrupt configuration file to determine the reason for the
corruption. If the CONFSAVE file is not corrupt, you can use it
to reload the system if you first rename it to CONFxxyy.