<?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: Erase-on-delete -- how to determine via $getdvi in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886445#M68637</link>
    <description>Requested f$getdvi code included in OpenVMS Alpha V8.2.</description>
    <pubDate>Tue, 31 May 2005 15:42:10 GMT</pubDate>
    <dc:creator>Jim Geier_1</dc:creator>
    <dc:date>2005-05-31T15:42:10Z</dc:date>
    <item>
      <title>Erase-on-delete -- how to determine via $getdvi</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886437#M68629</link>
      <description>One of the side-effects of using the recommended /erase qualifier to prepare disks for a shadow set is that the volume characteristic erase_on_delete is set. This is easily turned off  using SET VOLUME/NOERASE, but I was wondering how to determine whether the erase_on_delete characteristic is set for a volume. So I experimented using f$getdvi and found no change in the DEVCHAR, DEVCHAR2, DEVDEPEND, and DEVSTS bitmaps before and after setting /erase on the volume.&lt;BR /&gt;&lt;BR /&gt;How does one determine whether erase_on_delete is set for a volume? Am I missing or overlooking something obvious?</description>
      <pubDate>Thu, 17 Feb 2005 12:16:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886437#M68629</guid>
      <dc:creator>Jim Geier_1</dc:creator>
      <dc:date>2005-02-17T12:16:43Z</dc:date>
    </item>
    <item>
      <title>Re: Erase-on-delete -- how to determine via $getdvi</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886438#M68630</link>
      <description>Stupid question, but why bother and not blindly do the:&lt;BR /&gt;$ SET VOLUME/NOERASE</description>
      <pubDate>Thu, 17 Feb 2005 12:21:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886438#M68630</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-02-17T12:21:26Z</dc:date>
    </item>
    <item>
      <title>Re: Erase-on-delete -- how to determine via $getdvi</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886439#M68631</link>
      <description>Not a stupid question, and one could certainly issue SET VOLUME/NOERASE for all disks on a system -- that would be very practical and perhaps even efficient.&lt;BR /&gt;&lt;BR /&gt;It would be interesting to know how to determine the state of the erase_on_delete characteristic for a given volume. SHOW DEVICE certainly knows how, and DELETE knows how, and I'd like to know how.</description>
      <pubDate>Thu, 17 Feb 2005 12:27:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886439#M68631</guid>
      <dc:creator>Jim Geier_1</dc:creator>
      <dc:date>2005-02-17T12:27:11Z</dc:date>
    </item>
    <item>
      <title>Re: Erase-on-delete -- how to determine via $getdvi</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886440#M68632</link>
      <description>Its in the volume control block&lt;BR /&gt;VCB$B_STATUS2 &lt;BR /&gt;bit 3 set means erase on delete.&lt;BR /&gt;&lt;BR /&gt;The VCB address is in the UCB at UCB$L_VCB&lt;BR /&gt;&lt;BR /&gt;In SDA&lt;BR /&gt;sda&amp;gt; READ SYS$LOADABLE_IMAGES:SYSDEF&lt;BR /&gt;sda&amp;gt; SHOW DEV DKxxx&lt;BR /&gt;sda&amp;gt; EXAM VCB+VCB$B_STATUS2</description>
      <pubDate>Thu, 17 Feb 2005 12:49:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886440#M68632</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-02-17T12:49:15Z</dc:date>
    </item>
    <item>
      <title>Re: Erase-on-delete -- how to determine via $getdvi</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886441#M68633</link>
      <description>Jim,&lt;BR /&gt;&lt;BR /&gt;the ERASE-bit is not a DEVICE characteristics, but a VOLUME characteristic.&lt;BR /&gt;&lt;BR /&gt;The VCB$V_ERASE bit is stored in the VCB (Volume Control Block). Visible with SDA&amp;gt;SHOW DEVIVE Dxxx&lt;BR /&gt;...&lt;BR /&gt;                --- Volume Control Block (VCB) 82773B80 ---&lt;BR /&gt;&lt;BR /&gt;Volume: TOOLS            Lock name: TOOLS&lt;BR /&gt;Status:  A0 extfid,system&lt;BR /&gt;Status2: 1C mountver,erase,nohighwater&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;There does not seem to exist a F$GETDVI lexical function argument to obtain this characteristic of a volume (even V7.3-2 VOLCHAR does not do it).&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Thu, 17 Feb 2005 13:04:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886441#M68633</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-02-17T13:04:18Z</dc:date>
    </item>
    <item>
      <title>Re: Erase-on-delete -- how to determine via $getdvi</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886442#M68634</link>
      <description>And. Jim,&lt;BR /&gt;&lt;BR /&gt;if you really want it in DCL without running SDA, capturing the output, and parsing it, then there are some crazy tricks that can be done.&lt;BR /&gt;&lt;BR /&gt;Look at &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=746158" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=746158&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;and find the explanations by John Gillings.&lt;BR /&gt;&lt;BR /&gt;If you understand enough of that to be able to use that as a blueprint, together with Ian's answer, then go ahead.&lt;BR /&gt;&lt;BR /&gt;If it is not sufficiently clear what he is doing, and why, then you are probably wiser by not using it, but even then it is very instructive of some of the workings.&lt;BR /&gt;&lt;BR /&gt;Have fun, and if you DO venture, please inform us of your results!&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;Jan</description>
      <pubDate>Thu, 17 Feb 2005 14:19:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886442#M68634</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-02-17T14:19:26Z</dc:date>
    </item>
    <item>
      <title>Re: Erase-on-delete -- how to determine via $getdvi</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886443#M68635</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Over 20 new $GETDVI item codes have been added for V8.2 (both Alpha and I64).  Please see the System Services reference manual for more details.  &lt;BR /&gt;&lt;BR /&gt;For your coding pleasure, among the new item codes added is dvi$_erase_on_delete.&lt;BR /&gt;&lt;BR /&gt;                   --Rob&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 20 Feb 2005 19:46:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886443#M68635</guid>
      <dc:creator>Robert Brooks_1</dc:creator>
      <dc:date>2005-02-20T19:46:27Z</dc:date>
    </item>
    <item>
      <title>Re: Erase-on-delete -- how to determine via $getdvi</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886444#M68636</link>
      <description>Starting with V8.2, OpenVMS Engineering eliminated the ambiguity of the INITIALIZE command with the /ERASE qualifier both erasing the volume *and* setting the erase-on-delete volume characteristic by enhancing the /ERASE qualifier for the INITIALIZE command to take a value, one of either /ERASE=INIT or /ERASE=DELETE. Omitting the value replicates the pre-V8.2 behaviour, causing the erasure of the volume and the setting of the erase-on-delete characteristic.&lt;BR /&gt;&lt;BR /&gt;Additionally, the lexical function F$GETDVI has a new argument, ERASE_ON_DELETE, returning True or False to indicate whether the eraee-on-delete volume characteristic hsa been set.&lt;BR /&gt;&lt;BR /&gt;Good things come to those who wait...thanks!</description>
      <pubDate>Tue, 31 May 2005 15:41:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886444#M68636</guid>
      <dc:creator>Jim Geier_1</dc:creator>
      <dc:date>2005-05-31T15:41:02Z</dc:date>
    </item>
    <item>
      <title>Re: Erase-on-delete -- how to determine via $getdvi</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886445#M68637</link>
      <description>Requested f$getdvi code included in OpenVMS Alpha V8.2.</description>
      <pubDate>Tue, 31 May 2005 15:42:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/erase-on-delete-how-to-determine-via-getdvi/m-p/4886445#M68637</guid>
      <dc:creator>Jim Geier_1</dc:creator>
      <dc:date>2005-05-31T15:42:10Z</dc:date>
    </item>
  </channel>
</rss>

