RE: Job behaviour RPGLE vs CLLE - Explained

This explains it exactly. Thanks Mark.

Hi, Jim:

This happens if you code in RPG/400 or RPGLE like this:

      CALL   'PGM001'
versus:
      MOVEL   'PGM001'   PGMNAM   10
      CALL      PGMNAM

This second case causes RPG to generate the full dynamic call that 
"resolves" to the name on each call.  Note that there is more

"overhead" 

for doing it this way.

For this reason (in order to reduce runtime overhead for needless 
re-resolving), when the name of the object called is known at 
compile-time, (the first case above), IBM compilers generate the code

to 

do the "resolve" (issue RSLVSP MI instruction) in the "initialization" 
part of the *PGM, so this overhead is incurred just once, and from that

point on, e.g. at the point of the CALL, a pointer to the *PGM is used 
(already resolved). 

 
Fast is fine, but accuracy is everything. 
Earp, Wyatt
This message has been sent from Foodstuffs (Auckland) Limited ("Foodstuffs").

The information contained in this message and or attachments 
is intended only for the person or entity to which it is 
addressed and may contain confidential and/or privileged 
material. Any review, retransmission, dissemination or other 
use of, or taking of any action in reliance upon, this 
information by persons or entities other than the intended 
recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any 
system and destroy any copies.

The views and opinions expressed in this message may be those
of the individual and not necessarily those of Foodstuffs, 
and are not given or endorsed by it.

Please note that this communication does not designate an 
information system for the purposes of the Electronic 
Transactions Act 2002.