On Thu, Aug 5, 2021 at 8:27 AM David Gibbs via JAVA400-L <
java400-l@xxxxxxxxxxxxxxxxxx> wrote:

Folks:

I'm looking for advice on the best way to detect if a job is actually
doing work.

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?


How often do you see a "hung" job? I don't think I've seen one in the
25yrs I've been on the platform..

I have however seen lots of jobs stuck in a poorly written loop. Checking
the call stack isn't usually enough to determine if that's what's actually
happening as it does usually change...but we do have a lot of ILE
procedures. With OPM, I suppose only the statement # is prone to change.

Our monitoring looks for "high" (> 5% or so) CPU use over an
extended period of 60min or so I think.

But even then, it usually is up to the on-call person to debug the job and
see if it's looping or working as designed.

Charles

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.