× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Alan -

Short version of the question is, what are the gotchas for a call stack
like this, program-to-program:

*DFTACTGRP --> *DFTACTGRP --> *NEW --> *DFTACTGRP.

There aren't many. If you issue any OVRSCOPE(*CALLLVL) overrides in the *NEW activation group, they will NOT be in effect for the programs in the *DFTACTGRP group called from *NEW.

But if you issue any OVRSCOPE(*CALLLVL) overrides in the *DFTACTGRP program from which the *NEW program is called, those overrides WILL be in effect both in the *NEW activation group and the *DFTACTGRP activation group called from *NEW.

If you call any *DFTACTGRP programs from *NEW that remain active (i.e. return with LR off if RPG), they will remain active even when the *NEW activation group is destroyed.

There may be other issues, but I can't think of any more at this time. I do this quite a lot calling OPM programs to lookup up an item number or customer name based on the description/name and don't have any problems.

I can't remember where I've done this, as I always made sure, to the
best of my recollection, that they were

*DFTACTGRP-->*NEW-->*CALLER.

For new development that is the way to go certainly.

Ken
http://www.kensims.net/
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.