<?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: Disk space allocation in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852188#M69627</link>
    <description>I guess a unix style answer is &lt;BR /&gt;pipe show dev/mount/fu | sear sys$input "Total blocks","Free blocks","Disk"&lt;BR /&gt;&lt;BR /&gt;(or I guess this could be done in perl with the VMS::getdvi module)&lt;BR /&gt;but you don't want to do that do you :-)&lt;BR /&gt;&lt;BR /&gt;Write some DCL using F$GETDVI - its fun and educational!&lt;BR /&gt;&lt;BR /&gt;See &lt;A href="http://dcl.openvms.org" target="_blank"&gt;http://dcl.openvms.org&lt;/A&gt; for examples.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 23 Jan 2004 11:13:56 GMT</pubDate>
    <dc:creator>Ian Miller.</dc:creator>
    <dc:date>2004-01-23T11:13:56Z</dc:date>
    <item>
      <title>Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852181#M69620</link>
      <description>I am working on some scripts to report on disk allocations and usage.&lt;BR /&gt;The show dev d /mount command gives me the currently free count and the output is great to work with, i.e. line by line space separated.  The one additional item I need is total allocated to that disk / file system.  I would love something that looked like a bdf or df -k output.&lt;BR /&gt;I apologize if I have missed the easy answer in the doc or help.&lt;BR /&gt;Thanks in advance.</description>
      <pubDate>Fri, 23 Jan 2004 10:14:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852181#M69620</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2004-01-23T10:14:20Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852182#M69621</link>
      <description>see F$GETDVI("devicename","FREEBLOCKS")&lt;BR /&gt;and F$GETDVI("devicename","MAXBLOCKS")&lt;BR /&gt;&lt;BR /&gt;for example of use see&lt;BR /&gt;&lt;A href="http://dcl.openvms.org/stories.php?story=04/01/11/4165701" target="_blank"&gt;http://dcl.openvms.org/stories.php?story=04/01/11/4165701&lt;/A&gt;</description>
      <pubDate>Fri, 23 Jan 2004 10:20:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852182#M69621</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-01-23T10:20:22Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852183#M69622</link>
      <description>THanks again Ian for the quick answer.  I have not quite got a handle on some of the tricks with the functions.&lt;BR /&gt;&lt;BR /&gt;If I could give you 100 pts I would.  &lt;BR /&gt;&lt;BR /&gt;Thanks !!!!  Have a great weekend.</description>
      <pubDate>Fri, 23 Jan 2004 10:22:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852183#M69622</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2004-01-23T10:22:35Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852184#M69623</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;See the online help for lexical f$getdvi . You can extract many more information about the disk.&lt;BR /&gt;&lt;BR /&gt;$help lexical f$getdvi&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Best regards,&lt;BR /&gt;Lokesh Jain</description>
      <pubDate>Fri, 23 Jan 2004 10:24:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852184#M69623</guid>
      <dc:creator>Lokesh_2</dc:creator>
      <dc:date>2004-01-23T10:24:44Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852185#M69624</link>
      <description>Thanks Lokesh..&lt;BR /&gt;&lt;BR /&gt;As you can tell I am an HPUX guy but not yet a VMS guy.&lt;BR /&gt;&lt;BR /&gt;Thanks for the direction.</description>
      <pubDate>Fri, 23 Jan 2004 10:30:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852185#M69624</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2004-01-23T10:30:29Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852186#M69625</link>
      <description>&lt;BR /&gt;&lt;BR /&gt;Using the lexical f$getdvi in a DCL script is definetly the VMS style / native solution.&lt;BR /&gt;Btw... be sure to check out lexical f$device to get you a list of intereting (mounted!) deviced to loop through.&lt;BR /&gt;&lt;BR /&gt;If you want to solve the problem more in a unix style then just use SHOW DEV/FULL/MOUN&lt;BR /&gt;and parse for "Total blocks 999999"&lt;BR /&gt;and "Free blocks 99999".&lt;BR /&gt;&lt;BR /&gt;btw... I suspect that the 'real problem' you are trying to solve has been solved many times before, both in freeware and commercial packages. Still... this could be a fun excersize to get into VMS!&lt;BR /&gt;&lt;BR /&gt;Enjoy,&lt;BR /&gt;Hein.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 23 Jan 2004 11:08:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852186#M69625</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2004-01-23T11:08:29Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852187#M69626</link>
      <description>Thanks Hein,  You hit it on the head.  Cannot learn for myself if I use someone elses utility.&lt;BR /&gt;&lt;BR /&gt;Thanks for the tips!!!</description>
      <pubDate>Fri, 23 Jan 2004 11:10:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852187#M69626</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2004-01-23T11:10:13Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852188#M69627</link>
      <description>I guess a unix style answer is &lt;BR /&gt;pipe show dev/mount/fu | sear sys$input "Total blocks","Free blocks","Disk"&lt;BR /&gt;&lt;BR /&gt;(or I guess this could be done in perl with the VMS::getdvi module)&lt;BR /&gt;but you don't want to do that do you :-)&lt;BR /&gt;&lt;BR /&gt;Write some DCL using F$GETDVI - its fun and educational!&lt;BR /&gt;&lt;BR /&gt;See &lt;A href="http://dcl.openvms.org" target="_blank"&gt;http://dcl.openvms.org&lt;/A&gt; for examples.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 23 Jan 2004 11:13:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852188#M69627</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-01-23T11:13:56Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852189#M69628</link>
      <description>Actually Ian.  This is what I am working on.&lt;BR /&gt;Instead of stuggling the ins and outs with DCL scripting I am going to run some remote shells from a UNIX system to VMS so I can take the output and send it through awk so I can get some quick reporting done.&lt;BR /&gt;Someother day will be spent learning DCL.&lt;BR /&gt;&lt;BR /&gt;Thanks !</description>
      <pubDate>Fri, 23 Jan 2004 11:34:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852189#M69628</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2004-01-23T11:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852190#M69629</link>
      <description>awk is available for VMS&lt;BR /&gt;&lt;A href="http://vms.process.com/scripts/fileserv/fileserv_search.exe?package=GAWK&amp;amp;description=&amp;amp;author=&amp;amp;system=Either&amp;amp;language=All&amp;amp;RD=&amp;amp;RM=&amp;amp;RY=" target="_blank"&gt;http://vms.process.com/scripts/fileserv/fileserv_search.exe?package=GAWK&amp;amp;description=&amp;amp;author=&amp;amp;system=Either&amp;amp;language=All&amp;amp;RD=&amp;amp;RM=&amp;amp;RY=&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;or, as I said you can do it in perl using the VMS::getdvi module</description>
      <pubDate>Fri, 23 Jan 2004 11:48:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852190#M69629</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-01-23T11:48:05Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852191#M69630</link>
      <description>Even better.. See I am learning loads by the minute.&lt;BR /&gt;&lt;BR /&gt;Thanks !!&lt;BR /&gt;</description>
      <pubDate>Fri, 23 Jan 2004 11:49:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852191#M69630</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2004-01-23T11:49:16Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852192#M69631</link>
      <description>and a pre-built perl can be obtained from&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/freeware/freeware60/perl-5_8_1/" target="_blank"&gt;http://h71000.www7.hp.com/freeware/freeware60/perl-5_8_1/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Use the VMS::Device module (included in above)&lt;BR /&gt;</description>
      <pubDate>Fri, 23 Jan 2004 12:04:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852192#M69631</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-01-23T12:04:58Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852193#M69632</link>
      <description>Gawk comes with Vms (or more precisely with Tcpip 5.any)&lt;BR /&gt;&lt;BR /&gt;$ gawk :== $ sys$common:&lt;SYSHLP.EXAMPLES.TCPIP.SNMP&gt;gawk.exe_alpha&lt;BR /&gt;&lt;BR /&gt;It is a strange idea to put it in the Snmp examples directory, but it is available.&lt;/SYSHLP.EXAMPLES.TCPIP.SNMP&gt;</description>
      <pubDate>Fri, 23 Jan 2004 12:39:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852193#M69632</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2004-01-23T12:39:51Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852194#M69633</link>
      <description>Instead of perl, you can use python which has other qualities (readability, easy to maintain...)&lt;BR /&gt;&lt;BR /&gt;python for Vms is available at &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://vmspython.dyndns.org/" target="_blank"&gt;http://vmspython.dyndns.org/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;see too&lt;BR /&gt; &lt;A href="http://www.ferg.org/python_presentations/python_intro_for_managers.ppt" target="_blank"&gt;http://www.ferg.org/python_presentations/python_intro_for_managers.ppt&lt;/A&gt;&lt;BR /&gt;&amp;gt; &lt;A href="http://www.ferg.org/python_slides/index.html" target="_blank"&gt;http://www.ferg.org/python_slides/index.html&lt;/A&gt;</description>
      <pubDate>Fri, 23 Jan 2004 12:51:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852194#M69633</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2004-01-23T12:51:52Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852195#M69634</link>
      <description>I have posted 2 procedures at DCL.OPENVMS:&lt;BR /&gt;&lt;BR /&gt;SPACE.COM is activated at a terminal(-session). It presents an overview of disk usage 1 line per disk.&lt;BR /&gt;&lt;BR /&gt;MONITOR_DEVICES.COM can also be run at a terminal session, but it is INTENDED to be ran in a MOTIF display window. It presents disk usage as a percentage bar, but also checks clusterwide mount statusses &amp;amp; shadow statusses. Non-nominal situations are highlighted.&lt;BR /&gt;It also gives management a nice 'moving picture', so they can show 'everything is permanently under control' (which it actually DOES help with!).&lt;BR /&gt;&lt;BR /&gt;Try if you like it, and DO let me know if you run into a configuration that is NOT covered.&lt;BR /&gt;&lt;BR /&gt;Enjoy.&lt;BR /&gt;&lt;BR /&gt;Jan&lt;BR /&gt;</description>
      <pubDate>Tue, 27 Jan 2004 10:04:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852195#M69634</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2004-01-27T10:04:18Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852196#M69635</link>
      <description>Except monitoring free space, you should also check contiguous disk space. Programs may fail if space is too fragmented.&lt;BR /&gt;&lt;BR /&gt;I don't know a method for retrieving this info in DCL so I try to create a contiguous file of 10.000 blocks every 30 minutes on almost every disk. If that fails : alarm.</description>
      <pubDate>Tue, 27 Jan 2004 11:30:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852196#M69635</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-01-27T11:30:14Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852197#M69636</link>
      <description>Freewware product svailable on CD (5.0, perhaps 6.0 as well) doing this is FREE. One line per disk.&lt;BR /&gt;Possibly, DFU (freeware as well) may show the same issues (and defragments as well).&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Jan 2004 02:21:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852197#M69636</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2004-01-28T02:21:12Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852198#M69637</link>
      <description>Thanks for the tip Willem. It is only sad to hear that DCL can not do the job.</description>
      <pubDate>Wed, 28 Jan 2004 04:05:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852198#M69637</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-01-28T04:05:50Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852199#M69638</link>
      <description>Actually... specifically in a cluster, creating a large contiguous file as a test is probably the best method. (COPY/ALLOC=10000/CONT NL: dev:[000000]contig.tmp)&lt;BR /&gt;&lt;BR /&gt;Cluster members have freeblock caches and the xqp will tell the other nodes to give back the free block cache before failing a request. [hmmm... not 100% sure it does this for lack of contig space]&lt;BR /&gt;&lt;BR /&gt;Also... conceivably, if you fail to allocate the big file, then maybe you could release one of a few 'spare' contig space you pre-allocated and really soudn the alarm if you find your spares already released? ( $DELE dev:[000000]contig.tmp. )&lt;BR /&gt;&lt;BR /&gt;groetjes,&lt;BR /&gt;Hein.&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Jan 2004 10:39:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852199#M69638</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2004-01-28T10:39:06Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space allocation</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852200#M69639</link>
      <description>Tim - Try looking in my directory for the file:&lt;BR /&gt;DISK_CAPACITY.COM&lt;BR /&gt;It produces a formatted report in GB.  I have other variants if you really want it in blocks...&lt;BR /&gt;&lt;BR /&gt;It also handles volume sets correctly.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Tom</description>
      <pubDate>Fri, 06 Feb 2004 20:56:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/disk-space-allocation/m-p/4852200#M69639</guid>
      <dc:creator>Thomas Simpson</dc:creator>
      <dc:date>2004-02-06T20:56:59Z</dc:date>
    </item>
  </channel>
</rss>

