Re: File Size / Reuse Deleted Records

On 1/14/2016 2:21 PM, rob@xxxxxxxxx wrote:

Having some sort of ceiling does help to prevent the "run away" job.

I deal with a tremendous variety of code here, from System/3 vintage
matching record to brand new **FREE. In 8 years I have yet to encounter
an unattended runaway job. Now, when a developer is testing
something... sure. But they're usually quick to kill that job. Lot of
words to say that I don't worry about a runaway job filling up my DASD.
And we run unattended at night and weekends.

What I fail to see in that, and in SYSTABLES or SYSTABLESTAT, is the
maximum number of rows.

I didn't see that either; DSPFD shows the increments, the increment size
and the file capacity. If I had to manage disk tightly, I might DSPLOG
LOG(QHST) MSGID(CPF4058 CPA5305) to find candidates. Then DSPFD these
to help analyse what needs to happen.