× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 13 February 2013 21:18, Monnier, Gary <Gary.Monnier@xxxxxxxxx> wrote:
Joel,

Rather than going directly at large objects you can first go through and check library size.

Basically you use DSPOBJD to list libraries to an output file then use the QLIRLIBD to list the libraries and their sizes.

You can then focus on the largest sized libraries to find excessively sized objects.

Also check the IFS. You may have files building there also.

HTH.

Gary

And that's just the route we took with trying to identify what was
pushing up disk use.
http://www.dbg400.net/foswiki/bin/view/DBG400/BldLibInfo is the code I
put together for it.

The IFS was more tricky and I settled for a RTVDSKINF for specific
portions of the IFS, as we only allow users and processes to use one
folder off the root. So far it's always been runaway ODBC jobs that
have caused issues, so the temp storage checker has kept things
running smoothly.

Regards, Martin

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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.