Do the RTVDSKINF/PRTDSKINF.  Maybe create an outfile with a timestamp to
hold the *SYS information from PRTDSKINF.  Then you can plot trends.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    "rich herdman"
                    <rherdman@columbus.       To:     "midrange-l@midrange.com" 
<midrange-l@midrange.com>
                    rr.com>                   cc:
                    Sent by:                  Fax to:
                    midrange-l-admin@mi       Subject:     (changed) DASD usage 
of IFS objects
                    drange.com


                    01/04/2002 10:34 AM
                    Please respond to
                    midrange-l






So, objects in the IFS use more DASD that you would expect?  Interesting...

Maybe that would explain our problem - our DASD usage is growing at
(almost) alarming rate since we went to V5R1, and we have been running
daily
DSPLIB's to find the culprit(s).  We have been unable to find any libraries
that
are growing that fast, but we do have a bunch of stuff (spread evenly
between
lots of little files and a few large files) we put into the IFS on a daily
basis.

What would be the best way to find out how much DASD is being used by
the IFS?  Would running a RTKDSKINF and then a PRTDSKINF be the best way?
Or is there a faster way to get this?

Thanks.


Rich Herdman
Abbott Foods
Columbus, OH

On Fri, 4 Jan 2002 10:09:17 -0500, barsa@barsaconsulting.com wrote:

>
>QDOC = Slow
>IFS = Fast
>
>Agreed, however, IFS uses lots of disk space.  Some time ago, I noticed
>that the IFS was consuming lots of tapes, and I did some investigation.  I
>determined that typical objects in the IFS (relatively small) use on
>average about 2 and a half times the amount of disk space that they
report.
>
>When I inquired about this to Rochester, literally every developer that I
>spoke to started to respond with the same phrase.  "Well, it's a tender
>balance..."
>
>Al
>
>Al Barsa, Jr.
>Barsa Consulting Group, LLC
>







_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.