** This thread discusses the article: Unraveling the Mystery of Activation Groups **
** This thread discusses the Content article: Unraveling the Mystery of Activation Groups **
0
** This thread discusses the article: Unraveling the Mystery of Activation Groups **
** This thread discusses the Content article: Unraveling the Mystery of Activation Groups **
0
** This thread discusses the article: Unraveling the Mystery of Activation Groups **
What are some of the specific benefits of using activation groups? What are some of the the specific pitfalls of using activation groups? Thanks in advance for any intel.
** This thread discusses the article: Unraveling the Mystery of Activation Groups **
It's nice to know how to use activation groups but why bother? What does it do for me? What does it do for the users?
** This thread discusses the article: Unraveling the Mystery of Activation Groups **
What about using commitment control, OVRxxxF, shared open data path?
** This thread discusses the article: Unraveling the Mystery of Activation Groups **
Using DFTACTGRP(*ELIGIBLE) is a very dangerous thing to do. It might reclaim system activation groups that are important to your job. When you want to clean up many activation groups, the easiest way is just to sign off and sign on again. If you don't want to sign off, the correct action is to do a DSPJOB, find out what activation groups are being used, and individually reclaim the ones that are associated with your own applications. If you don't know why an activation group is there, you should not reclaim it.
** This thread discusses the article: Unraveling the Mystery of Activation Groups **
"Limited function is defined as programs that don't contain any procedures, don't call any procedures, and use no contemporary built-in functions (BIFs) ..." I think %PADDR is the only built-in function that is not allowed for a DFTACTGRP(*YES) program. " ... as well as any features that require procedures not supported by *DFTACTGRP." What other features besides bound calls and %PADDR require procedures not supported by *DFTACTGRP?