回复： Writing the System Dump File to an Alternate Disk for OpenVMS

[ji shao sheng]

You can write the system dump file to a device other than the system disk (DOSD) on OpenVMS systems.

This is especially useful in large-memory systems and in clusters with common system disks where sufficient

disk space is not always available on one disk to support customer dump file requirements.

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:

• The dump device directory structure must resemble the current system disk structure. The

[SYS

n.SYSEXE]SYSDUMP.DMP file will reside there, with the same boot time system root.

Use AUTOGEN to create this file. In the MODPARAMS.DAT file, the following symbol prompts

AUTOGEN to create the file:

DUMPFILE_DEVICE = "$nnn$ddcuuuu"

You can enter a list of devices.

• The dump disk must have an ODS-2 or ODS-5 file structure.

• The dump device cannot be part of a volume set.

• Although not a requirement, HP recommends that you mount the dump device during system startup. If

the dump device is mounted, it can be accessed by CLUE and AUTOGEN and for the analysis of crash

dumps. For best results, include the MOUNT command in SYS$MANAGER:SYCONFIG.COM.

• For the Crash Log Utility Extractor (CLUE) to support DOSD, you must define the logical name

CLUE$DOSD_DEVICE to point to the dump file to be analyzed after a system crash. For instructions,

refer to Section 2.9.

• The dump device cannot be part of a shadow set unless it is also the system device and the master

member of the shadow set.

• On Alpha systems, use the following format to specify the dump device environment variable

DUMP_DEV at the console prompt:

>>>

SET DUMP_DEV device-name[,...]

[colin1992]

最近刚好给客户做了DUMP文件的设置调整，平台是IA64，具体的步骤如下：

1.初始化磁盘，该磁盘是专供dump使用

INIT/NOHIGH $3$DKA300: DUMPDEV

2.挂载该dump磁盘
MOUNT/SYS/NOASSIST/NOREBUILD $3$DKA300: DUMPDEV DUMPDEV$

3.手动生成所需的dump目录
CREATE/DIR $3$DKA300:[SYS0.SYSEXE]

4.在sysgen中调整dumpstyle参数为13
MC SYSGEN SET DUMPSTYLE 13

5.执行boot_options，调整dump_dev, 指向新增的dump磁盘
@BOOT_OPTIONS.COM   $! manually setup DUMP_DEV

6.在dump磁盘上手动生成dump文件，size的大小是block数。所需时间根据dump文件大小，可能会很长。
MC SYSGEN CREATE $3$DKA300:[SYS0.SYSEXE]SYSDUMP.DMP /SIZE= 41943040

7.卸载dump磁盘
dismount DUMPDEV$

重启服务器，新的dump设置应该就生效了。如果可能的话，可以用ctrl+p测试dump的设置是否成功。

[专属天使]

学习了