|
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.