Updated: 11 December 1998 |
OpenVMS System Manager's Manual
Previous | Contents | Index |
$ @SYS$SYSTEM:SHUTDOWN SHUTDOWN -- Perform an Orderly System Shutdown How many minutes until final shutdown [0]: 10 Reason for shutdown: [Standalone] MONTHLY PREVENTIVE MAINTENANCE Do you want to spin down the disk volumes [No]? [Return] Do you want to invoke the site-specific shutdown procedure [Yes]? [Return] Should an automatic system reboot be performed [No]? [Return] When will the system be rebooted [later]? 12:30 Shutdown options (enter as a comma-separated list): REMOVE_NODE Remaining nodes in the cluster should adjust quorum CLUSTER_SHUTDOWN Entire cluster is shutting down REBOOT_CHECK Check existence of basic system files SAVE_FEEDBACK Save AUTOGEN feedback information from this boot DISABLE_AUTOSTART Disable autostart queues Shutdown options [NONE] [Return] SHUTDOWN message on AVALON, from user SYSTEM at _AVALON$OPA0: 12:00:00.20 AVALON will shut down in 10 minutes; back up 12:30. Please log off node AVALON. MONTHLY PREVENTIVE MAINTENANCE %SHUTDOWN-I-OPERATOR, This terminal is now an operator's console. %%%%%%%%%%% OPCOM, 16-MAY-1998 12:01:00.15 %%%%%%%%%%% Operator status for operator _AVALON$OPA0: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled. %SET-I-INTSET, login interactive limit = 0 current interactive value = 17 %SHUTDOWN-I-SHUTNET, The DECnet network will now be shut down. SHUTDOWN message on AVALON, from user SYSTEM at _AVALON$OPA0: 12:05:00.20 AVALON will shut down in 5 minutes; back up 12:30. Please log off node AVALON. MONTHLY PREVENTIVE MAINTENANCE 17 terminals have been notified on AVALON. SHUTDOWN message on AVALON from user SYSTEM at _AVALON$OPA0: 12:06:55.28 AVALON will shut down in 3 minutes; back up 12:30. Please log off node AVALON. MONTHLY PREVENTIVE MAINTENANCE %%%%%%%%%%% OPCOM, 16-MAY-1998 12:07:12.30 %%%%%%%%%%% Message from user DECnet on AVALON DECnet event 2.0, local node state change From node 2.161 (AVALON), 16-MAY-1998 12:07:22.26 Operator command, Old state = On, New state = Shut SHUTDOWN message on AVALON user SYSTEM at _AVALON$OPA0: 12:08:12.56 AVALON will shut down in 2 minutes; back up 12:30. Please log off node AVALON. MONTHLY PREVENTIVE MAINTENANCE %%%%%%%%%%% OPCOM, 16-MAY-1998 12:08:12:30 %%%%%%%%%%% Message from user JOB_CONTROL on AVALON -SYSTEM-S-NORMAL, normal successful completion %%%%%%%%%%% OPCOM, 16-MAY-1998 12:08:42.30 %%%%%%%%%%% Message from user DECNET on AVALON DECnet shutting down %SYSTEM-I-STOPQUEUES, The queues on this node will now be stopped. SHUTDOWN message on AVALON from user SYSTEM at _AVALON$OPA0: 12:09:12.56 AVALON will shut down in 1 minute; back up 12:30. Please log off node AVALON. MONTHLY PREVENTIVE MAINTENANCE SHUTDOWN message on AVALON, from user SYSTEM at _AVALON$OPA0: 12:10:00.20 AVALON will shut down in 0 minutes; back up 12:30. Please log off node AVALON. MONTHLY PREVENTIVE MAINTENANCE 17 terminals have been notified on AVALON %SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked. %SHUTDOWN-I-STOPUSER, All user processes will now be stopped. %SHUTDOWN-I-REMOVE, All installed images will now be removed. %SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted. %%%%%%%%%%% OPCOM, 16-MAY-1998 12:09:42.30 %%%%%%%%%%% Message from user System on AVALON _AVALON$OPA0:, AVALON shutdown was requested by the operator. %%%%%%%%%%% OPCOM, 16-MAY-1998 12:10:02.44 %%%%%%%%%%% Logfile was closed by operator _AVALON$OPA0: Logfile was SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;8 %%%%%%%%%%% OPCOM, 16-MAY-1998 12:10:32.20 %%%%%%%%%%% Operator _AVALON$OPA0: has been disabled, username SYSTEM SYSTEM SHUTDOWN COMPLETE |
On VAX systems, the following message is also displayed:
USE CONSOLE TO HALT SYSTEM |
Halt the system after you see this message.
4.8.2 Understanding the Order of Shutdown Events
The following events occur as the shutdown proceeds. The procedure displays the corresponding messages on the terminal.
Should an automatic system reboot be performed [No]? |
SYSTEM SHUTDOWN COMPLETE |
USE CONSOLE TO HALT SYSTEM |
In addition to choosing shutdown options when you execute SHUTDOWN.COM, you can customize SHUTDOWN.COM to meet the needs of your site in the following ways.
Method | For More Information |
---|---|
Defining logical names | Section 4.8.3.1 |
Modifying the site-specific shutdown command procedure | Section 4.8.3.2 |
Before executing SHUTDOWN.COM, you can define the following logical names to control the operations of the command procedure:
Logical Name | Description |
---|---|
SHUTDOWN$DECNET_MINUTES | Defines the number of minutes remaining before DECnet is shut down; must be defined with the /SYSTEM qualifier. The default is 6 minutes. |
SHUTDOWN$DISABLE_AUTOSTART | Specifies the number of minutes between the time autostart is disabled for queues and the time the system is shut down; must be defined with the /SYSTEM qualifier. For more information, see Section 13.7.1.9. |
SHUTDOWN$INFORM_NODES | Specifies a list of OpenVMS Cluster nodes to be notified when the system is shutting down. This logical name is described in detail in this section. |
SHUTDOWN$MINIMUM_MINUTES | Defines the minimum number of minutes you can specify as number of minutes to shutdown. For example, if your users require 30 minutes' notice before a system shutdown, define this logical name to be 30. This logical must be defined with the /SYSTEM qualifier. |
SHUTDOWN$QUEUE_MINUTES | Defines the number of minutes remaining before shutdown when queues are shut down; must be defined with the /SYSTEM qualifier. The default is 1 minute. |
SHUTDOWN$TIME | Defines the absolute time of the shutdown; must be defined with the /SYSTEM qualifier. |
SHUTDOWN$VERBOSE | If defined to any string, specifies that the shutdown command procedure is to list each disk as it is dismounted. |
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.
4.8.4 Performing an Orderly Shutdown with SYSMAN
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.
$ 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.
When you use this option, all locally attached disks are dismounted clusterwide. Therefore, you must shut down applications on other nodes that have open files on the locally attached disks. Failure to do so might cause mount verify timeout problems as well as application problems. |
[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. |
$ 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, refer to the OpenVMS System Management Utilities Reference Manual.
4.8.5 Performing an Emergency Shutdown with the OPCCRASH.EXE Program
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.
Run the OPCCRASH.EXE program directly only if SHUTDOWN.COM fails. |
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 |
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.
4.8.6 Performing an Emergency Shutdown Using Console Commands
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.
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:
Previous | Next | Contents | Index |
Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal |
6017PRO_011.HTML
|