Re: avoid running ILE programs in the DAG...

Your assumption are correct but if I put the other service program in a
named activation group and they throw an error I am screwed. The exception
shuts down the named activation group and I get an error the next time I try
to refer to it.

On Wed, Oct 6, 2010 at 4:15 PM, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>wrote:

Hello,

Sure it does. Look in QUSRWRK and you will find all the QDASOINIT and the
QZRCSRVS jobs. What activation group do they run in, default activation
group.

QDASOINIT are database server jobs. They aren't client programs written
in Java (what you said) they are server programs provided by IBM.

But I think I've figured out what you're referring to... The server
jobs are running in the default activation group, and your triggers are
written to run in *CALLER, so they also end up in the default activation
group.

You can't code a named activation group on the trigger itself in this
case, because that might cause a problem when the same trigger is
invoked by an ILE program in a "real" activation group that uses
commitment control... You want your trigger to run in the same
activation group when commitment control is active, because then any
records that the trigger updates/writes will be in the same commitment
scope.

So you pretty much have to code those triggers in *CALLER, which is
frustrating.

But any other routine called by the server job (besides a trigger) can
be coded with ACTGRP(SOMETHING) so you don't have to run in the DAG.

Your message makes it sound like this would be a frequent issue... but,
I don't know about you... but 99% of my work isn't trigger
programming... I do triggers from time to time, but they're not a major
part of my day. They're just an odd exception to the rule.

--
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.