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

FastPath Tasks: Optional
HP NonStop S-Series Hardware Installation and FastPath Guide—541880-002
F-2
1. Prerequisites
1. Prerequisites
Before you change the system configuration, complete the following tasks.
1a. Verify Required Configuration Changes
Verify that the procedures in Appendix E, FastPath Tasks: Required are complete.
1b. Review Initial System Configuration
The following initial system configuration is shipped in the OPEN FIRST box:
•
CONFTEXT configuration file list
•
SCF initial configuration file list: $SYSTEM. ZSYSCONF. SCF0000.
The SCF0000 file is an input file to the initial $SYSTEM. ZSYSCONF.CONFIG file.
Verify how the system is initially configured:
•
Which processes and devices are already configured in the initial system
configuration database and started automatically during system load?
•
Which processes do not start automatically and therefore require startup files?
•
Which processes and devices must not be renamed?
For information about default values for OSM or TSM, see the OSM User’s Guide or
the TSM Configuration Guide as appropriate.
1c. Start Required Processes
Before you perform some system configuration procedures, such as configuring
Expand-over-IP, certain processes must be started. Some of these processes do not
start automatically when the system is loaded. Examples of such processes include:
•
NonStop TCP/IP processes (except $ZTCP0 and $ZTCP1)
•
Parallel Library TCP/IP processes and associated routes and subnets
For information about the standard configuration and startup files for NonStop TCP/IP
processes that are shipped with your system, see Preloaded and Supported Hardware
and Software on page 1-49.
To modify the standard startup files or create startup files for required processes, see
3. Automate System Startup on page F-7.
1a. Verify Required Configuration Changes F-2
1b. Review Initial System Configuration F-2
1c. Start Required Processes F-2
1d. Save Current System Configuration F-3
1e. If Your Server Will Be Part of a ServerNet Cluster F-3