<?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>topic Re: Host-Based Mini-Merge on OpenVMS in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/host-based-mini-merge-on-openvms/m-p/3830048#M77853</link>
    <description>Hi Heinz!&lt;BR /&gt;&lt;BR /&gt;HBMM is Host-Based Mini-Merge.&lt;BR /&gt;&lt;BR /&gt;Your description of DOSD was pretty much known to me, but I like it so short and concise. &lt;BR /&gt;The problem is that only four EVA disks can be defined using wwidmgr, and I have defined four of them and don't want to delete any of them. So it seams that I have to use localy attached disk for DOSD. Am I right?&lt;BR /&gt;&lt;BR /&gt;Best regards&lt;BR /&gt;&lt;BR /&gt;Domen&lt;BR /&gt;Domen</description>
    <pubDate>Tue, 25 Jul 2006 07:05:36 GMT</pubDate>
    <dc:creator>Domen Setar</dc:creator>
    <dc:date>2006-07-25T07:05:36Z</dc:date>
    <item>
      <title>Host-Based Mini-Merge on OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/host-based-mini-merge-on-openvms/m-p/3830046#M77851</link>
      <description>Hi!&lt;BR /&gt;&lt;BR /&gt;I have some questions about using HBMM on OpenVMS V8.2 Alpha servers.&lt;BR /&gt;&lt;BR /&gt;Is it possible to use HBMM on standalone systems with only two physical disks which form one shadowset, becuse in this case dump file must stay on system disk?&lt;BR /&gt;&lt;BR /&gt;We have our Alpha Servers without local disks. We use disks on EVA storage arrays. I can make special disk on EVA for dump file, but I have defined disks on SRM console in the way that both members of system shadow disk are seen over two paths. So I have defined all four boot disks in wwidmgr. Is there a way to define the dump disk not to lose current redundancy?&lt;BR /&gt;&lt;BR /&gt;Best regards&lt;BR /&gt;&lt;BR /&gt;Domen Setar</description>
      <pubDate>Tue, 25 Jul 2006 06:08:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/host-based-mini-merge-on-openvms/m-p/3830046#M77851</guid>
      <dc:creator>Domen Setar</dc:creator>
      <dc:date>2006-07-25T06:08:34Z</dc:date>
    </item>
    <item>
      <title>Re: Host-Based Mini-Merge on OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/host-based-mini-merge-on-openvms/m-p/3830047#M77852</link>
      <description>Hi Domen&lt;BR /&gt;&lt;BR /&gt;If I understand you correctly, then you mix several things. &lt;BR /&gt;&lt;BR /&gt;HBMM: I can not find out what is your question &lt;BR /&gt;&lt;BR /&gt;DOSD: Dump off system disk. I will try to give you an answer for Dosd.&lt;BR /&gt;&lt;BR /&gt;- To use DOSD (dump off system disk) you have to define the path to the dump disks in wwidmgr. &lt;BR /&gt;&lt;BR /&gt;- You then have to set the console variable DUMPDEV so, that the path to the dump disks is defined. Don't forgett to include the path to the systemdisk within dump_dev, it's required as far as I remember for dumping the errorlog buffers. &lt;BR /&gt;&lt;BR /&gt;- The dumpfile must reside in a similar directory structure like the systemdisk (dumpdisk:[sysX.sysexe]sysdump.dmp)&lt;BR /&gt;&lt;BR /&gt;- You must define the symbol DUMPFILE_DEVICE in Modparams.dat. (DUMPFILE_DEVICE = "$1$dga10")&lt;BR /&gt;&lt;BR /&gt;- The Sysgen Parameter Dumpstyle must be 4, 5, 12 or 13 (Bit 2 must be set)&lt;BR /&gt;&lt;BR /&gt;- take care to mount the Dumpdisk very early during startup (SYS$MANAGER:SYCONFIG.COM)&lt;BR /&gt;&lt;BR /&gt;- You must define a logical name CLUE$DOSD_DEVICE pointing to the Dumpdisk)&lt;BR /&gt;&lt;BR /&gt;- You can find further information to DOSD in this manual &lt;A href="http://h71000.www7.hp.com/doc/82FINAL/aa-pv5nj-tk/aa-pv5nj-tk.PDF" target="_blank"&gt;http://h71000.www7.hp.com/doc/82FINAL/aa-pv5nj-tk/aa-pv5nj-tk.PDF&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I hope that helps&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Heinz</description>
      <pubDate>Tue, 25 Jul 2006 06:56:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/host-based-mini-merge-on-openvms/m-p/3830047#M77852</guid>
      <dc:creator>Heinz W Genhart</dc:creator>
      <dc:date>2006-07-25T06:56:47Z</dc:date>
    </item>
    <item>
      <title>Re: Host-Based Mini-Merge on OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/host-based-mini-merge-on-openvms/m-p/3830048#M77853</link>
      <description>Hi Heinz!&lt;BR /&gt;&lt;BR /&gt;HBMM is Host-Based Mini-Merge.&lt;BR /&gt;&lt;BR /&gt;Your description of DOSD was pretty much known to me, but I like it so short and concise. &lt;BR /&gt;The problem is that only four EVA disks can be defined using wwidmgr, and I have defined four of them and don't want to delete any of them. So it seams that I have to use localy attached disk for DOSD. Am I right?&lt;BR /&gt;&lt;BR /&gt;Best regards&lt;BR /&gt;&lt;BR /&gt;Domen&lt;BR /&gt;Domen</description>
      <pubDate>Tue, 25 Jul 2006 07:05:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/host-based-mini-merge-on-openvms/m-p/3830048#M77853</guid>
      <dc:creator>Domen Setar</dc:creator>
      <dc:date>2006-07-25T07:05:36Z</dc:date>
    </item>
    <item>
      <title>Re: Host-Based Mini-Merge on OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/host-based-mini-merge-on-openvms/m-p/3830049#M77854</link>
      <description>HBMM requires at least two nodes to be effective. Assuming you wont to avoid long disk merges should a node crash, then the other cluster members can reconcile the bitmaps with its data.</description>
      <pubDate>Tue, 25 Jul 2006 07:45:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/host-based-mini-merge-on-openvms/m-p/3830049#M77854</guid>
      <dc:creator>Thomas Ritter</dc:creator>
      <dc:date>2006-07-25T07:45:31Z</dc:date>
    </item>
    <item>
      <title>Re: Host-Based Mini-Merge on OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/host-based-mini-merge-on-openvms/m-p/3830050#M77855</link>
      <description>Hi Domen&lt;BR /&gt;&lt;BR /&gt;I'm not sure from where the limitation comes, but I think it may be possible to define more than 4 path within the console variable bootdef_dev. &lt;BR /&gt;&lt;BR /&gt;If this is not possible, then I would define 4 path to the systemdisk in bootdef_dev. For dump_dev I would define 2 path to the systemdisk and two path to the dump disk.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Heinz&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 25 Jul 2006 07:57:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/host-based-mini-merge-on-openvms/m-p/3830050#M77855</guid>
      <dc:creator>Heinz W Genhart</dc:creator>
      <dc:date>2006-07-25T07:57:37Z</dc:date>
    </item>
  </channel>
</rss>

