System startup files are developed and used by the system manager and operators to perform startup and shutdown operations. In some cases the files may be centrally located, separated by subsystem or by startup and shutdown functionality. There is no required naming convention for these files.
The sequence in which startup files are invoked can be important. Some processes require other processes to be running before they can be started. Examples of subsystems that must be started after a coldload are; TMF, TACLs, SPOOLER, TCPIP, CMON, and ODBC.
RISK The subvolume(s) that contain these files should reside on $SYSTEM in case that is the only volume that can be loaded.
RISK Only system managers should be allowed to modify startup files. The loss or modification of these files could be destructive to starting the system processes.
BP-FILE-STARTUP-01 Startup files should be secured "NUUU".
BP-OPSYS-OWNER-03 Startup files should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-03 Startup files should reside on $SYSTEM.<startup>
If available, use Safeguard software or a third party object security product to grant access to the Startup subvolume to necessary personnel, and deny access to all others.
BP-SAFE-STARTUP “01 Add a Safeguard Protection Records to grant appropriate access to the Startup files.
Where are the startup files located?
Who owns the startup files?
Are the startup files correctly secured with the Guardian or Safeguard system?