Re: Looking for advice: How to detect a job is actually doing work
"D*B" <[email protected]>
| Newsgroups | gmane.comp.lang.as400.java |
|---|---|
| Message-ID | <CDF8944102D34BCA8F17643062BB8574@Lisp> |
<David> Maybe I didn't explain my question. I'm just looking for advice on what Job attributes to consider to determine if a job is active or not. I've already got the CallStackEntry array. I'm also considering the job active status. Is there anything else that would be a good indicator that a job is active and not hung up? </David> ... what's your definition of "hung up"? a job could be waiting for an event: end of another job, end of another thread, user input, a message from another job, an external ressource. In most of these cases it might be impossible making an automatic decision if the job could be waiting forever. D*B -- This is the Java Programming on and around the IBM i (JAVA400-L) mailing list To post a message email: [email protected] To subscribe, unsubscribe, or change list options, visit: https://lists.midrange.com/mailman/listinfo/java400-l or email: JAVA400-L-request-+hD5IHI5Xscn3HwCXmMcX9BPR1lH4CV8@public.gmane.org Before posting, please take a moment to review the archives at https://archive.midrange.com/java400-l. Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com