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-7
Contents of the Initial CONFIG File
Contents of the Initial CONFIG File
When the system is delivered, the $SYSTEM.ZSYSCONF.CONFIG file contains a
standard system configuration created by HP. Some of the objects already configured
in this file are:
•
A $ZM QIO monitor process in each processor
•
The $ZZLAN LAN subsystem manager
•
The $ZZWAN WAN subsystem manager
•
The $ZDMP HP Tandem Failure Data System (TFDS) process
•
The $ZNET Subsystem Control Process (SCP) management process
•
The $ZZATM Asynchronous Transfer Mode subsystem monitor process (optional)
•
Magnetic disk drives
•
Tape drives
•
LAN adapters
•
The $ZSPE SP-to-EMS event conversion process
•
The $CLCI initial TACL process
•
The $ZNET Subsystem Control Program process
•
The $ZTCP0 and $ZTCP1 NonStop TCP/IP processes
•
The $ZLOG alternate EMS collector
•
These objects for OSM:
°
The $ZOSM (Applet Server process)
°
The $ZCMOM (main OSM server process)
°
The $ZOEV (OSM event viewer manager)
This initial CONFIG file is also saved on your system as the ZSYSCONF.CONF0000
file. For example displays from the CONF0000 file, refer to Section 2, Using SCF to
Display Your System’s Configuration.
Recreating the Initial CONFIG File
If the current configuration file has become corrupted and there is no other
configuration file from which you can load the system, use this procedure to re-create
the initial CONFIG file.
1. Start the system from a system console, specifying the CONFBASE base
configuration file on the $SYSTEM.SYS nn subvolume.
2. After the system starts and displays a TACL prompt, log on and start SCF with a
command that invokes the SCF command file SCF0000. For example:
> SCF / IN $SYSTEM.ZSYSCONF.SCF0000 /
SCF executes the SCF0000 file, makes online configuration changes to the
running system, creates an SCFLOG file of the processed commands and returned
messages, and records these configuration changes permanently in the CONFIG
file. At this point, the contents of the CONFIG file are the same as those of the
CONF0000 file shipped with the system.