Issue with ovrprtf/dltovr (is this an activation group issue)

Hi Scott

date: Tue, 11 Sep 2007 15:10:39 -0500
from: Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
subject: Re: Tell me more about activation groups (was Re: Issue with
ovrprtf/dltovr (is this an activation group issue))

It might be worth noting that your program is never removed from memory
if the activation group is never reclaimed. (This is true with
ACTGRP(*CALLER) as well -- except in that case, the programs are running
in *DFTACTGRP which Cannot be reclaimed, and therefore they always stay
in memory until the job ends.) This speeds up subsequent calls, but
also means that if you recompile the program, your batch job will
continue to re-run the old copy, and won't pick up the changes.

Thanks for the good explanation.
So why then do batch & interactive jobs behave differently?
With a batch job, the program is in memory and is released when the job
ends.
With an interactive job, it is in memory until the program ends. If one
compiles the program and then calls the program, the changed program is
called, not the one in memory - even though the activation group is still
active.

Hmmmm... I'm gonna have to test this... submit CL pgm, call pgma, delay 1
min, compile pgma meanwhile and see what happens.

Regards

Kit
(Still learning, after all these years)