<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Alpha 服务器中的主题 Writing the System Dump File to an Alternate Disk for   OpenVMS</title>
    <link>https://community.hpe.com/t5/alpha-%E6%9C%8D%E5%8A%A1%E5%99%A8/writing-the-system-dump-file-to-an-alternate-disk-for-openvms/m-p/6216717#M1341</link>
    <description>&lt;P align="left"&gt;You can write the system dump file to a device other than the system disk (DOSD) on OpenVMS systems.&lt;/P&gt;&lt;P align="left"&gt;This is especially useful in large-memory systems and in clusters with common system disks where sufficient&lt;/P&gt;&lt;P align="left"&gt;disk space is not always available on one disk to support customer dump file requirements.&lt;/P&gt;&lt;P align="left"&gt;Requirements for DOSD are somewhat different on Alpha and I64 systems than on VAX systems. On all&lt;/P&gt;&lt;P align="left"&gt;systems, however, you must correctly enable the DUMPSTYLE system parameter to enable the bugcheck&lt;/P&gt;&lt;P align="left"&gt;code to write the system dump file to an alternate device.&lt;/P&gt;&lt;P&gt;The following sections describe the requirements for DOSD on Alpha, I64, and VAX systems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left"&gt;DOSD Requirements on Alpha and I64 Systems&lt;/P&gt;&lt;P align="left"&gt;On Alpha and I64 systems, DOSD has the following requirements:&lt;/P&gt;&lt;P align="left"&gt;• The dump device directory structure must resemble the current system disk structure. The&lt;/P&gt;&lt;P align="left"&gt;[SYS&lt;/P&gt;&lt;P&gt;&lt;FONT size="2" face="Courier"&gt;&lt;FONT size="2" face="Courier"&gt;n&lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT size="2" face="NewCenturySchlbk-Roman"&gt;&lt;FONT size="2" face="NewCenturySchlbk-Roman"&gt;&lt;FONT size="2" face="NewCenturySchlbk-Roman"&gt;.SYSEXE]SYSDUMP.DMP file will reside there, with the same boot time system root.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;Use AUTOGEN to create this file. In the MODPARAMS.DAT file, the following symbol prompts&lt;/P&gt;&lt;P align="left"&gt;AUTOGEN to create the file:&lt;/P&gt;&lt;P align="left"&gt;DUMPFILE_DEVICE = "$nnn$ddcuuuu"&lt;/P&gt;&lt;P align="left"&gt;You can enter a list of devices.&lt;/P&gt;&lt;P align="left"&gt;• The dump disk must have an ODS-2 or ODS-5 file structure.&lt;/P&gt;&lt;P align="left"&gt;• The dump device cannot be part of a volume set.&lt;/P&gt;&lt;P align="left"&gt;• Although not a requirement, HP recommends that you mount the dump device during system startup. If&lt;/P&gt;&lt;P align="left"&gt;the dump device is mounted, it can be accessed by CLUE and AUTOGEN and for the analysis of crash&lt;/P&gt;&lt;P align="left"&gt;dumps. For best results, include the MOUNT command in SYS$MANAGER:SYCONFIG.COM.&lt;/P&gt;&lt;P align="left"&gt;• For the Crash Log Utility Extractor (CLUE) to support DOSD, you must define the logical name&lt;/P&gt;&lt;P align="left"&gt;CLUE$DOSD_DEVICE to point to the dump file to be analyzed after a system crash. For instructions,&lt;/P&gt;&lt;P align="left"&gt;refer to Section 2.9.&lt;/P&gt;&lt;P align="left"&gt;• The dump device cannot be part of a shadow set unless it is also the system device and the master&lt;/P&gt;&lt;P align="left"&gt;member of the shadow set.&lt;/P&gt;&lt;P align="left"&gt;• On Alpha systems, use the following format to specify the dump device environment variable&lt;/P&gt;&lt;P align="left"&gt;DUMP_DEV at the console prompt:&lt;/P&gt;&lt;P align="left"&gt;&amp;gt;&amp;gt;&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT size="2" face="Courier"&gt;&lt;FONT size="2" face="Courier"&gt;SET DUMP_DEV &lt;/FONT&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;FONT size="2" face="NewCenturySchlbk-Roman"&gt;&lt;FONT size="2" face="NewCenturySchlbk-Roman"&gt;device-name[,...]&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 25 Sep 2013 13:00:54 GMT</pubDate>
    <dc:creator>ji shao sheng</dc:creator>
    <dc:date>2013-09-25T13:00:54Z</dc:date>
    <item>
      <title>Writing the System Dump File to an Alternate Disk for   OpenVMS</title>
      <link>https://community.hpe.com/t5/alpha-%E6%9C%8D%E5%8A%A1%E5%99%A8/writing-the-system-dump-file-to-an-alternate-disk-for-openvms/m-p/6216717#M1341</link>
      <description>&lt;P align="left"&gt;You can write the system dump file to a device other than the system disk (DOSD) on OpenVMS systems.&lt;/P&gt;&lt;P align="left"&gt;This is especially useful in large-memory systems and in clusters with common system disks where sufficient&lt;/P&gt;&lt;P align="left"&gt;disk space is not always available on one disk to support customer dump file requirements.&lt;/P&gt;&lt;P align="left"&gt;Requirements for DOSD are somewhat different on Alpha and I64 systems than on VAX systems. On all&lt;/P&gt;&lt;P align="left"&gt;systems, however, you must correctly enable the DUMPSTYLE system parameter to enable the bugcheck&lt;/P&gt;&lt;P align="left"&gt;code to write the system dump file to an alternate device.&lt;/P&gt;&lt;P&gt;The following sections describe the requirements for DOSD on Alpha, I64, and VAX systems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left"&gt;DOSD Requirements on Alpha and I64 Systems&lt;/P&gt;&lt;P align="left"&gt;On Alpha and I64 systems, DOSD has the following requirements:&lt;/P&gt;&lt;P align="left"&gt;• The dump device directory structure must resemble the current system disk structure. The&lt;/P&gt;&lt;P align="left"&gt;[SYS&lt;/P&gt;&lt;P&gt;&lt;FONT size="2" face="Courier"&gt;&lt;FONT size="2" face="Courier"&gt;n&lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT size="2" face="NewCenturySchlbk-Roman"&gt;&lt;FONT size="2" face="NewCenturySchlbk-Roman"&gt;&lt;FONT size="2" face="NewCenturySchlbk-Roman"&gt;.SYSEXE]SYSDUMP.DMP file will reside there, with the same boot time system root.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P align="left"&gt;Use AUTOGEN to create this file. In the MODPARAMS.DAT file, the following symbol prompts&lt;/P&gt;&lt;P align="left"&gt;AUTOGEN to create the file:&lt;/P&gt;&lt;P align="left"&gt;DUMPFILE_DEVICE = "$nnn$ddcuuuu"&lt;/P&gt;&lt;P align="left"&gt;You can enter a list of devices.&lt;/P&gt;&lt;P align="left"&gt;• The dump disk must have an ODS-2 or ODS-5 file structure.&lt;/P&gt;&lt;P align="left"&gt;• The dump device cannot be part of a volume set.&lt;/P&gt;&lt;P align="left"&gt;• Although not a requirement, HP recommends that you mount the dump device during system startup. If&lt;/P&gt;&lt;P align="left"&gt;the dump device is mounted, it can be accessed by CLUE and AUTOGEN and for the analysis of crash&lt;/P&gt;&lt;P align="left"&gt;dumps. For best results, include the MOUNT command in SYS$MANAGER:SYCONFIG.COM.&lt;/P&gt;&lt;P align="left"&gt;• For the Crash Log Utility Extractor (CLUE) to support DOSD, you must define the logical name&lt;/P&gt;&lt;P align="left"&gt;CLUE$DOSD_DEVICE to point to the dump file to be analyzed after a system crash. For instructions,&lt;/P&gt;&lt;P align="left"&gt;refer to Section 2.9.&lt;/P&gt;&lt;P align="left"&gt;• The dump device cannot be part of a shadow set unless it is also the system device and the master&lt;/P&gt;&lt;P align="left"&gt;member of the shadow set.&lt;/P&gt;&lt;P align="left"&gt;• On Alpha systems, use the following format to specify the dump device environment variable&lt;/P&gt;&lt;P align="left"&gt;DUMP_DEV at the console prompt:&lt;/P&gt;&lt;P align="left"&gt;&amp;gt;&amp;gt;&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT size="2" face="Courier"&gt;&lt;FONT size="2" face="Courier"&gt;SET DUMP_DEV &lt;/FONT&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;FONT size="2" face="NewCenturySchlbk-Roman"&gt;&lt;FONT size="2" face="NewCenturySchlbk-Roman"&gt;device-name[,...]&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2013 13:00:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/alpha-%E6%9C%8D%E5%8A%A1%E5%99%A8/writing-the-system-dump-file-to-an-alternate-disk-for-openvms/m-p/6216717#M1341</guid>
      <dc:creator>ji shao sheng</dc:creator>
      <dc:date>2013-09-25T13:00:54Z</dc:date>
    </item>
    <item>
      <title>回复： Writing the System Dump File to an Alternate Disk for   OpenVMS</title>
      <link>https://community.hpe.com/t5/alpha-%E6%9C%8D%E5%8A%A1%E5%99%A8/writing-the-system-dump-file-to-an-alternate-disk-for-openvms/m-p/6431022#M1342</link>
      <description>&lt;P&gt;最近刚好给客户做了DUMP文件的设置调整，平台是IA64，具体的步骤如下：&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1.初始化磁盘，该磁盘是专供dump使用&lt;/P&gt;&lt;P&gt;INIT/NOHIGH $3$DKA300: DUMPDEV&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2.挂载该dump磁盘&lt;BR /&gt;MOUNT/SYS/NOASSIST/NOREBUILD $3$DKA300: DUMPDEV DUMPDEV$&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3.手动生成所需的dump目录&lt;BR /&gt;CREATE/DIR $3$DKA300:[SYS0.SYSEXE]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;4.在sysgen中调整dumpstyle参数为13&lt;BR /&gt;MC SYSGEN SET DUMPSTYLE 13&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;5.执行boot_options，调整dump_dev, 指向新增的dump磁盘&lt;BR /&gt;@BOOT_OPTIONS.COM&amp;nbsp;&amp;nbsp; $! manually setup DUMP_DEV&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;6.在dump磁盘上手动生成dump文件，size的大小是block数。所需时间根据dump文件大小，可能会很长。&lt;BR /&gt;MC SYSGEN CREATE $3$DKA300:[SYS0.SYSEXE]SYSDUMP.DMP /SIZE= 41943040&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;7.卸载dump磁盘&lt;BR /&gt;dismount DUMPDEV$&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;重启服务器，新的dump设置应该就生效了。如果可能的话，可以用ctrl+p测试dump的设置是否成功。&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Mar 2014 06:42:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/alpha-%E6%9C%8D%E5%8A%A1%E5%99%A8/writing-the-system-dump-file-to-an-alternate-disk-for-openvms/m-p/6431022#M1342</guid>
      <dc:creator>colin1992</dc:creator>
      <dc:date>2014-03-31T06:42:44Z</dc:date>
    </item>
    <item>
      <title>回复： Writing the System Dump File to an Alternate Disk for   OpenVMS</title>
      <link>https://community.hpe.com/t5/alpha-%E6%9C%8D%E5%8A%A1%E5%99%A8/writing-the-system-dump-file-to-an-alternate-disk-for-openvms/m-p/6758826#M1344</link>
      <description>&lt;P&gt;学习了&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jun 2015 05:59:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/alpha-%E6%9C%8D%E5%8A%A1%E5%99%A8/writing-the-system-dump-file-to-an-alternate-disk-for-openvms/m-p/6758826#M1344</guid>
      <dc:creator>专属天使</dc:creator>
      <dc:date>2015-06-25T05:59:40Z</dc:date>
    </item>
  </channel>
</rss>

