Re: activation groups and rclrsc

Hello Jim.

On 1/10/06, Jim Horn <jimh@xxxxxxxxxxxxxx> wrote:
>
> In the future we will try to move to the AG *new/*caller approach.  In our
> system, often a program that is on a menu is also called by another
> program,
> so it is hard to determine which programs are indeed *new. Don't know how
> much of a problem it is to have several programs running in a *new AG if
> they are only called a few times.  (pgma calls pgmb calls pgmc all in *new
> AG's because we don't necessarily know which one will be called first)


As I understand it, each time you call a program that was created with the
ACTGRP(*NEW) specified in the header, a new activation group is created for
the job.  This can be costly, if in your example you have three program
calls, that means that three new activation groups will be created, one for
each program, each time each program is called.  If you call the same
program three times, you get a new activation group created all three
times.

This can lead to slow runtimes.

--
"Enter any 11-digit prime number to continue..."
"In Hebrew SQL, how do you use right() and left()?..." - Random Thought
"If all you have is a hammer, all your problems begin to look like nails"