Re: PF member current number of increments larger than the max

Well you can also set system value QSTGLOWLMT to shut the system down to a
restricted state instead of letting the system go down hard.

Most of the issues I have seen of late have been the system running out of
disk due to temp stg being used by SQL; setting the right number of records
won't help you there.


On Wed, Nov 7, 2018 at 7:41 PM Don Brown <DBrown@xxxxxxxxxx> wrote:

I have a weekly scheduled process that runs a query and emails me the
report if any files are within a predefined percentage of full.

This runs on about 10 systems and Monday mornings I have 10 emails to
quickly review and check if any files need attention.

I can then review the list and either investigate if a file has an abnormal
number of records, run a reorg if there are a lot of deleted records or
adjust the file size for normal growth.

I am on the side of *NOMAX is a disaster waiting to happen. I remember the
Long IPL's for System/38 when a system ended abnormally with no disk space.

Cheers

Don Brown




______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com