You would think that such a process would need to know how long the job should normally take and hopefully the process is not extend by additional data being process.
The other way, would be for a process to monitor all the file I/o and determine if any additional records are either being created or read; thereby determined if there is any I/o and abort if the process is in an idle state for an extended period of time.
There are many more methods but any way that is chosen would require data to determine when/how of even if a process should be abended.
FOR example, take MS Windows, exactly how long should one wait to determine if the system has died or still updating. Not that long ago, MS was doing its thing, which eventually ended some 12 hours later. I was a patch.... (I hope).
Olav.
---- John Sommer <[log in to unmask]> wrote:
> All,
> On rare occasion, some jobs get "hung" for one reason or another, and system processing is halteduntil someone discovers the problem job and aborts it.
> It happened again Friday night. A job hung and all weekend processing was waiting in queue for that job to finish.Has anyone found a utility that monitors job run time, so that it can auto-abort such jobs after X number of hours?
> Thanks for any suggestions,John
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
