|
The idea of a system file containing a list of all files and theirYou 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.
size sounds nice but the overhead of updating for every record added
or deleted would be tremendous.
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>> Thanks!
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?
--
____________________________________________________________________
__ 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.
As an Amazon Associate we earn from qualifying purchases.
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.