|
What about QFOLDER or other PC folder type objects? Would those appear? Are you running this command from a user ID with ALLOBJ authority? Perhaps it can't see everything. Did you try running just a summary query over your raw data file? Add that up and see what comes out. One thing you won't see is QTEMP (or rather, all the QTEMPs floating around your system), since that 'library' would be visible only to the individual job running. Your QTEMP is different than your batch job's QTEMP, and different from your neighbor's QTEMP. Is there a lot of stuff running on the AS/400 at the time? Perhaps many QTEMPs are swimming around, full of stuff. One last thing - locked objects may not report their full DSPOBJD information. Neither will locked file members. So, if lots of things are running with locked files and locked members, perhaps you're missing those items. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Purge and Archive your AS/400 Data Without Programming with ARCTOOLS (tm) DCSoftware, Inc. (508) 435-8243 (508) 435-4498 (fax) http://www.arctools.com mailto:info@arctools.com +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: oludare <oludare@ix.netcom.com> To: RPG AS/400 UserGroup <RPG400-L@midrange.com>; AS/400 Midrange Usergroup <MIDRANGE-L@midrange.com> Cc: Thomas, Michael <buttah@mindspring.com>; Mike Thomas <mthomas@bofasecurities.com> Date: Wednesday, September 01, 1999 3:12 PM Subject: DASD USAGE UTILITY >Guys: > >I have created a DASD daily usage utility using DSPOBJD, CLP,QRY and embeded >SQL. This utility works fine for information display, reporting and for all >object types analysis. > >These are my observations: >1. Empty libraries are not returned by DSPOBJD (see detail command >below), not a big deal. >2. Using WRKSYSSTS, my DASD size is 41.94Gig, %used is 92.3845, my >utility > reports about 76% used (30.89Gig), this is a big deal. >3. What happened to 16% of DASD, where in the system can I find this used >storage or > is there a good explanation for the hidden space. > >This command was ran once for control data and could be run again to change >control data >============================================================= >DSPOBJD OBJ(*ALL/*ALL) OBJTYPE(*ALL) + > DETAIL(*BASIC) OUTPUT(*OUTFILE) + > OUTFILE(PULSEOBJS) > >This command is run every night to compare with control data and to show >usage >====================================================== >DSPOBJD OBJ(*ALL/*ALL) OBJTYPE(*ALL) + > DETAIL(*BASIC) OUTPUT(*OUTFILE) + > OUTFILE(PULSEOBJSZ) > >+--- >| This is the RPG/400 Mailing List! >| To submit a new message, send your mail to RPG400-L@midrange.com. >| To subscribe to this list send email to RPG400-L-SUB@midrange.com. >| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: david@midrange.com >+--- > +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.