|
from: John Yeung <gallium.arsenide@xxxxxxxxx>
subject: Re: No longer stuck, but more "busy" messages.
On Sat, Jan 16, 2021 at 9:25 AM Brad Stone <bvstone@xxxxxxxxx> wrote:
On Fri, Jan 15, 2021 at 6:27 PM James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:
I'm still puzzled about how a job can be in a "RUN" state showing noAre you not familiar with the IBM HTTP server jobs? ;)
call stack and not actually doing anything.
I'm not in front of an IBM i session to check right now, but don't
those kinds of things spend most of their time in some kind of wait
status? When they wake up to actually "do something" then they do have
a run status (as in, literally showing "RUN" in the WRKACTJOB
display), but it is usually fleeting. If you do manage to catch them
in that status, I am confident they have a call stack.
John Y.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.