×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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.
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.
midrange.com
