× 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.



Chuck,

Thanks for the info. I didn't ask the question, but it's always good to know
this sort of stuff...

Rory

On Tue, Nov 30, 2010 at 9:43 AM, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 11/12/10 2:10 PM, Pete Hall wrote:
On 2010-11-12 04:55, rajeev chandel wrote:

Any idea about [Subject:].

Is there any reason why we don’t see the Call Stack of the Job,
when the job is ACTIVE?

I've seen that when the job is using a lot of cpu cycles, like when
running a SQL query that builds an index. It waits long enough to
time out, then shows an empty call stack display.


FWiW the CPU utilization is unlikely to have prevented directly, the
display of the *PGMSTK in the index-build scenario. In that scenario,
the process [primary thread, or any secondary thread for thread stack]
performing the index-build [job status IDX] is operating in the LIC
["below the MI"]. A LIC function can not be interrupted [except by a
LIC request], so typically each MI instruction is designed to effect
only "quick" operations. The index-build request is at least one
exception, a long-running LIC\MI operation [Load\Dump AKA Restore\Save
are other examples]. These atypical instructions are interrupt-capable
only by either the completion of the task(s) implementing the feature,
or an explicit action by the LIC to "look for" an interrupt [often
described by the idiom "coming up for air"]. Any unmasked operation,
i.e. any non-LIC program processing being performed ["above the MI
boundary"], can be interrupted by the MI instruction to materialize the
program stack. The WRKJOB or DSPJOB being used to materialize the
program stack has a timeout limit [perhaps established by the DFTWAIT
for the job] for the materialize request, so when the operation being
performed can not be interrupted [such as with the database index
build], an error will be logged and the "display call stack" will be empty.

Regards, Chuck
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.





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-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.