Halt and Shutdown Procedures
» Table of Contents |  | | » Glossary | | | » Index | | |
| | |
| ||
| ||
The following sections describe halt and shutdown procedures for Integrity servers and OpenVMS I64.
If your system hangs and you want to force a crash, you can use MP, if available. Use the tc command. Confirm your intention when prompted. The tc command forces a crash dump. You can reset the machine (without forcing a crash) by using the MP rs command.
For cell-based servers, when you enter the tc or rs command, you are first prompted to select the partition for which you want the operating system shut down.
Alternatively, when the operating system controls the console, press Ctrl/P. The next step taken by the system depends on whether XDELTA is loaded:
If XDELTA is loaded, the system enters XDELTA after you press Ctrl/P. The system displays the instruction pointer and current instructions. You can force a crash from XDELTA by entering ;C, as in the following example:
$
Console Brk at 8068AD40
8068AD40! add r16 = r24, r16 ;; (New IPL = 3)
;CIf XDELTA is not loaded, pressing Ctrl/P causes the system to enter the IPC facility. Pressing Ctrl/P within the utility brings the “Crash? (Y/N)” prompt. Enter Y to cause the system to crash and to bring you eventually to EFI. If you enter any other character, the system returns back to the IPC facility.
Before you shut down the operating system, decide if you want it to reboot automatically or if you want to enter console-mode commands after the shutdown completes. If you want the system to reboot automatically after the shutdown, first set up automatic booting, as described in “Setting Boot Options for Your System Disk”.
You can perform the following two types of shutdown operations, as discussed in the indicated sections:
An orderly shutdown with SYS$SYSTEM:SHUTDOWN.COM (see “Orderly Shutdown”)
An emergency shutdown with OPCCRASH.EXE (see “Emergency Shutdown with OPCCRASH.EXE”)
The SHUTDOWN.COM procedure shuts down the operating system while performing maintenance functions such as disabling future logins, stopping the batch and printer queues, dismounting volumes, and stopping user processes. To use the SHUTDOWN.COM command procedure, log in to the SYSTEM account, enter the following command:
|
|
|
For more information about the SHUTDOWN.COM command procedure, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials.
On cell-based Integrity servers, two special types of nPartition reboot are supported: reboot for reconfiguration, which reboots an nPartition and enables cell configuration changes to occur, and shutdown for reconfiguration, which puts an nPartition into an inactive state.
To perform a reboot for reconfiguration from OpenVMS I64 running on an nPartition, enter the OpenVMS @SYS$SYSTEM:SHUTDOWN command and then answer YES to the prompt asking whether to perform an automatic system reboot.
On cell-based Integrity servers, an operating system reboot is equivalent to a reboot for reconfiguration. Performing a reboot for reconfiguration enables any cell assignment changes for the nPartition (for example, removing an active cell or activating a newly added cell).
The reboot for reconfiguration takes all cells assigned to the nPartition through a cell boot phase. The cells with a Yes use-on-next-boot attribute proceed through the nPartition boot phase to become active cells whose resources are available to software running on the nPartition.
To perform a shutdown for reconfiguration of an nPartition running OpenVMS I64, first enter the OpenVMS @SYS$SYSTEM:SHUTDOWN command and then answer NO to the prompt asking whether to perform an automatic system reboot. Next, access MP and use the rr command (specify the OpenVMS nPartition to shutdown for reconfiguration).
A shutdown for reconfiguration takes all cells assigned to the nPartition through a cell boot phase and then stops their boot progress at the boot-is-blocked (BIB) state. When all cells assigned to the nPartition are at the BIB state, the nPartition is inactive and no software can run on the nPartition until it is manually booted past BIB.
To boot an inactive nPartition past BIB, use the MP bo command and specify which nPartition to make active. Booting past the BIB state involves all cells that are assigned to the nPartition and that have a Yes use-on-next-boot attribute. The cells are taken through the nPartition boot phase to become active cells whose resources are available to software running on the nPartition.
For more information about shutting down an Integrity server or an nPartition, see the appropriate hardware documentation.
If you cannot perform an orderly shutdown with the SHUTDOWN.COM procedure, run the OPCCRASH.EXE emergency shutdown program. To run the OPCCRASH.EXE program, log in to the SYSTEM account and enter the following command:
|
|
|
For more information about the OPCCRASH program, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials.
On cell-based Integrity servers, entering the OpenVMS RUN SYS$SYSTEM:OPCCRASH command results in the system dumping memory and then halting at the P00>>> prompt. To reset the nPartition following OPCRASH, access the nPartition console and press any key to reboot.
Using the MP tc command to reset an nPartition results in the system dumping memory and then automatically resetting the nPartition.