Re: Disk threshhold

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Rob

You might consider adding a tool to monitor for growth, to tell you long 
before these thresholds are reached. This isn't a verndor response, BTW.

I'm aware of 2 - I wrote one for a former employer, called disk/HUNTER - 
it is now marketed by s4i - I forget the name. You basically specify 
%-reduction in free space - maybe 5 by default. You will get various 
actions when that happens, including comparing total space by 
user-owned, etc. This one wakes up every maybe 15 seconds and checks 
free space - it's very light impact on the system - my boss at the time 
is a brilliant guy, he came up with the mechanism. It does not do 
anything high-impact while monitoring - it may do a PEX trace, which can 
be intense, when a problem occurs.

Oh, yeah - I think Help Systems has one, too.

I think one of the regulars here wrote a free one - Martin Rowe - he 
calls it DASDMON, last I saw.

These utilities will catch short-term spikes - RTVDSKINF won't do that. 
We had a brief thread on this a while back - 
http://archive.midrange.com/midrange-l/201007/msg00563.html

HTH
Vern

On 2/21/2012 7:46 AM, rob@xxxxxxxxx wrote:
> I thought I understood you clearly at first and I was going to reply:
>
> Thank you Sue.  We were thinking the opposite, meaning, we were thinking
> of having STRSST lower than QSTGLOWLMT because of that draconian
> QSTGLOWACN value of *ENDSYS.  Perhaps if we stuck to *MSG or *CRITMSG then
> a lower QSTGLOWLMT than STRSST makes sense.
>
> But then I got myself confused again.  Let's blame it on QSTGLOWLMT being
> percent available and SST being percent used.  So are you saying we should
> set QSTGLOWLMT to something like 10-20% available and have STRSST set to
> 91-95% used?  So when QSTGLOWLMT is hit then a QSTGLOWACN of *MSG or
> *CRITMSG kicks in and then if no appropriate action is performed then SST
> kicks in and shuts down a few operations.
>
> If we use *MSG for QSTGLOWACN then QSYSOPR and QSYSMSG both will get
> CPI099C - Critical storage lower limit reached. at the lower percentage
> and then later SST will kick in and QSYSOPR and QSYSMSG will both get
> CPF0907 - Serious storage condition may exist. Press HELP.  Along with SST
> killing operations like:  FTP, SNDDST, SNDNETF, and more.
>
> Rob Berendt