|
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
such situations.
As an Amazon Associate we earn from qualifying purchases.
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.