We would like to "catch" jobs that have been in ready status for longer time than expected.
One way to do that could be to define two correlated events in EDWA and then let the second event trigger some handling if the first event (job in ready) have been active
for more than x minutes.
But is there other (smarter) ways to do that?
Is there a "long in ready" feature similar to maxdur/mindur in plans?
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
2 replies Latest Post - 2013-03-07T22:40:22Z by mymaestro
Pinned topic Catch jobs in ready status for long time
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-03-07T22:40:22Z at 2013-03-07T22:40:22Z by mymaestro
Fabrizio1975 0600020REY7 PostsACCEPTED ANSWER
Re: Catch jobs in ready status for long time2013-03-06T09:31:31Z in response to SystemAdminHello Finn,
there is not a mechanism similar to Maxdur for job in READY,
even because we can not leverage to an "estimated time" as for the Maxdur.
So the the event rule with a timeout action I think is the best way.
mymaestro 200000237U206 PostsACCEPTED ANSWER
Re: Catch jobs in ready status for long time2013-03-07T22:40:22Z in response to Fabrizio1975Just to clarify, you only need one event rule to manage the READY states. It's a sequence of events with a timeout action.
Unlike job duration, there really is no reason for READY to exist longer than a few seconds... unless they really do use workstation limits to throttle production, and I don't find any customers doing that for several years now. Tell me if I'm wrong ;-)