Re: Best Way to Kill Runaway Interactive Jobs?

1)  How does one define a runaway job?  Lots of CPU?  Lots of disk?  Never 
ending but neither of the first two?
We had a runaway query that sucked up disk space.  Set a cap on the group 
profile and that problem will never occur again.  Try to keep them at 80 
to 90% full.
After shooting a few people who insisted on *wrap or *prtwrap for all 
joblogs, the occurance of never ending dropped off significantly.  Instead 
of getting upset because their job ended because their log was full, they 
now try to find out why their log got full.
Lots of CPU?  Better start delving into the work management API's.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Ted Barry" <TBARRY@centralsan.dst.ca.us>
Sent by: midrange-l-bounces@midrange.com
01/22/2003 01:11 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     <midrange-l@midrange.com>
        cc: 
        Fax to: 
        Subject:        Best Way to Kill Runaway Interactive Jobs?


Does anyone know of a way to setup a server job to monitor and kill 
runaway interactive jobs?  This invariably happens when one is on 
vacation, but never when you're clued to the system.  Why is that?


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.