SCF Reference Manual for G-Series RVUs (G06.24+)

Using SCF to Configure and Manage NonStop
S-Series Servers
SCF Reference Manual for G-Series RVUs—520413-004
1-5
Types of CONFIG Files
Types of CONFIG Files
On systems running G-series, the system configuration database files are stored on
the $SYSTEM.ZSYSCONF subvolume, independent of which SYSnn subvolume the
operating system is running on.
Table 1-2 describes the system configuration files that are used on systems running
G-series.
Table 1-2. Types of System Configuration Files for Systems Running G-Series
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.
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 prior to 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 an automatically 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
in order 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.