HP OpenVMS System Manager's Manual, Volume 2:... |
Managing Page, Swap, and Dump Files |
|
|
| |
Writing the System Dump File to an Alternate Disk
Requirements for DOSD are somewhat different on Alpha and I64 systems than on VAX systems. On all systems, however, you must correctly enable the DUMPSTYLE system parameter to enable the bugcheck code to write the system dump file to an alternate device.
The following sections describe the requirements for DOSD on Alpha, I64, and VAX systems.
DOSD Requirements on Alpha and I64 Systems ![]()
On Alpha and I64 systems, DOSD has the following requirements:
DUMPFILE_DEVICE = "$nnn$ddcuuuu"You can enter a list of devices.
SET DUMP_DEV device-name[,...]On DEC 3000 series systems, the following restrictions
on the use of the DUMP_DEV environment variable exist:
|
$ @SYS$MANAGER:BOOT_OPTIONSShell> FSn:\EFI\VMS\VMS_SET DUMP_DEV device-name[,...]
(where: FSn: is any bootable FAT file-structured partition that includes the VMS_SET utility)Designating the Dump Device on Alpha Systems![]()
To designate the dump device with the DUMP_DEV environment variable, follow these steps:
>>>SHOW BOOTDEF_DEV
BOOTDEF_DEV dub204.7.0.4.3,dua204.4.0.2.3
>>>SHOW DEVICES
Resetting IO subsystem... dua204.4.0.2.3 $4$DUA204 (RED70A) RA72 dua206.4.0.2.3 $4$DUA206 (RED70A) RA72 dua208.4.0.2.3 $4$DUA208 (RED70A) RA72 polling for units on cixcd1, slot 4, xmi0... dub204.7.0.4.3 $4$DUA204 (GRN70A) RA72 dub206.7.0.4.3 $4$DUA206 (GRN70A) RA72 dub208.7.0.4.3 $4$DUA208 (GRN70A) RA72 >>>In this example:
In this example, dua208.4.0.2.3 and dub208.7.0.4.3 are paths to the dump device; dub204.7.0.4.3 and dua204.4.0.2.3 are paths to the boot device.>>>SET DUMP_DEV dua208.4.0.2.3,dub208.7.0.4.3,dub204.7.0.4.3,dua204.4.0.2.3
>>>SHOW *
auto_action HALT baud 9600 boot_dev dua204.4.0.2.3 boot_file boot_osflags 0,0 boot_reset ON bootdef_dev dub204.7.0.4.3,dua204.4.0.2.3 booted_dev dua204.4.0.2.3 booted_file booted_osflags 0,0 cpu 0 cpu_enabled ff cpu_primary ff d_harderr halt d_report summary d_softerr continue dump_dev dua208.4.0.2.3,dub208.4.0.4.3,dub204.7.0.4.3,dua204.4.0.2.3 enable_audit ON interleave default language 36 pal V5.48-3/O1.35-2 prompt >>> stored_argc 2 stored_argv0 B stored_argv1 dua204.4.0.2.3 system_variant 0 version T4.3-4740 Jun 14 2003 15:16:38 >>>
After you complete this section, refer to " Enabling DOSD on Alpha and I64 Systems," which follows the next section.
Designating the Dump Device on I64 Systems![]()
You can designate the dump device on I64 systems by using either of the following:
| HP recommends that you use the use the OpenVMS I64 Boot Manager Utility. (Use of the utility is optional for other devices but mandatory for Fibre Channel devices.) For more information on this utility, refer to the HP OpenVMS System Manager's Manual, Volume 1: Essentials. |
To designate the dump device with the DUMP_DEV environment variable from the OpenVMS DCL prompt, follow these steps:
$ @SYS$MANAGER:BOOT_OPTIONS.COMEnter your choice: DOpenVMS I64 Boot Manager Dump Options List Management Utilities
(1) ADD an entry to the Dump Options list (2) DISPLAY the Dump Options list (3) REMOVE an entry from the Dump Options list (4) MOVE the position of an entry in the Dump Options list (B) Set to operate on the Boot Device Options list (D) Set to operate on the Dump Device Options list (G) Set to operate on the Debug Device Options list (E) EXIT from the Boot Manager utility You can also enter Ctrl-Y at any time to abort this utility.
While using this utility, you can change a response
by typing the up-arrow (^) as many times as you
need to. To end the program and return to the DCL prompt, enter
Ctrl/Y. |
Enter your choice: 1Enter the device name (Enter "?" for a list of devices): $1$DGA1
efi$bcfg: $1$DGA1 (VMS_DUMP_DEV_01) Option successfully added
efi$bcfg: $1$DGA1 (VMS_DUMP_DEV_02) Option successfully added
efi$bcfg: $1$DGA1 (VMS_DUMP_DEV_03) Option successfully added
Enter your choice: EUsing the EFI Utilities for OpenVMS VMS_SET Command![]()
You can use the EFI utilities for OpenVMS (I64 only) to specify the dump device environment variable DUMP_DEV at the EFI console prompt:
Shell> FS0:\EFI\VMS\VMS_SHOW DEVICE VMS: EIA0 0-30-6E-39-F7-A5
EFI:Acpi(000222F0,0)/Pci(3|0)/Mac(00306E39F7A5
VMS: DKA0 HP 18.2GATLAS10K3_18_SCAHP05
EFI: Acpi(000222F0,100)/Pci(1|0)/Scsi(Pun0,Lun0)
VMS: DKB400 HP 18.2GST318406LC HP05
EFI: fs2: Acpi(000222F0,100)/Pci(1|1)/Scsi(Pun4,Lun0
VMS: DKB200 HP 18.2GST318406LC HP05
EFI: fs1: Acpi(000222F0,100)/Pci(1|1)/Scsi(Pun2,Lun0)
VMS: DKB0 HP 18.2GATLAS10K3_18_SCAHP05
EFI: fs0: Acpi(000222F0,100)/Pci(1|1)/Scsi(Pun0,Lun0)
VMS: EWA0 0-30-6E-39-77-3
EFI: Acpi(000222F0,100)/Pci(2|0)/Mac(00306E39773D
Shell> FS0:\EFI\VMS\VMS_SET DKA0, DKB0, DKB200VMS: DKA0 HP 18.2GATLAS10K3_18_SCAHP05EFI:
Acpi(000222F0,100)/Pci(1|0)/Scsi(Pun0,Lun0)
VMS: DKB0 HP 18.2GATLAS10K3_18_SCAHP05EFI: fs0:
Acpi(000222F0,100)/Pci(1|1)/Scsi(Pun0,Lun0)
VMS: DKB200 HP 18.2GST318406LC HP05EFI: fs1:
Acpi(000222F0,100)/Pci(1|1)/Scsi(Pun2,Lun0)After you complete this section, refer to the next section.
Enabling DOSD on Alpha and I64 Systems![]()
Finally, enable the DOSD bit of the DUMPSTYLE system parameter
by setting bit 2. For example, enter the value of 4 at the SYSBOOT> prompt to designate an uncompressed physical dump
to an alternate disk with minimal console output:
The HP OpenVMS System Management Utilities Reference Manual and online help contain details about the DUMPSTYLE system parameter.SYSBOOT>SET DUMPSTYLE 4
| The error log dump file is always created
on the system disk so that error log buffers can be restored when
the system is rebooted. This file is not affected by setting the
DUMPSTYLE system parameter or the DUMP_DEV environmental variable. The system chooses the first valid device that it finds in the list as the dump device. Therefore, the dump disk path entries must appear before the system disk entries in the list. On Alpha systems, the number of devices that can be included in DUMP_DEV is limited. This limit varies from platform to platform, and it also depends on the device configuration. Some platforms allow only a single device; others allow a list. Systems that allow a list of devices limit the length of the list to 256 bytes in the internal format that the console subsystem uses. This length provides space for 4 entries if SCSI or CI-based disks are used, and 8 to 9 entries if fibre-channel disks are used. On I64 systems, up to 99 devices can be included in DUMP_DEV, regardless of platform or device configuration. |
DOSD Requirements on VAX Systems ![]()
On VAX systems, DOSD has the following requirements:
DUMPFILE_DEVICE = "$nnn$ddcuuuu"You can list only one device.
| On VAX 7000 configurations, by using bits 16 through 27 of the DUMPSTYLE system parameter. Note that the DUMP_DEV environment variable that is provided on VAX 7000 configurations is not used by OpenVMS VAX. |
| On configurations other than the VAX 7000, by using bits 16 through 27 of register 3 (R3). You can use this portion of the register to specify the dump device. |
| To restore error log buffers when the system is rebooted after a system crash, the error logs must be saved on the system disk. For this purpose, AUTOGEN creates a SYSDUMP.DMP file on the system disk; the file is large enough to contain the maximum size of error log buffers. |
|
|