Re: Job behaviour RPGLE vs CLLE

Hi, Barbara:

Regards,

Mark S. Waterbury

> Barbara Morris wrote:

"Mark S. Waterbury" wrote:

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.

Mark, the re-resolve is not necessarily done even when using a
variable.  RPG keeps track of the library and program name that each
call-variable had when the program was resolved.  To get a re-resolve,
you have to use that particular variable to call a different program,
and then you can re-resolve to your original program.

 C       MOVEL   'PGM001    ' PGMNAM   10
 C       CALL                 PGMNAM
 C**       MOVEL   'DUMMYRSLV ' PGMNAM
 C**       CALL                 PGMNAM
 C       MOVEL   'PGM001    ' PGMNAM
 C       CALL                 PGMNAM

Without the call to the different program (commented out here), whatever
PGM001 it found on the first call will continue to be used on the second
call, since the value of PGMNAM is the same as it was for the first
call.

It isn't sufficient to just change the variable and change it back.  You
have to actually make a call with the new value.

For RPG/400, the FREE opcode would cause the program to "forget" the
resolved program and re-resolve.  But ILE RPG doesn't support FREE, so
to get that particular feature of FREE, you have to use this call to
some other program (which should be a very fast-running do-nothing
program).