RE: Automatically killing long running jobs

Are you trying to reduce the number of pages being produced, or to reduce
the workload?

One thing I did at a client site was to have a prompt screen that popped up
when a user submitted one of the big hitters. The user was told that the
program would take a long time to run, and would it be permissible to submit
it to run at night. If they responded with a "Y" (which was the default),
the job was submitted to the nightly job queue. That queue was released when
the backups were finished, and held again at 6 AM.

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces+nelsonp=speakeasy.net@xxxxxxxxxxxx
[mailto:midrange-l-bounces+nelsonp=speakeasy.net@xxxxxxxxxxxx] On Behalf Of
Jim.McLean@xxxxxxxxxx
Sent: Monday, November 12, 2007 10:25 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: Automatically killing long running jobs


Hi Everyone,

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?