Re: Looking for activation group opinions

Sam, I meant to write pgm not job: "The reasoning behind this, is that named actgrps are not deleted/destroyed when the job pgm ends, they remain inactive/dormant for when the pgm(s) are called again."
Example: PGM_main (actgroup named:AG_DRV), runs 2 pgms, pgm1 (actgrp = *new), pgm2 (actgrp = AG_2). When pgm1 runs a random AG is created and deleted when it ends; when pgm2 runs for the first time AG_2 is created and when it gets done remains with 'In Use' status = 'No' meaning not deleted/destroyed just ready  for when the same pgm gets called again.
Yes when the job ends all act grps are deleted whether it's a batch job or if it's interactive until the session ends. On Saturday, March 5, 2022, 11:40:27 AM CST, Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:



On 3/5/2022 12:03 PM, Code 1109 via RPG400-L wrote:

  Alan, in generally speaking, to get a better pgm performance and if you know that a pgm or series of pgms are going to be called more than once in a job then it's better to use a 'named' activation group and have the called pgms use that one or *CALLER.The reasoning behind this, is that named actgrps are not deleted/destroyed when the job ends, they remain inactive/dormant for when the pgm(s) are called again.

Is this true, that "named actgrps are not deleted/destroyed when the job
ends"?

Sam