Re: Starting out with sub-procedures

[Douglas Handy <dhandy1@xxxxxxxxxxxxx>]

JT,

>>| Bear in mind that QCMDEXC is call level sensitive when used for 
>>| OVRxxx commands.

>Would that be the case if the wrapper was compiled ACTGRP(*CALLER)...?

The problem isn't so much the activation group, it is the call level.

Overrides normally only apply at their own call level or below.  When the call
level where they were invoked goes away, the overrides go away with them
although I always consider it good coding to explicitly issue a DLTOVR as well
when done.

QCMDEXC is a special case, and is smart enough to allow you to issue a OVRxxx
command and have it take effect as if were coded at the level of the caller,
instead of lasting only for the duration while QCMDEXC is in the call stack.

However, by making a wrapper to QCMDEXC, you are introducing a new call level
between the original code and QCMDEXC.  Thus when it issues OVRxxx, QCMDEXC
detects that and makes the override apply at the level of the caller -- which is
to say the wrapper procedure.  Then when the wrapper returns and pops off the
call stack, the override naturally goes away with it.

This effectively makes it not very useful for issuing OVRxxx commands....

Doug