<?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: DVE in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/dve/m-p/4428658#M94781</link>
    <description>Dave,&lt;BR /&gt;&lt;BR /&gt;even easier than that!&lt;BR /&gt;&lt;BR /&gt;Just SET VOLUME/SIZE  (without specifying value) will set the size equal to limit,  which I think will be more than sufficient for your current needs.&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
    <pubDate>Thu, 28 May 2009 14:32:33 GMT</pubDate>
    <dc:creator>Jan van den Ende</dc:creator>
    <dc:date>2009-05-28T14:32:33Z</dc:date>
    <item>
      <title>DVE</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dve/m-p/4428655#M94778</link>
      <description>Is there a simple, foolproof method of verifying that DVE is enabled (or not) on an existing mounted (/sys) volume??&lt;BR /&gt;&lt;BR /&gt;Dave</description>
      <pubDate>Thu, 28 May 2009 12:35:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dve/m-p/4428655#M94778</guid>
      <dc:creator>The Brit</dc:creator>
      <dc:date>2009-05-28T12:35:46Z</dc:date>
    </item>
    <item>
      <title>Re: DVE</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dve/m-p/4428656#M94779</link>
      <description>Hi Dave,&lt;BR /&gt;&lt;BR /&gt;Not foolproof, but does&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1243519968551+28353475&amp;amp;threadId=1046073" target="_blank"&gt;http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1243519968551+28353475&amp;amp;threadId=1046073&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;answer your question?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Kris (aka Qkcl)</description>
      <pubDate>Thu, 28 May 2009 13:15:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dve/m-p/4428656#M94779</guid>
      <dc:creator>Kris Clippeleyr</dc:creator>
      <dc:date>2009-05-28T13:15:07Z</dc:date>
    </item>
    <item>
      <title>Re: DVE</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dve/m-p/4428657#M94780</link>
      <description>Maybe.&lt;BR /&gt;&lt;BR /&gt;In my case, &lt;BR /&gt;&lt;BR /&gt;Expansion Size Limit    87011328&lt;BR /&gt;Total blocks            75497472&lt;BR /&gt;Logical Volume Size     75497472&lt;BR /&gt;&lt;BR /&gt;I dont know if the /Limit qualifier has ever been applied to this volume&lt;BR /&gt;&lt;BR /&gt;I need to increase the size by only a few hundred blocks, to&lt;BR /&gt;&lt;BR /&gt;75498000&lt;BR /&gt;&lt;BR /&gt;(original disk was from EVA, new disk is from XP)&lt;BR /&gt;&lt;BR /&gt;My question is, given the current values, could I &lt;BR /&gt;&lt;BR /&gt;1.   Shadow the new unit (of course)&lt;BR /&gt;2.   remove the old unt (of course)&lt;BR /&gt;&lt;BR /&gt;3.   Use "set volume/size" to make the LBN count = 75498000&lt;BR /&gt;&lt;BR /&gt;Dave.</description>
      <pubDate>Thu, 28 May 2009 13:26:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dve/m-p/4428657#M94780</guid>
      <dc:creator>The Brit</dc:creator>
      <dc:date>2009-05-28T13:26:22Z</dc:date>
    </item>
    <item>
      <title>Re: DVE</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dve/m-p/4428658#M94781</link>
      <description>Dave,&lt;BR /&gt;&lt;BR /&gt;even easier than that!&lt;BR /&gt;&lt;BR /&gt;Just SET VOLUME/SIZE  (without specifying value) will set the size equal to limit,  which I think will be more than sufficient for your current needs.&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Thu, 28 May 2009 14:32:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dve/m-p/4428658#M94781</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2009-05-28T14:32:33Z</dc:date>
    </item>
    <item>
      <title>Re: DVE</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dve/m-p/4428659#M94782</link>
      <description>Dave,&lt;BR /&gt;&lt;BR /&gt;The OpenVMS SET VOLUME command affects the file structure data, not the underlying volume maintained by the storage array.&lt;BR /&gt;&lt;BR /&gt;If the storage array is already presenting the larger volume, then shadowing need not be used to migrate the volume.&lt;BR /&gt;&lt;BR /&gt;The use of host-based volume shadowing to migrate volumes reflected the need to move the data to different storage arrays, or different containers on the same storage array. That presentation, "Migrating OpenVMS Storage Environments without Interruption or Disruption", is available at &lt;A href="http://www.rlgsc.com/hptechnologyforum/2007/1512.html" target="_blank"&gt;http://www.rlgsc.com/hptechnologyforum/2007/1512.html&lt;/A&gt;&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>Thu, 28 May 2009 14:43:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dve/m-p/4428659#M94782</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2009-05-28T14:43:11Z</dc:date>
    </item>
  </channel>
</rss>

