Re: avoid running ILE programs in the DAG... -- RPG400-L

We had to put our service programs back into DAG because commitment control
would not work unless the program was running DAG.

We also ran into big problems with errors in named activation groups. Every
time that an error is thrown in a named activation group the system destroys
the activation group and when you try to go back to it the program crashes
because the pointer is now pointing at a object that doesn't exist anymore.

The only way we could seem to get around this was to run the service program
and programs in the DAG so that it could not destroy the activation group.

Totally bizarre behavior on IBM's part. Errors occur all the time. Why
destroy the activation group but that what they do.

I don't like running everything in the DAG but pretty much have no choice.

On Wed, Oct 6, 2010 at 8:12 AM, Stefano Arrighini - Smea s.r.l. <
s.arrighini@xxxxxxx> wrote:

Hi to all

Some years ago all ours programs ran in the DAG.

In the past two years we "introduced" Activation Group in some programs
(some in named AG, other in temporary ones).
We made this for various reason (avoid recursion, improve performance,
etc.).

Unfortunately (or better... by ignorance...) we made this operation
without having well understood Activation Groups.

Now I'm trying to do spring cleaning...

In all (or almost) technical articles and forum I read, I found the
advice
to avoid running ILE programs in the DAG.

So we modified our programs to run all of them in Named Activation Group
(or Temporary) and not in the DAG.
None of our programs are compilated with DFTACTGRP(*YES)!!
So I simply replaced *CALLER with Named-one in the ACTGRP option of ours
"starting program" (the first program in the call stack of ours job).

I found lots of advantages... but this operation introduced some problem
with OVRDBF scoping.

To avoid this problem I changed the OVRDBF (and OVRPRTF and DLTOVR) with
scoping problem.

A make an OVRPRTF and calls B
B calls C
C is in a different AG and isn't affected by OVRPRTF. But I want it.

OVRPRTF OVRSCOPE(*CALLLVL) was my solution..

Now my MAIN question is...
Compiling all my existing program in a proper Activation Group (not in
the
DAG), how many other problem can produce?

For example I found some difference in "free resources".
The RCLRSC LVL(*CALLER) used in the DAG can't be "replaced" with a
similar
command in a Named AG...
I have to close the Activation Group... Right?

Any help or observation would be greatly appreciated.
Thanks in advance

Stefano
--
This is the RPG programming on the IBM i / System i (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.