|
Hello All, Thanks for all the replies. It's my customer box, with 500GB. It was 90% 2 days ago. They have loaded in DataPropagator (5722DP4) yesterday and they space utilization suddenly shot up to 99%. That is like 50GB increased in a day! They are totally clueless what had gone wrong. It's night time over here in ASIA, and i shall be going onsite tomorrow to further check if they have journalling turn on and etc. By deleting historical files and applying ptf perm. would help to an extent which i would be able to turn on diskinfo. Really appreciate everybody's input here. I shall keep you guys updated on my findings. regards, Daniel On 8/3/06, Vernon Hamberg <vhamberg@xxxxxxxxxxx> wrote:
Daniel You might look for some usual suspects. You might not have the space to do a DSPOBJD *ALL/*ALL *ALL OUTPUT(*OUTFILE) which is useful for determining the large items - similar to disk information. 1. If you have a command line, see if you have a lot of files starting with QHST* WRKF QHST* You can probably delete old ones - the bit after QHST is the Julian date plus a sequence character. 2. Then there might be journal receivers - especially related to the audit journal. Try DSPOBJD *ALL/*ALL *JRNRCV to an outfile if you can, or to the screen. 3. WRKOBJPDM QRPLOBJ and clear it out 4. IFS objects - you can execute EDTF '/' - then put a 6 on the directories whose size you want to know about - I suggest you do NOT do this with QIBM or QSYS.LIB!! Once you get some room, you might consider getting the disk/HUNTER product from Centerfield Technologies (www.centerfieldtechnology.com) that would have warned you far ahead of this situation. I used to work there, so this is not a vendor response. HTH Vern At 05:09 AM 8/3/2006, you wrote: >Hello All, > >Out of nowhere, my disk utilization is 99% (total 500gb). I can go >disktasks, but i doubt the job will ever finish. The system is >development, hence i can re-ipl anything. > >Please advise what i can do, or is there any ways to locate those big >files via search command? > >Regards, >Daniel >-- >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.
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.