Re: Full database files

[John Carr <74711.77@xxxxxxxxxxxxxx>]

Date:   6/27/97  9:27 AM

RE:     Re: Full database files


Matthias
I think everyone should look at their shop's average(reasonable) number
of records in their files.  I mean; Are you a >100,000 shop or a 
100,000> / <500,000 shop or are you a 500,000+ type shop for instance.

Once you know that,  Change the CRTPF command to something reasonable for
your shop like; Init. 100,000 incre.10,000, # incre. 10
or something good for your shop.

I still think its imprudent to across the board change your files to *NOMAX.
The reason for having a ceiling is still valid.  Suppose you have a 
runaway program(not that any of us EVER have bugs in our production code)
The runaway program may add a Million records before you could kill it
and before you did, It might just kill you. 

In addition you should run a program (maybe something as simple as 
DSPFD *LIBL/*ALL TYPE(*mbr)  FILEATR(*PF) to a OUTFILE) once and awhile.
Then read that file and inspect the CURRENT NUMBER OF RECORDS, and the 
Initial Number of records,  ETC.  to see which files are close to 
max'ing out.

Then take action.

John Carr CDP
EdgeTech

At 05:07 PM 6/27/97, Matthias Oertli wrote:
>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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *