RE: Full database files -Reply

Rather than using *NOMAX on the CHGPF SIZE parameter, it's better to use   
a finite size, but something large, just in case one a runaway job dumps   
out a vast quantity of records into a file while the machine is running   
unattended.  Use something like SIZE(100000 10000 1000).  (One hundred   
thousand records to start with, incrementing by 10000, incrementing 1000   
times.)

HTH

 -Doc

 ----------
From:   
 midrange-l-owner%midrange.com[SMTP:midrange-l-owner%midrange.com@mcs.com]  

Sent:  27 June 1997 08:26
To:  midrange-l; oertlim
Subject:  Full database files -Reply

I personally would use the Change Physical File (CHGPF) command to change   
the
member size to *NOMAX.  This would eliminate the message from showing up   
at
all.

Of course there is a draw back to this and that is that you will have to
monitor the file sizes
on your own.  However, this draw back may out way the messages sent to
operator.
I would not give the users the option to respond to QSYSOPR messages for   
the
sake that
they may respond incorrectly.  Not to knock users, but they are not   
trained
on what the
QSYSOPR messages are.  I would rather increase the member size to *NOMAX   
and
monitor file sizes than give a user a chance to cause problems.

Hope this helps

Rich

 ---
Rich Brearley
Programmer/Analyst
Durham County Hospital Corp

>>> "Matthias Oertli" <oertlim@s054.aone.net.au> 06/27/97 05:07pm >>>
As everybody knows, every time a database file becomes full, the
system sends a message to QSYSOPR asking to increase the
file's size. You choose ignore, and that's that.

While the system is waiting for the 'file-full' message to be answered,
the job is on hold, obviously. If it happens to be an interactive job,
the user/workstation is on hold until the message is answered.

I would like to know how you people handle this situation. Do you
let the users do Sysreq 6 and answer the message? Do you add
the 'file-full' message to the system reply list and change all jobs to
use it? Is there an ever-present operator standing by to answer these
messages?

Your thought on this are appreciated.
Regards,
Matthias
 --------------------------------------------------------------------------  
 -----
 ------------------
Matthias Oertli, Sydney, Australia

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *