AW: activation groups and rclrsc

Hi,

yet an other idea:
1. Programs are only those objects that are
   either called from a menu, from command line or submitted.
2. Programs get a named activation group
   --> Activation group = program name
3. A program consist only of a series of procedure calls.
   Instead of creating programs, the modules are embedded in
   service programs.
4. These procedures are embedded in service programs.
   Because we still have a couple of RPGIII programs, we sometimes
   generate programs and service programs, to allow calls from
   RPGIII programs.
5. All service programs that contain Insert, Update or Delete procedures
   use activation group *Caller.
   (To use commitment control and on activation group level)
6. Other service programs may also get named activation groups
   (Activation group = Service Program Name)
   to minimize activation for procedures that are called
   from other procedures (i.e. date procedures)

Mit freundlichen Gruessen / Best regards

Birgitta

"Shoot for the moon, even if you miss, you'll land among the stars."
(Les Brown)

-----Ursprungliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]Im Auftrag von Tony Carolla
Gesendet: Mittwoch, 11. Januar 2006 01:12
An: RPG programming on the AS400 / iSeries
Betreff: 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"
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.