Dave

At 06:46 PM 12/2/1997 -0500, you wrote:
>
>If PGM_A contains a dynamic call: 'CALL PGM_B'
>and that line of code is executed 1,000 times, does the
>EXACT SAME PROCESS occur 1,000 times?  In other words,
>for each of the 1,000 dynamic calls, does the address of PGM_B have
>to be resolved, does the user's authority to PGM_B have to be checked,
>and whatever else needs to get done..... for each one of the 1,000 CALLs?

I think it depends. John Carr mentions using a variable for the program
name—are you talking about this, or the standard RPG CALL opcode?

If you're talking about calling an RPG, it will be more efficient to _not_
turn on *INLR until the last time. If you use MOVE *ON *INLR, then the RPG
program gets closed down every time, and initialization (whatever that
entails) is repeated for each CALL.

Another factor is purging/paging. If you use the same object many times and
with little time in between, the object will still probably reside in main
memory, so that your app won't need to go get it on disk (page fault). But
this is always the case—nothing to do with *INLR, e.g.

I suspect every call to a CLP requires reinitialization—along the lines of
turning on *INLR in RPG.

JMHO

Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN  55401-2499
(612) 371-1111 x480


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


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-2019 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 here. If you have questions about this, please contact [javascript protected email address].