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-7
3. Automate System Startup
3. Automate System Startup
Some system applications and subsystems are not configured to start automatically in
the initial CONFIG file. Startup command files can automate the starting of devices and
processes on the system. Automating system startup minimizes the possibility of
operator errors caused by forgotten or incorrectly typed commands.
To automate system startup, you can Modify Provided Startup Files or Create Startup
Files.
Modify Provided Startup Files
For a description of the startup files shipped with the server, see Preloaded and
Supported Hardware and Software on page 1-49. Consider modifying the RELOAD
command in the CIIN file to reload only a minimal set of processors (such as processor
1). This strategy allows you to test for successful startup of a minimal system
environment before you bring up the remainder of the system.
Create Startup Files
You can implement the system startup sequence with a collection of startup files, each
with a specific purpose. Startup files can be created for:
•
System software
•
Subsystems
•
Communications lines
•
Applications
Tips for Startup Files
•
Copy the STARTCOM and STARTSCF files on the $SYSTEM.ZSYSCONF
subvolume and make changes to these copies to create your own command files.
Do not alter these files directly.
•
The sequence in which you invoke startup files can be important. Some processes
require other processes to be running before they can be started. Be sure to
indicate the order in which startup files are to be run.
•
You must configure a line-handler process for a data communications line in the
CONFIG file before you can invoke a startup file for that line, if one is required.
•
You do not need to create startup files for processes in the CONFIG file that are
configured to start automatically.
•
It is recommended that you specify “N” for the read access portion of the file
security attribute (RWEP) for your startup files to allow the file to be read by any
user on the network. For example, you might secure these files “NCCC.”