Re: finding large objects on Iseries -- MIDRANGE-L

Hi Matt

I had wondered about using Win Explorer or some other tool to help with this. I didn't mention it in any of my replies to the original post, however.

What does windirstat do with the library file system? The stuff under /QSYS.LIB?

Thanks
Vern

On 2/14/2013 10:42 AM, Matt Olson wrote:

I've used windirstat (http://windirstat.info/) with success by pointing it to the IFS root directory on the AS400 to do space/file analysis in the past. Perhaps that will help you?

-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxx]
Sent: Thursday, February 14, 2013 10:37 AM
To: Midrange Systems Technical Discussion
Subject: Re: finding large objects on Iseries

If the OP wanted to know only about files, the database cross-reference files might do the trick. SYSTABLES view did not seem to have sizes in it, however.

But the OP was asking about objects, all kinds, I assume.

One list of objects is the *LIB object - try DMPOBJ against a small library and take a look at the spooled file it creates. You'll see the contents of an index - entries have 2 byes that are the MI object type - x'1901' is a physical file, for example. Then the entry has the name of the object. Later on there is a space area with more details, the layout of which I don't know. I mean, we're not supposed to worry about that, right?

Maybe the library object HAS the size, and maybe that is where DSPOBJD goes - again, I don't know. But if you have a large system, you're still going to have a long time to process things.

For the task described here, I also think RTVDSKINF and PRTDSKINF are the best solution - they cover both IFS directories and libraries.

Cheers - and 4 more days!
Vern

On 2/14/2013 10:15 AM, Stone, Joel wrote:

The idea of a system file containing a list of all files and their
size sounds nice but the overhead of updating for every record added
or deleted would be tremendous.

You are kidding, right? IBM makes a good chunk of their revenue selling storage - and much of their sales are because client disk systems get clogged up with junk.

If they made it too easy, I am guessing their sales would take a hit. Not much incentive to help clients keep their disk storage clean.

It would be like trash companies lobbying to reduce product packaging waste - probably wont happen.

I am guessing that OS/400 probably knows its files and sizes to some extent - it is simply not available to us. Maybe Im wrong, don't know.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of franz400
Sent: Wednesday, February 13, 2013 8:08 PM
To: Midrange Systems Technical Discussion
Subject: Re: finding large objects on Iseries

The idea of a system file containing a list of all files and their
size sounds nice but the overhead of updating for every record added
or deleted would be tremendous.
I've always run the RTVDSKINF (and RTVDIRINF) once a week during
quieter times, and then can use PRTDSKINF and PRTDIRINF (or query the outfiles:
QUSRSYS/QAEZDISK and for RTVDIRINF, see the help text for how the file
is named .

And if just looking for a quick check of a library, WRKOBJPDM - F14 to
show object size, and F15 to selection
Subset Object List

Object . . . . . . . . . . . . *ALL *ALL, name, *generic*
Object type . . . . . . . . . *FILE *ALL, *type
Object attribute . . . . . . . *ALL *ALL, attribute,
*generic*,
*BLANK
Object size
From . . . . . . . . . . . . 0 0 - 9999999999
To . . . . . . . . . . . . . 9999999999 0 - 9999999999

Text . . . . . . . . . . . . . *ALL

Jim Franz

----- Original Message -----
From: "Vernon Hamberg" <vhamberg@xxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, February 13, 2013 4:06 PM
Subject: Re: finding large objects on Iseries

The only thing you have is DSPOBJD as you have it. Submit it to batch
and let it run.

You also need to look at the IFS.

There is another option - RTVDSKINF followed by PRTDSKINF. These are
also going to be long-running, but you get both library objects and
non-library stuff.

HTH
Vern

On 2/13/2013 2:52 PM, Stone, Joel wrote:

We want to reduce the % system ASP used as displayed by WRKSYSSTS.

One method is DSPOBJD OBJ(*ALLUSR/*ALL) OBJTYPE(*ALL) to an outfile.
But this takes a long time.

Is there a file on the iseries to query such that I can simply

SELECT * from systemfile where OBJSIZE > 1000000000

Ie is there a file on the iseries similar to QADBIFLD or QADBXREF
which contains libname, objname, and size of each object?

>> Thanks!

____________________________________________________________________
__ This outbound email has been scanned for all viruses by the
MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com
____________________________________________________________________
__

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

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