Difference between revisions of "System Startup"
(Created page with "'''System startup''' is a complex of events that occur when an OpenVMS system is booted. =Startup Phases= 1. Start the CLUSTER_SERVER process. 2. Define logical names needed...") |
|||
| Line 2: | Line 2: | ||
=Startup Phases= | =Startup Phases= | ||
| + | |||
1. Start the CLUSTER_SERVER process. | 1. Start the CLUSTER_SERVER process. | ||
| + | |||
2. Define logical names needed for basic operations and install images listed in SYS$MANAGER:VMSIMAGES.DAT. | 2. Define logical names needed for basic operations and install images listed in SYS$MANAGER:VMSIMAGES.DAT. | ||
| + | |||
3. Execute [[SYCONFIG.COM]]. | 3. Execute [[SYCONFIG.COM]]. | ||
| + | |||
4. Add any new drivers by executing AUTOCONFIGURE ALL<sup>VAX</sup>/IO AUTOCONFIGURE<sup>Alpha and I64</sup> | 4. Add any new drivers by executing AUTOCONFIGURE ALL<sup>VAX</sup>/IO AUTOCONFIGURE<sup>Alpha and I64</sup> | ||
| + | |||
5. Install the primary swap file, if the file is present. | 5. Install the primary swap file, if the file is present. | ||
| + | |||
6. Start the CONFIGURE process unless [[NOAUTOCONFIG]] is set to 1 or [[STARTUP$AUTOCONFIGURE_ALL]] is defined as [[False]] by [[SYCONFIG.COM|SYS$MANAGER:SYCONFIG.COM]]. | 6. Start the CONFIGURE process unless [[NOAUTOCONFIG]] is set to 1 or [[STARTUP$AUTOCONFIGURE_ALL]] is defined as [[False]] by [[SYCONFIG.COM|SYS$MANAGER:SYCONFIG.COM]]. | ||
| + | |||
7. Execute SYLOGICALS.COM. At this point, all the devices are available either through the AUTOCONFIGURE command or through the CONFIGURE process. | 7. Execute SYLOGICALS.COM. At this point, all the devices are available either through the AUTOCONFIGURE command or through the CONFIGURE process. | ||
| + | |||
8. If the system is a satellite node in a VAXcluster or an OpenVMS Cluster environment, execute SATELLITE_PAGE.COM to install page and swap files on a local disk. [[SATELLITE_PAGE.COM]] is created when you execute the [[CLUSTER_CONFIG.COM]] procedure. | 8. If the system is a satellite node in a VAXcluster or an OpenVMS Cluster environment, execute SATELLITE_PAGE.COM to install page and swap files on a local disk. [[SATELLITE_PAGE.COM]] is created when you execute the [[CLUSTER_CONFIG.COM]] procedure. | ||
| + | |||
9. Execute [[SYPAGSWPFILES.COM]]. | 9. Execute [[SYPAGSWPFILES.COM]]. | ||
| + | |||
10. Perform the following steps in no specified order: | 10. Perform the following steps in no specified order: | ||
| + | |||
* Install required images | * Install required images | ||
* Start various operating system processes (OPCOM, CACHE_SERVER, ERRFMT, JOBCTL) | * Start various operating system processes (OPCOM, CACHE_SERVER, ERRFMT, JOBCTL) | ||
| Line 17: | Line 28: | ||
* On VAX systems, start the [[SECURITY_SERVER]] which manages the [[Proxy database|proxy database]] and [[Intrusion database|intrusion database]] | * On VAX systems, start the [[SECURITY_SERVER]] which manages the [[Proxy database|proxy database]] and [[Intrusion database|intrusion database]] | ||
* Start the [[License Management Facility|LMF]] and load all appropriate [[Product Authorization Keys|PAK]] from the LMF database. | * Start the [[License Management Facility|LMF]] and load all appropriate [[Product Authorization Keys|PAK]] from the LMF database. | ||
| + | |||
11. Perform the following steps in no specified order: | 11. Perform the following steps in no specified order: | ||
| + | |||
* Enable [[OPCOM|operator consoles]] and the [[Operator log|operator log]] files | * Enable [[OPCOM|operator consoles]] and the [[Operator log|operator log]] files | ||
* Start the [[SMISERVER]] process | * Start the [[SMISERVER]] process | ||
The order of the startup phases is determined in the database file [[VMS$PHASES.DAT]]. | The order of the startup phases is determined in the database file [[VMS$PHASES.DAT]]. | ||
Latest revision as of 05:35, 14 February 2019
System startup is a complex of events that occur when an OpenVMS system is booted.
Startup Phases
1. Start the CLUSTER_SERVER process.
2. Define logical names needed for basic operations and install images listed in SYS$MANAGER:VMSIMAGES.DAT.
3. Execute SYCONFIG.COM.
4. Add any new drivers by executing AUTOCONFIGURE ALLVAX/IO AUTOCONFIGUREAlpha and I64
5. Install the primary swap file, if the file is present.
6. Start the CONFIGURE process unless NOAUTOCONFIG is set to 1 or STARTUP$AUTOCONFIGURE_ALL is defined as False by SYS$MANAGER:SYCONFIG.COM.
7. Execute SYLOGICALS.COM. At this point, all the devices are available either through the AUTOCONFIGURE command or through the CONFIGURE process.
8. If the system is a satellite node in a VAXcluster or an OpenVMS Cluster environment, execute SATELLITE_PAGE.COM to install page and swap files on a local disk. SATELLITE_PAGE.COM is created when you execute the CLUSTER_CONFIG.COM procedure.
9. Execute SYPAGSWPFILES.COM.
10. Perform the following steps in no specified order:
- Install required images
- Start various operating system processes (OPCOM, CACHE_SERVER, ERRFMT, JOBCTL)
- Execute SYSECURITY.COM and starts the AUDIT_SERVER process
- On VAX systems, start the SECURITY_SERVER which manages the proxy database and intrusion database
- Start the LMF and load all appropriate PAK from the LMF database.
11. Perform the following steps in no specified order:
- Enable operator consoles and the operator log files
- Start the SMISERVER process
The order of the startup phases is determined in the database file VMS$PHASES.DAT.
