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-4

Making Online Configuration Changes

Because configuration changes are made online using SCF, they take effect as soon

as the affected objects are started (with the SCF START command). Except for

subsystems controlled by the WAN subsystem, these changes are permanent; they

persist through processor and system loads (unless you load the system using a

different configuration file, as discussed in the next subsection). For subsystems

controlled by the WAN subsystem, configuration changes are not permanent; you must

reimplement them if the system or a processor goes down.

The general method for performing SCF changes follows:

1. Create a command file containing the SCF commands to implement a

configuration change.

2. For fallback purposes, save the current system configuration database CONFIG

file using the SCF SAVE command (on page 5-103). This example shows how to

save the current CONFIG file to a file named CONF0102 on the

$SYSTEM.ZSYSCONF subvolume:

-> SAVE CONFIGURATION 1.2

3. Invoke the SCF command file created in Step 1. For example:

-> OBEY SCFCONF

This method has the advantage of recoverability by saving a copy of a known, stable

configuration. In case the most recent change results in a problem, you can restore

the previous configuration by loading the system from the saved system configuration

file.