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



I been too busy to check threads here for a few days ... so my ideas may be too late to be helpful.

I check disk space regularly using DSPSYSSTS
there are other commands with similar info

My understanding is that if you get above 80% disk space consumption you got problems, while above 90% it is time to shut down the system until more hard drive can be added, because for the system to work right, it needs some work space.

If you check disk utilization from time to time, and it has been healthy, then suddenly crazy, I would suspect
* a runaway job that is creating infinitely large spool file entries
* a runaway job that is creating infinitely large physical file.

Typically for me, a runaway job is something that got into some kind of loop, so if I am able to get at spool and see which one is absurd size. I would expect that on a development box, you may be at greater risk of some software having a bug that causes an infinite loop.

Sometimes when doing a conversion, or adding new products, we can miscalculate what some application will need, disk space wise. It may be smart to uninstall the last thing that got added.

An IPL can stop the runaway job, and recover perhaps 1-2% of disk space, but it cannot erase whatever garbage was created that ate all the disk space.

DSPJOBTBL will tell you how much disk space is being eaten to keep track of jobs that generated reports that are on spool ... reports that you can delete, then recover that disk space, also recovers disk space used to keep track of the jobs that generated those reports.

Check GO CLEANUP for how long you keeping various system job logs.

On our system, we have RTVDSKINF setup to regenerate the statistics at end calendar month, so we have recent statistics available. Be careful running PRTDSKINF to avoid massive door stop report ... start by selecting only those objects libraries etc. larger than some arbitrary thresh hold like 1,000 k, to see what is the truely big stuff on the system, then ratchet down the cut-off.

When implementing new applications, something perhaps ought to be run more often to see what kind of drain they putting on system resources.

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.



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.