× 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.



RTVDSKINF is a strategic tool - it is useful for reporting long-term usage patterns. It is not a short-term, tactical, emergency tool. So I can't resist a commercial:

<commercial>

Our disk/HUNTER product runs as a real-time, never-ending monitor of disk space. It detects spikes in usage in real-time (every 15 seconds). When a spike occurs, it does a number of things to identify likely suspects, including checking the IFS for growth, user profile allocation for growth, and what specific jobs and objects (including job that caused the growth in the object) have consumed the most disk space in, say, 5 minutes after the spike occurred. It integrates nicely with products like Messenger-Plus and ROBOT/Console. Info at <www.centerfieldtechnology.com>

</commercial>

At 12:03 PM 4/13/2004 -0500, you wrote:
We wrote a program to drill down the IFS and list the data to a file. Then
it automatically runs a report showing you what objects have grown between
two dates.  And if the total growth exceeds a set amount, or the growth of
any one directory exceeds another set amount, then an email is generated
to people who are supposed to care.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/09/2004 07:41 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>

To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RTVDSKINF - tons of fun

I just did a RTVDSKINF to see what's taking space on my system.  A
little SQL magic over the file QUSRSYS/QAEZDISK brought up two very
interesting but ultimately annoying issues.

Two of the major offenders are objects of type *STMF and *JVAPGM.
Unfortunately, QAEZDISK has very little information on these objects.
You get the first 12 characters of the name for JVAPGMs, and nothing at
all on STMFs.  While this is a nice report for the majority of QSYS
objects, I'd love to get some more information on those objects that
aren't being explicitly identified.

The JVAPGMs in particular are troublesome - some 3GB in JVAPGM objects,
and many of them look like duplicates, but with different dates.

Does anybody have any insight on this?

Joe



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.