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



> From: Chris Rehm
>
> Maybe I'm wrong about this, Joe, but I think the LR processing done by
> the main module only allows LR processing in that module. The called
> modules are dumped from memory because they are dependent on the main
> module for their place in the PAG, but they don't get LR processing,
> right? Or am I all messed up on this?

I really mistyped, Chris... sorry I misled you.  I was not talking about
true LR processing (that is, lines of code conditioned by the LR indicator).
I was referring to the concept of being purged from memory, and thus
subsequently going through initialization.  I haven't actually tested
whether LR processing occurs, my guess is that files and the like will
definitely be closed.  What would you call this processing?  "Shutdown"
processing, for lack of a better term?  In any event, my observation was
about whether initialization was called again for submodules after the main
module ends with *INLR on.

I found something very interesting.  With the following situation:

1. MAIN1 calls SUBP1 (using CALLB)
2. SUBP1 does not set on *INLR
3. MAIN1 does not set on *INLR (does a RETURN)

Call MAIN1 twice in a row, and SUBP1 *INZSR gets called both times.  In
fact, the *INZSR for MAIN1 gets called each time.  It's as if the concept of
*INLR is ignored for the main module, and when the main module executes a
RETURN, *INLR is set on automatically.  This is very bizarre.

Joe



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.