Re: Automatically killing long running jobs

Hello,
How I am doingthis at the moment:

1. At regular intervals 15 min
I run TAATOOL/CVTWRKACT and keep the results in a file.
2. Run it again in 15 min and see whatever the previous jobs have finished
and which one is still running
3. If one is still running after a certain period of time I kill it. :)

Thanks
mihai


On 11/12/07, Marc Rauzier <mrauzier@xxxxxxx> wrote:

Le: 12 nov. 2007, vous écriviez dans:
gmane.comp.hardware.ibm.midrange:

Hi Everyone,

Hello Jim

I'm looking for a solution to my problem of long running reports.
Everyone once in a while a user gets carried away and submits a
very, very large report to the system. What I would like to do is
kill any reports that run for more than X minutes. These reports
run in our reporting queue/subsystem, so it would be safe to kill
any job in that subsystem that's been running for more that X
minutes.

Any ideas on how best to accomplish this? Or am I off the mark in
trying this?

You can try to create your own class for your subsystem and use the
"MAX CPU time" parameter. If you setup this parameter to anything else
than *NOMAX, the system will end the job when it uses more than the
number of milliseconds CPU. This is not exactly what you are looking
for but it may help.

--
Cordialement
Marc Rauzier
(pour me répondre, ne pas utiliser le from mais le reply-to)



--
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.