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


  1.  Home
  2. MIDRANGE-L
  3. November 2007

Re: Automatically killing long running jobs



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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.