RE: is operating system always to blame, was: Ready to scrap an AS/400

>Say the program loops and writes records into a data file of some sort,
> the procedure fills up the disk. This can happen by the way. An AS/400
>query with improper joins specified will also fill up disk. The cannot
know
>what is filling up the disk, it can only warn someone that the disk is
>reached its threshold. Eventually, the machine will fail. I'd say that
this
>is not the fault of the OS.



That was the original reason for the  SIZE parameter on the CRTPF
We've bumped up our default from the 13,000 to this;

 Member size:                     SIZE
   Initial number of records  . .                100000
   Increment number of records  .                10000
   Maximum increments . . . . . .                10


You should set some default for your shop for runaway programs as described
above.

*NOMAX is NOT a good thing to use as a standard.  If you use it,  You
better be darn sure you know the programs that will add records to that
file and TRUST them ALOT.

Like John Blushi said in Animal House,    "It's your own fault flounder,
you shouldn't have trusted us"


John Carr



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---