Re: File Size / Reuse Deleted Records

Hi Buck

100% agreed.

In the last 10+ years the only "runaway jobs" I have ever seen that had any
out of control impact on DASD usage were the result of WRKQRY with file
output selected. These files are also created by default with *NOMAX so
there is no way to prevent someone chewing up the storage via WRKQRY short
of managing storage at the profile level (which I also never bother with).

I recommend never attempting to manage the storage at the table level, it
always causes more problem than it solves by unexpectedly stopping jobs
when they hit the "number of record" ceiling.

Instead, invest in whatever you require to allow you to get system alerts -
including storage messages - and manage the system at the storage level.


On Fri, Jan 15, 2016 at 8:45 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

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.

--
--buck

Visit wiki.midrange.com and register for an account. Edit a page that
helps you, and because it's public, you'll help someone else, too!

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.