![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
If you plan to use an option every time you use SHUTDOWN.COM, define the logical name in the site-specific startup command procedure SYLOGICALS.COM. For more information, see Section 5.2.5.
Specifying a List of Nodes to Be Notified When the System Is
Shutting Down
You can define the logical name SHUTDOWN$INFORM_NODES to be a list of OpenVMS Cluster nodes that are notified when the system is shut down. You must define SHUTDOWN$INFORM_NODES before executing SYS$SYSTEM:SHUTDOWN.COM.
To define SHUTDOWN$INFORM_NODES, enter a command in the following format:
DEFINE SHUTDOWN$INFORM_NODES "node-list"
where node-list specifies the list of nodes to be informed. For example:
$ DEFINE SHUTDOWN$INFORM_NODES "NODE1,NODE2,NODE3"
If you plan to inform the same nodes every time you shut down the system, add the command to the site-specific startup command procedure SYLOGICALS.COM. For more information, see Section 5.2.5.
If you define SHUTDOWN$INFORM_NODES, all member nodes included in the list are notified when you execute SHUTDOWN.COM. Users on the node that is being shut down are always notified, regardless of whether you define SHUTDOWN$INFORM_NODES. If you omit the name of the node that is being shut down from the list specified in the DEFINE command, SHUTDOWN.COM automatically adds the name to the list.
The information in Table 4-3 indicates which nodes are notified at different phases of the shutdown sequence, depending on whether SHUTDOWN$INFORM_NODES is defined.
| Shutdown Phase | If SHUTDOWN$INFORM_NODES Is Not Defined |
If SHUTDOWN$INFORM_NODES Is Defined |
|---|---|---|
| First shutdown notification | Notify all terminals on all nodes | Notify all terminals on all listed nodes |
| Between first shutdown notification and 2 minutes before final shutdown | Notify all terminals logged in to the node that is shutting down | Notify all users logged in on all listed nodes |
| Between 2 minutes before final shutdown notification until final shutdown | Notify all users logged in on all nodes | Notify all users logged in on all listed nodes |
| Shutdown canceled | Notify all terminals on all nodes | Notify all terminals on all listed nodes |
You can add site-specific commands to the site-specific shutdown procedure SYS$MANAGER:SYSHUTDWN.COM. An empty SYSHUTDWN.COM file is included in your distribution kit.
SHUTDOWN.COM prompts you to indicate if you want to execute the site-specific procedure SYSHUTDWN.COM:
Do you want to invoke the site-specific shutdown procedure [Yes]?
Press Return to accept the default answer YES.
The advantage of using the System Management Utility (SYSMAN) for shutdown is that you can shut down a group of nodes quickly. SYSMAN enables you to enter all of the shutdown parameters in one command line, rather than responding to the interactive dialog in SHUTDOWN.COM. SYSMAN does not wait for the nodes to shut down before you can use other SYSMAN commands; the interface returns immediately.
How to Perform This Task
$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> SHUTDOWN NODE/[qualifier]
Qualifiers can be any of the following options:
| Qualifier | Function |
|---|---|
| MINUTES_TO_SHUTDOWN | Indicates the number of minutes until shutdown occurs. |
| REASON | Indicates the reason for the shutdown. |
| REBOOT_TIME | Indicates the time you expect to reboot the system, such as LATER, 2 P.M., or 14:00. This time is displayed in the shutdown message to users. |
| [NO]SPIN_DOWN_DISKS | Spins down disks. The default is NO. You cannot spin down the system disk. |
| [NO]INVOKE_SYSHUTDOWN | Invokes the site-specific shutdown procedure. The default is INVOKE_SYSHUTDOWN. |
| [NO]AUTOMATIC_REBOOT | Reboots the system automatically when the shutdown is complete. The default is NO. |
| [NO]REBOOT_CHECK | Checks for basic operating system files and notifies you if any are missing. The default is NO. |
| [NO]CLUSTER_SHUTDOWN | Shuts down the entire OpenVMS Cluster system. The default is NO. |
| [NO]REMOVE_NODE | Removes the node from the active cluster quorum; use this when you do not expect the shut-down node to rejoin the cluster for an extended period. The default is NO. |
| [NO]SAVE_FEEDBACK | Records feedback data from the system since it was last booted and creates a new version of the AUTOGEN feedback data file, which you can use the next time you run AUTOGEN. The default is NO. |
Example
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> SHUTDOWN NODE/MINUTES_TO_SHUTDOWN=10/REBOOT_TIME="later" - _SYSMAN> /REASON="DISK CORRUPTION PROBLEMS"/REBOOT_CHECK/SAVE_FEEDBACK
If you enter this command example on NODE21, it requests a shutdown on NODE21 with:
SHUTDOWN message on node NODE21, from user SYSTEM at _NODE21$0PA0: 12:00:00:20. NODE21 will shut down in 10 minutes; back up later. Please log off node NODE21. DISK CORRUPTION PROBLEMS
For more information, see the OpenVMS System Management Utilities Reference Manual.
Ordinarily, you shut down the system using the orderly shutdown procedure SHUTDOWN.COM. After SHUTDOWN.COM performs orderly housekeeping tasks, it invokes the program SYS$SYSTEM:OPCCRASH.EXE to shut down the system. OPCCRASH.EXE performs only the following minimal housekeeping functions:
In an emergency, if you cannot invoke SHUTDOWN.COM, you can run the OPCCRASH.EXE program to shut down your system immediately without performing any of the housekeeping functions that ensure an orderly shutdown.
Note
Run the OPCCRASH.EXE program directly only if SHUTDOWN.COM fails.
How to Perform This Task
To run the OPCCRASH.EXE program directly, you must have the CMKRNL privilege. You can enter the commands from any terminal and any privileged account. Follow these steps:
$ RUN SYS$SYSTEM:OPCCRASH
SYSTEM SHUTDOWN COMPLETE
USE CONSOLE TO HALT SYSTEM
Example
The following example runs the OPCCRASH program to force a system crash, and halts the system:
$ RUN SYS$SYSTEM:OPCCRASH
SYSTEM SHUTDOWN COMPLETE
[Ctrl/P]
>>>HALT
HALTED AT 8000708A
On VAX systems, the following message is also displayed:
USE CONSOLE TO HALT SYSTEM
Halt the system when you see this message.
Certain computer consoles have an additional emergency CRASH command. If your computer has the CRASH command, it is located on the console media; you can execute it only from the console prompt on the console terminal. For example:
P00>>> CRASH
If the CRASH command does not exist on your console, you can shut down the system manually from the console.
Note
Use CRASH commands from the console only if the OPCCRASH.EXE program fails.
On VAX systems, enter the following commands:
P00>>> D PSL 041F0000 P00>>> D PC FFFFFFFF P00>>> CON
On Alpha systems, enter the following commands:
P00>>> D PS 1F00 P00>>> D PC FFFFFFFFFFFFFF00 P00>>> CON
See one of the following manuals for a description of the CRASH command or for equivalent commands to use to force an abrupt emergency shutdown:
After you install the operating system, you can customize it for site-specific requirements.
Information Provided in This Chapter
This chapter describes the following tasks:
| Task | Section |
|---|---|
| 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 correct time zone information on your system | Section 5.8 |
| ++ Setting time using the Battery-Backed Watch (BBW) | Section 5.9 |
| Choosing languages, and date and time formats | Section 5.10 |
| Saving your customization | Section 5.11 |
This chapter explains the following concepts:
| Concept | Section |
|---|---|
| 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 reboots.
You should understand the following terms:
| Term | Definition |
|---|---|
| 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.3. |
| 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
these procedures.
STARTUP.COM executes several site-specific startup command procedures that Digital 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 Digital, in the order in which they execute. These procedures are located in the system directory with the logical name SYS$STARTUP.
| Order | Command Procedure | Function |
|---|---|---|
| 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. |
Your distribution kit provides two versions of each site-specific command procedure in the directory SYS$MANAGER:
Note
Do not modify or delete the Digital-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.
When modifying site-specific startup command procedures, be sure to follow these rules:
Caution
The startup procedures provided by Digital 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.
Before modifying the site-specific startup command procedures, you should understand the order of system startup events.
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.
Caution
Do not modify VMS$PHASES.DAT. To start up correctly, the system requires that the contents of this file remain intact.
On starting up, a system performs tasks in the following order:
Note
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 15.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.
The system must have installed at least one page file before SYPAGSWPFILES.COM exits. Otherwise, STARTUP.COM displays the following error message:
%STARTUP-E-NOPAGFIL, no page files have been successfully installed.
Caution
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 on installing page and swap files on a satellite node's local disk, see OpenVMS Cluster Systems.
How to Perform This Task
CREATE file-spec/SIZE=block-count
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
SYSGEN INSTALL file-spec /SWAPFILE
6017P009.HTM OSSG Documentation 22-NOV-1996 14:21:29.12
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.