Hmm. I seem to recall at least one personal experience with Bad Things
Happening when certain ILE-only constructs were back-doored into
*DFTACTGRP by using *CALLER.
And what happens if you need a program that would behave badly in
*DFTACTGRP to terminate-but-stay-activated (either so it can pick up
where it left off, or so multiple calls in a batch job don't create
separate spool files)? Named activation groups can be most helpful in
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact