Re: Looking for activation group opinions

[Mark Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>]

Sam,

When the job ends, all of the activation groups are deleted / destroyed -- all files are closed, and any dynamic storage is freed, etc. -- everything is "cleaned up."

You can also get much the same effect by issuing RRTJOB -- this ends the routing step (aka. job step) and will close all open files, free dynamically allocated memory, and delete all activation groups, except for the default activation group ... that gets cleaned up so it looks like it did when you first signed on.

NOTE: I would never suggest using RRTJOB in production code, but it can occasionally be useful for cleaning up between each testing iteration when "debugging" -- especially if you need to recompile some programs or service programs that may have been "activated" in one or more ACTGRPs in your job.

Mark S. Waterbury


> On Saturday, March 5, 2022, 12:40:25 PM EST, 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