<?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: Setting DVE on OpenVMS 7.3-2 system disk in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/setting-dve-on-openvms-7-3-2-system-disk/m-p/4984889#M76884</link>
    <description>Jim,&lt;BR /&gt;&lt;BR /&gt;there is a bug in V7.3-2 regarding setting the volume extension limit when booted from the operating system CD.&lt;BR /&gt;&lt;BR /&gt;Use the OpenVMS Alpha V8.2 operating system CD to boot from. That one will work.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
    <pubDate>Tue, 13 Jun 2006 01:55:12 GMT</pubDate>
    <dc:creator>Volker Halle</dc:creator>
    <dc:date>2006-06-13T01:55:12Z</dc:date>
    <item>
      <title>Setting DVE on OpenVMS 7.3-2 system disk</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/setting-dve-on-openvms-7-3-2-system-disk/m-p/4984887#M76882</link>
      <description>When deploying DVE (dynamic volume expansion) what is recommended to convert the system disk or shadow set to DVE? I booted a system running OpenVMS Alpha 7.3-2 from the OpenVMS 7.3-2 CD, mounted the system disk /nosystem and then issued the command SET VOLUME/LIMIT. I got the following errors:&lt;BR /&gt;&lt;BR /&gt;$$$ mount/over=shadow $1$dga1 openvms732&lt;BR /&gt;%MOUNT-I-MOUNTED, OPENVMS732 mounted on _$1$DGA1: ()&lt;BR /&gt;%MOUNT-I-REBUILD, volume was improperly dismounted; rebuild in progress&lt;BR /&gt;&lt;BR /&gt;$$$ set volume/limit $1$dga1:&lt;BR /&gt;%SET-E-NOTSET, error modifying _$1$DGA1:&lt;BR /&gt;-SYSTEM-W-DEVNOTALLOC, device not allocated&lt;BR /&gt; &lt;BR /&gt;$$$ dismount $1$dga1:&lt;BR /&gt;$$$ mount/nosystem $1$dga1: openvms732&lt;BR /&gt;%MOUNT-I-MOUNTED, OPENVMS732 mounted on _$1$DGA1: ()&lt;BR /&gt;$$$ set volume/limit $1$dga1:&lt;BR /&gt;%SET-E-NOTSET, error modifying _$1$DGA1:&lt;BR /&gt;-SYSTEM-W-DEVNOTALLOC, device not allocated&lt;BR /&gt;&lt;BR /&gt;How do I set DVE on our system disk?</description>
      <pubDate>Mon, 12 Jun 2006 17:19:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/setting-dve-on-openvms-7-3-2-system-disk/m-p/4984887#M76882</guid>
      <dc:creator>Jim Geier_1</dc:creator>
      <dc:date>2006-06-12T17:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Setting DVE on OpenVMS 7.3-2 system disk</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/setting-dve-on-openvms-7-3-2-system-disk/m-p/4984888#M76883</link>
      <description>Jim,&lt;BR /&gt;&lt;BR /&gt;On a normal disk, all you need is to MOUNT it privately (a quick check with a LDDRIVER will allow you to confirm this for yourself).&lt;BR /&gt;&lt;BR /&gt;I have not tried setting a system residence volume to extend (and I am not in my office at this instant, so it is difficult to recover from a failed test).&lt;BR /&gt;&lt;BR /&gt;As a start, set the dynamic extend flag on a non-system volume. I do not have the time to check the docset at this instant, but a requirement for at least instantaneous exclusivity would be unsurprising.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Mon, 12 Jun 2006 18:22:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/setting-dve-on-openvms-7-3-2-system-disk/m-p/4984888#M76883</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2006-06-12T18:22:39Z</dc:date>
    </item>
    <item>
      <title>Re: Setting DVE on OpenVMS 7.3-2 system disk</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/setting-dve-on-openvms-7-3-2-system-disk/m-p/4984889#M76884</link>
      <description>Jim,&lt;BR /&gt;&lt;BR /&gt;there is a bug in V7.3-2 regarding setting the volume extension limit when booted from the operating system CD.&lt;BR /&gt;&lt;BR /&gt;Use the OpenVMS Alpha V8.2 operating system CD to boot from. That one will work.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Tue, 13 Jun 2006 01:55:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/setting-dve-on-openvms-7-3-2-system-disk/m-p/4984889#M76884</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2006-06-13T01:55:12Z</dc:date>
    </item>
    <item>
      <title>Re: Setting DVE on OpenVMS 7.3-2 system disk</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/setting-dve-on-openvms-7-3-2-system-disk/m-p/4984890#M76885</link>
      <description>IIRC The bug is to do with which process owns the disk when it is privately mounted and the check that SET VOLUME makes. It was fixed in a patch. If you are current on patches and if you make a minimal VMS system on another disk then booting from that minimal system may work.&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Jun 2006 03:33:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/setting-dve-on-openvms-7-3-2-system-disk/m-p/4984890#M76885</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2006-06-13T03:33:52Z</dc:date>
    </item>
    <item>
      <title>Re: Setting DVE on OpenVMS 7.3-2 system disk</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/setting-dve-on-openvms-7-3-2-system-disk/m-p/4984891#M76886</link>
      <description>Will boot from the OpenVMS 8.2 CD to set the DVE on the system disk.</description>
      <pubDate>Tue, 13 Jun 2006 10:04:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/setting-dve-on-openvms-7-3-2-system-disk/m-p/4984891#M76886</guid>
      <dc:creator>Jim Geier_1</dc:creator>
      <dc:date>2006-06-13T10:04:06Z</dc:date>
    </item>
  </channel>
</rss>

