Re: Full database files

[Danny McQuestion <dcmcques@xxxxxxxxxx>]

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?


        I have a system reply list entry that says to give the message an 'I'. 
The thing is, the jobd's are not set to use the system reply list entry
by default.  An operator has to change the job.  This prevents the job
from running away without anyone knowing and keeps the operator from
having to answer and endless amount of messages.  I've got plenty of
DASD as to not to have to worry about a file filling up too much and
shutting down my system.  I do have a program that monitors QSYSOPR for
messages.  It does automatically answer the maximum spool file messages
for me with 700,000.  It pages me each time it answers one of these
messages.

        If you have a reoccurring problem with the same file, I would recomend
changing the size instead of having to battle with messages.

Danny Mc? 

---
Danny Mc?
E-mail:    dcmcques@vantek.net
 or Click: mailto:dcmcques@vantek.net
Web Page:  http://www.vantek.net/pages/dcmcques/index.html

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.2

mQCNAzF0vwQAAAEEANHAlvrDaRFM5J3H/OZCdfIMWDDmJnfutn7nhd6RUJiGCey2
sCH0PBAFhonINuI/bm0ACk4gRuwoQfERuLUMeESvMjNbcnt1qrpjsPVB9GyUs8x5
kB4gTzjD5UXQOF+EnD5I9wgSsPlXeTfwLXTs4RXUdTKoYHkxhsDJ9mZy58+NAAUR
tCZEYW5ueSBNY1F1ZXN0aW9uIDxkY21jcXVlc0B2YW50ZWsubmV0PokAlQMFEDF1
3jq89vGA2+K4WQEBa6gEAIxGmjwzJ0ezTPJdDKro+C55y9XVjoRWNcGSXDZHtDun
/aGx16AQ98RjCOoJH48ze4keG+KsUrSa7xXaPQpbOnoAP6I6Yanq3lxSEZzkUj/V
EL+C8LWDJli5dPyXXVnvyiZ4uoVpydQeL1lEzXm4xoCOMWe5pUkjc1+B3dtWb2Mw
iQCVAwUQMXXYK8DJ9mZy58+NAQFWEQP/TRU0eIpW2LaHygMNeiISOcPr3YX7Gbga
pdVi1oqi6ujSS5bWAE2qQG8OGpYjz25JpYBUMQgxfsaqhZ/P820CrcChqgu99ujM
J0goQPr2SY5mezg9Z8rd7EVgTg0BMIVjGSTf3IAPGdH9gStzSeFDKtGEzYgn+9tx
S7ZNYDwImUg=
=cnWd
-----END PGP PUBLIC KEY BLOCK-----
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *