Re: ACTGRP

Hi David,

I believe you are saying that a named group does not automatically
end like a *new group. In that case,when would it end?

It ends when you run the RCLACTGRP command (think of RCLACTGRP like RCLRSC -- except that it's for one activation group at a time.)

If you never run RCLACTGRP, then it stays active until the job ends (in this case, that'd be when the user signs off) in that case, it's just like the default actgrp where the OPM programs run (since the default actgrp only ends when the job ends)

Currently I cannot do what I'd like to because the application is
mainly OPM. After the first call, files of the previous library list
may remain open so even if I change the library list the program will
continue to use the files of the original library list.

I don't understand that. If you don't want the files to stay open, code CLOSE *ALL in your RPG program. What does this have to do with whether the code is ILE or OPM?

The idea was that by converting the OPM source and using an
activation group, this problem would evaporate with the activation
group at the end of the program.

That's true, if you use ACTGRP(*NEW) -- then all of the ACTGRP(*CALLER) programs will evaporate when the ACTGRP(*NEW) program ends.

Or, if you use named activation groups like I suggested, then you can run RCLACTGRP to reclaim them... easy enough.

But as the user on each entry can effectively change the library
list, I wondered if I could create a named activation group for
each product and keep all my files open between calls.

Yes, that's what I suggested.