Re: Maximum CPU Time and Maximum Temporary Storage settings to protect against run-away jobs

I'm going back in history here - I wrote a commercial monitor for Centerfield Technology about 12 years ago. It was called disk/HUNTER - has since been bought by S4I - so if a commercial version is in your view, check that out. I don't work for either of them, and there may have been enhancements since then.

disk/HUNTER (or its current name) doesn't put jobs on hold (nice feature) that I know of now, it did check every 15 seconds (or other setting) for reduction in free space that is beyond a threshold. That check is very light on the CPU.

I think there is a Help/Systems tool, Robot Space, maybe?

All of these give warnings of excessive DASD usage much sooner than the system capacity warnings.

Regards
Vern

On 2/11/2013 3:48 AM, Martin Rowe wrote:

On 8 February 2013 21:01, Eric Lehti <elehti@xxxxxxxxxxxxxxxxxx> wrote:

I would like to protect our system against run-away jobs.

[snip]

Hi Eric

We went a slightly different route with this. We have a background job
that takes a snapshot every 10 minutes and looks for jobs with
excessive temp storage or DASD over a preset level, or if it appears
to be climbing too quickly. For high temp storage we put the job on
hold (the level is set way above anything seen in normal use) and send
a message to QSYSOPR. That gets reviewed, and if it looks legitimate
we up the warning level a bit and release the job. That's worked well
for several years now, and I've extended our in-house version to
report on excessive CPU time used. You could add in anything else
that's specific to your way of working. The activity is logged to a
message queue, so it's easy to look back to see timings, etc.

http://www.dbg400.net/foswiki/bin/view/DBG400/DasdMon

Regards, Martin