Re: Disk threshhold -- MIDRANGE-L

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

wrote on Tue, 21 Feb 2012 13:46:24 GMT:

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.

When the threshold specified by QSTGLOWLMT is reached, the action
specified in QSTGLOWACN will be taken. And you're right, it's
confusing because QSTGLOWLMT is % unused. Where the setting on
the ASP via service tools is % full.

I've long recommended the service tools limit be set at something
like 95-98% and QSTGLOWLMT be set to something >5-15%, or
possibly more depending on what percentage of disk your two or
three largest files are. Usually 10% is more than enough to give
you time after the messages start to "do something" before the
communications jobs start shutting down.

Back in the day when a MB was an expensive item I had written an
exit point program that would clean up known culprits for MBs in
use, but I broke it while trying to enhance it and we now rely on
*MSG.

Sue

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.