Looking for advice: How to detect a job is actually doing work
David Gibbs via JAVA400-L <[email protected]>
| Newsgroups | gmane.comp.lang.as400.java |
|---|---|
| Message-ID | <[email protected]> |
Folks: I'm looking for advice on the best way to detect if a job is actually doing work. Currently I'm getting the call stack from the Job object and comparing various attributes of it to a previously retrieved call stack. Sadly, the CallStackEntry class doesn't implement a proper equals method. If the current call stack is different from the previous call stack, I'm taking that as a hint that the job is doing work. Are there any other job attributes, or techniques, you can think of that would be useful in identifying a hung vs. active job? Thanks! david -- I'm riding in the American Diabetes Association's Tour de Cure to raise money for diabetes research, education, advocacy, and awareness. You can make a tax-deductible donation to my ride by visiting https://mideml.diabetessucks.net. You can see where my donations come from by visiting my interactive donation map ... https://mideml.diabetessucks.net/map (it's a geeky thing). -- 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