HP OpenVMS Systems Documentation
OpenVMS System Manager's Manual
|Adding and deleting optional files||Section 5.1|
|Modifying site-specific startup command procedures||Section 5.2|
|Modifying login command procedures||Section 5.3|
|Customizing startup databases||Section 5.4|
|+Registering images that have system version dependencies||Section 5.5|
|Customizing the Help Message database||Section 5.6|
|Customizing Mail||Section 5.7|
|Setting up the Multipurpose Internet Mail Extension (MIME) utility||Section 5.8|
|Saving your customization||Section 5.9|
This chapter explains the following concepts:
|Site-specific startup command procedures||Section 5.2.1|
|The order of startup events||Section 5.2.2|
|Startup databases||Section 5.4.1|
|The layered product startup database||Section 5.4.2|
OpenVMS lets you customize the size of the operating system by deleting or adding optional system files, including support for DECwindows. This is particularly valuable for small systems or systems with limited disk space.
For example, if your system is a MicroVAX II computer with an RD54 system disk and you will not use system programming features such as the Delta/XDelta Debugger (DELTA/XDELTA) or the System Dump Analyzer utility (SDA), you might remove these files from the system disk.
Depending on the system you are using, you can add or delete files in one of the following ways:
An important part of customizing your system is to create or modify
site-specific startup command procedures. Adding commands to these
procedures ensures that the commands are executed each time the system
5.2.1 Understanding Site-Specific Startup Command Procedures
|Startup command procedure||A command procedure that executes when the system starts up.|
|Site-independent startup command procedure||
A startup command procedure that is required for and provided with all
OpenVMS systems, regardless of site-specific requirements. This
procedure is named SYS$SYSTEM:STARTUP.COM.
Do not modify this procedure.
When your system boots, it automatically executes STARTUP.COM. For more information, see Section 4.1.4.
|Site-specific startup command procedures||
Startup command procedures that you can modify to perform operations
specific to your site. Use any text editor to add or modify commands in
STARTUP.COM executes several site-specific startup command procedures that Compaq provides. These procedures are listed in Table 5-1.
You can also create your own procedures and execute them from SYSTARTUP_VMS.COM.
Table 5-1 lists and describes the site-specific startup command procedures provided by Compaq, in the order in which they execute. These procedures are located in the system directory with the logical name SYS$STARTUP.
|1||SYCONFIG.COM||A file to which you add commands for site-specific device configuration. For more information, see Section 5.2.4.|
|2||SYLOGICALS.COM||A file to which you add commands to define your site-specific system logical names. For more information, see Section 5.2.5.|
|3||SYPAGSWPFILES.COM||A file to which you add commands to install page and swap files (other than the primary page and swap files in SYS$SYSTEM, which are installed automatically). For more information, see Section 5.2.3.|
|4||SYSECURITY.COM||A file to which you add commands to define the location of security auditing and security archive files before starting the security auditing server. For more information, see Section 5.2.6.|
|5||SYSTARTUP_VMS.COM||A general-purpose command procedure to which you add commands to perform miscellaneous operations for setting up your site. For example, you might mount public disks in SYSTARTUP_VMS.COM. For more information, see Section 5.2.7.|
Do not modify or delete the Compaq-supplied template command files with the .TEMPLATE file type. The VMSKITBLD.COM procedure uses these files to create a new system disk. If you must use the .TEMPLATE version of the file because your .COM version is damaged, copy the .TEMPLATE file to a file with the .COM file type, and edit the copy.
The startup procedures provided by Compaq should always work. However, if you introduce an error in the startup or login procedures, you can accidentally lock yourself out of the system. Section 4.4.2 describes a boot procedure you can use in such an emergency.
A database file named VMS$PHASES.DAT determines the order of the phases of the startup procedure. It is a sequential list of the phases that STARTUP.COM starts. It includes a series of four basic phases (INITIAL, CONFIGURE, DEVICE, and BASEENVIRON) that start the operating system, followed by a series of phases for layered products.
Do not modify VMS$PHASES.DAT. To start up correctly, the system requires that the contents of this file remain intact.
At startup, a system performs tasks in the following order:
The order of events within system startup might change in future releases of the operating system.
When the system boots, it automatically installs the primary page and swap files, if they are present in the SYS$SYSTEM directory. If the page and swap files are not in SYS$SYSTEM, or if secondary page and swap files are located on a disk other than the system disk, you must install these files each time the system boots. To install these files, add commands to SYPAGSWPFILES.COM.
Before performing this task, you should understand page and swap files and why you might want to move them. For more information, see Section 16.2.
The SYPAGSWPFILES.COM file can also include commands other than INSTALL commands, such as SYSGEN CREATE commands and the DCL commands INITIALIZE and MOUNT, to set up the page and swap files. Note that, at the time STARTUP.COM invokes SYPAGSWPFILES.COM, only the system disk is mounted. Therefore, you might need to add MOUNT commands to SYPAGSWPFILES.COM to mount the disks that hold the page and swap files.
%STARTUP-E-NOPAGFIL, no page files have been successfully installed.
If a system dump file with the name SYSDUMP.DMP does not exist in the SYS$SPECIFIC:[SYSEXE] directory, the primary page file PAGEFILE.SYS must exist in SYS$SPECIFIC:[SYSEXE]PAGEFILE.SYS for writing crash dumps. If neither SYSDUMP.DMP nor PAGEFILE.SYS is located in SYS$SPECIFIC:[SYSEXE], no crash dump file is produced.
You can also use SATELLITE_PAGE.COM to install page and swap files on a satellite node's local disk. SATELLITE_PAGE.COM is created when you run CLUSTER_CONFIG.COM. For more information about installing page and swap files on a satellite node's local disk, refer to OpenVMS Cluster Systems.
SYSGEN> CREATE DUA2:[PAGE_SWAP]PAGEFILE_1.SYS/SIZE=100000 SYSGEN> CREATE DUA2:[PAGE_SWAP]SWAPFILE_1.SYS/SIZE=100000
$ SYSGEN := $SYSGEN
SYSGEN INSTALL file-spec /PAGEFILE
For swap files, use the following format:
SYSGEN INSTALL file-spec /SWAPFILE
The INSTALL command activates secondary page and swap files. Page and swap files not located in SYS$SYSTEM must be installed each time the system boots.
The following commands in SYPAGSWPFILES.COM install secondary page and swap files on the device DUA10: with the logical name PAGE_SWAP:
$ MOUNT/SYSTEM/NOASSIST DUA10: SYS2 PAGE_SWAP $ SYSGEN := $SYSGEN $ SYSGEN INSTALL PAGE_SWAP:[SYSTEM]PAGEFILE1.SYS/PAGEFILE $ if $status then write sys$output "Installed page file PAGEFILE1.SYS" $ SYSGEN INSTALL PAGE_SWAP:[SYSTEM]SWAPFILE1.SYS/SWAPFILE $ if $status then write sys$output "Installed swap file swapfile1.sys"
You can add commands to SYCONFIG.COM to perform site-specific device
configuration, including connecting nonstandard devices and suppressing
188.8.131.52 Connecting Nonstandard Devices
Standard devices are automatically connected and configured by STARTUP.COM each time the system boots. Nonstandard devices (devices not supplied by Compaq) are not automatically connected and configured; you must connect and configure these devices manually by entering certain commands. To execute these commands each time the system starts up, add the commands to SYCONFIG.COM.
On VAX systems, add SYSGEN CONNECT commands. For more information about connecting devices, see Section 8.4. For more information about the SYSGEN CONNECT command, refer to the SYSGEN section of the OpenVMS System Management Utilities Reference Manual.
On Alpha systems, add SYSMAN IO CONNECT commands. For more information about connecting devices, see Section 8.4. For more information about the SYSMAN IO CONNECT command, refer to the SYSMAN section of the OpenVMS System Management Utilities Reference Manual.
To connect a nonstandard device called the QQ device, add the following commands to SYCONFIG.COM:
$ SYSGEN := $SYSGEN $ SYSGEN CONNECT QQA0
You can define a symbol in SYCONFIG.COM to suppress autoconfiguration. For more information, see Section 8.4.3.