MIDRANGE dot COM Mailing List Archive



MIDRANGE-L » February 2013

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



On 8 February 2013 21:01, Eric Lehti <elehti@xxxxxxxxxxxxxxxxxx> wrote:
I would like to protect our system against run-away jobs.

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,

I don't think that anyone has yet mentioned in this thread that there
are similar limits you can configure in System-i Navigator (Look in
Management Cetnral, then for the Monitors section)
These came out in V4R5.
One drawback to them is that since it is client-based software, you have
to have be logged in, and I don't believe it feeds a message queue.
However, on the plus side, it does show out-of-compilance in red and
will interupt your PC work when it senses something beyond the limits
you set.

-John V.





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact