SCF Reference Manual for J-Series and H-Series RVUs

Using SCF to Configure and Manage NonStop
Integrity NS-Series Servers
SCF Reference Manual for J-Series and H-Series RVUs—529649-003
1-12
Getting a Corrupt System Configuration File
Analyzed
changes, enter an ALTER SUBSYS command to change these values to match
the current settings.
This misleading pending changes display can occur if you load the system from an
earlier configuration (either a CONF xxyy or the CONFBASE file) and that earlier
configuration has different system name, number, or time attributes than the
configuration being replaced. For example, if you load the \EAST system from the
CONFBASE file (which specifies \NONAME as the system name), an INFO
SUBSYS command displays \EAST as the current system and \NONAME as a
pending change. Entering an ALTER SUBSYS command to change the system
name to \EAST causes the pending change to disappear from a subsequent INFO
SUBSYS command.
Getting a Corrupt System Configuration File Analyzed
If the current system configuration file somehow becomes corrupt, you can send it to
your service provider to have the cause determined.
1. Return to a saved, stable configuration by following the procedure Returning to a
Saved Configuration on page 1-11.
2. Once the system is up and stable, copy to a backup tape the corrupt CONFSAVE
file. For example:
> BACKUP $TAPE, $SYSTEM.ZSYSCONF.CONFSAVE, LISTALL, &
DENSITY 6250
Do this before loading the system a second time, because another system load
operation will overwrite the CONFSAVE file you want analyzed.
3. Submit the tape to your service provider for analysis, along with a copy of any SCF
command file or SCF log file of the commands that were part of the process of
creating the corrupt configuration.
System Management Considerations
System managers should be aware of the considerations discussed in this subsection
when configuring systems running H-series RVUs.
Managing Multiple Versions of the Operating System
A side effect of having a ZSYSCONF system configuration subvolume is that the
SYS nn subvolume can be used as a software versioning tool, while the ZSYSCONF
subvolume can serve as a hardware versioning tool. That is, you can add software
product revisions (SPRs) for software changes without having to create a new
CONFIG file.
You can use the CONF xxyy file-naming convention to track major and minor
hardware configuration changes. A major change, like the addition of another