Re: override scope in a procedure

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

JDHorn@xxxxxxxxxxxxxx wrote:
>    I am trying to write a procedure or service program call to execute
>    override printer file commands. 

A procedure *or* service program?  Did you mean to say a procedure *in* 
a service program?


>    It seems that in either case the scope of the call level is greater than
>    the call level of the program that called it.

Yes.  That's the way procedures work, each call to a procedure creates a 
new call level.


>    Is there a way, other than using creating a string and calling qcmdexc
>    using Call/Parm to get the override to be at the same level as the calling
>    program?


You don't have to use call/parm -- you can (and should!!) use a prototype.

But, if your override logic is complex enough to warrant calling a 
procedure (not just a prototype) then you might consider using 
OVRSCOPE(*ACTGRPDFN) and running your program and override subprocedure 
in the same ILE (non-default) activation group.

You see... the call-level only matters when you use OVRSCOPE(*CALLLVL) 
or when you run your override from the DFTACTGRP.  When using proper ILE 
activation groups with *ACTGRPDFN the override applies to the entire 
activation group, regardless of call stack level.

That's one of many ways that activation groups make life better.