Re: override scope in a procedure

Charles Wilt wrote:

So do you have an example of where *CALLER would pose a problem for a program?

Or is an ILE program running in the default activation group via
*CALLER not so bad as long as no service programs are being used?

You're right that it's not so bad.

One possible downside is that the system never deallocates the static storage allocated to a *CALLER program running in the default activation group. So if you have a long-running job where several different applications get run, there's a potential of running out of storage. I have no idea if that's a real concern or not; I don't recall ever hearing about that happening.

Another more probable downside is that building a dependency on running in the default activation group as *CALLER limits future use of service programs for that application. But the limitation isn't obvious, so a *CALLER=DFT service program could go into production with the problem waiting to surface at the most inconvenient time.