Difference between revisions of "STARTUP.COM"
| Line 2: | Line 2: | ||
following startup tasks: | following startup tasks: | ||
* Define systemwide logical names required for the symbolic debugger, language processors, linker, image activator, and help processor. | * Define systemwide logical names required for the symbolic debugger, language processors, linker, image activator, and help processor. | ||
| − | * Start processes that control [[Error logging|error logging]], [[SMISERVER]] (the system management server), the [[JOB_CONTROL|job controller]], the [[OPCOM|operator log file]], and [[Security | + | * Start processes that control [[Error logging|error logging]], [[SMISERVER]] (the system management server), the [[JOB_CONTROL|job controller]], the [[OPCOM|operator log file]], and [[Security Auditing|security uditing]]. |
* Connect devices that are physically attached to the system by invoking the [[SYCONFIG.COM]] procedure. | * Connect devices that are physically attached to the system by invoking the [[SYCONFIG.COM]] procedure. | ||
* Configure devices and load their I/O drivers. | * Configure devices and load their I/O drivers. | ||
Latest revision as of 14:07, 3 December 2019
STARTUP.COM is the site-independent startup command procedure supplied with OpenVMS. It uses a series of command procedures, executable images, and database files to perform the following startup tasks:
- Define systemwide logical names required for the symbolic debugger, language processors, linker, image activator, and help processor.
- Start processes that control error logging, SMISERVER (the system management server), the job controller, the operator log file, and security uditing.
- Connect devices that are physically attached to the system by invoking the SYCONFIG.COM procedure.
- Configure devices and load their I/O drivers.
- Install known images to reduce I/O overhead in activating the most commonly run images or to identify images that must have special privileges.
Site-specific startup command procedures
STARTUP.COM executes the following site-specific startup command procedures in this order:
