🚀 go-pugleaf

In <101579@bu.edu> TEWKSBURY@BUDSGA.BU.EDU writes:
> ...
>  A.  Disk Usage:   Let's assume that you want to charge in units of
>  blocks/day and that your charge period is one month. 
> 
>    In order to get disk usage, you need to generate an ANALYZE/DISK/USAGE
>    report for each day and each disk and then append these 30+ reports to
>    a single file for use by the ADVISE... command. 
> ...
>    I have a really rudimentary disk usage accounting program 
> ...(Too bad I can't tell it to use my routine!:-)
> .... 

      I *can* tell it to use my routine.  :-)  If anyone is interested in
      the  programs which I developed, I'll gladly send them to you as soon
      as I "clean" them a bit.  Here's a brief synopsis of what these
      programs do:

           1)  A diskquota macro-32 program:  This program is designed to run
           once per day (if that is the sample period of your charging base)
           on each of your disks on which you wish to account for disk
           usage.  This program creates an indexed file of UIC/total_quota
           records on each disk.

           2)  A USAGE.DAT builder program.  This program converts each of
           the files produced in "1)" into a USAGE.DAT format file.

      Then all you do is append the files produced by "2)" into a single
      file which can be supplied to ADVISE CHARG as the disk usage file.

      The total size of the generated files on a 2-volume volume set with
      approximately 625 uic/quota records is only 70 blocks for this monthly
      data -- compare that to approximately 520,000 blocks for the same
      information using DEC's method!

      			Chip Tewksbury.