×
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.
<vendor response>
For a cheap insurance policy against unexpected DASD spikes check out
disk/HUNTER:
http://www.centerfieldtechnology.com/tools/diskhunter.asp
</vendor response>
As for estimating recovery time, it is pretty much impossible to do without
knowing much more about your system's config (journaling, SMAPP, ...).
Significant part can be played by access path recovery time for large
indexes that are automatically journaled by the system (SMAPP). Once IPL
starts you can use EDTRCYAP to check the estimated times. Going forward you
can use that same command to be more or less aggressive about future
recovery times.
You may also check into changing journal recovery ratio to be more
aggressive on recovery time. Search InfoCenter on QJOCHRVCR program.
Good luck.
Elvis
Celebrating 10-Years of SQL Performance Excellence on IBM i5/OS and OS/400
www.centerfieldtechnology.com
-----Original Message-----
Subject: Recovery Time estimate for abnormal system end due to DASD usage
All,
Just wondering if anyone has any experience or knowledge to share I can use
to estimate how long it
might take to re-IPL after an abnormal system end cause by the DASD filling
up.
Box is an 810 running v5r2, with 500GB (14x70GB mirrored) DASD and about
1,500 active jobs unusually
running 50-60% CPU.
Thanks!
Charles Wilt
midrange.com
