Re: Program or Procedure

On Feb 9, 2010, at 1:00 PM, rpg400-l-request@xxxxxxxxxxxx wrote:

Thanks, Jon. For clarification, does "activation path" mean the
startup/initialization time, or something else in this case?

Also for clarification, if this is the second call, and LR was left on,
etc., etc., then how does the performance compare?

I agree with Scott that the performance difference for the OP's requirement is a non-issue - but I'll comment briefly.

I meant "something else" because the startup etc. only takes place once. I should add though that some of the startup overhead saved by leaving LR on in the called routine is only saved _if_ the calling program also remains active. It stores a pointer to the called program so if it LRs itself then that pointer is lost and must be resolved on the next call.

Basically the path from call to first line of user code is shorter for a procedure call - the figure of 16 or 18 X best case scenario mentioned in an earlier post sounds about right. Program calls involve calls into system level APIs etc. to determine parameter access and so on. Procedure calls are much more direct - not exactly "just a branch" but much closer.

I think Barbara and/or Bruce have detailed some of this in earlier posts in other threads.


Jon Paris

www.Partner400.com
www.SystemiDeveloper.com