Re: No longer stuck, but more "busy" messages. -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Are there HTTP jobs that just sit at a Running status? For me (7.3), the
typical idle statuses are:
Waiting for dequeue
Waiting for signal
Waiting for time interval

date: Sat, 16 Jan 2021 12:32:53 -0500

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 no
call stack and not actually doing anything.

Are you not familiar with the IBM HTTP server jobs? ;)

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.

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.