Re: AW: Trigger weirdness with L-Date fields

The activation group is based on how the program is complied. If you give it
a activation group it will run in that activation group. If you give it
*CALLER it will be based on where the caller is running. If it is a client
server job running in QZDASOINIT job that will be the default activation
group. If running in a regular job it will be whatever they are running in.
. If created with the default that will be default activation group.

On Wed, Aug 24, 2011 at 12:54 PM, Charles Wilt <charles.wilt@xxxxxxxxx>wrote:

Exactly...I've never really bothered to figure out which activation
group a trigger runs in...my guess is it's one of the Qxxx ones...but
I suppose could be one of the *DFTACTGRP...

Charles

On Wed, Aug 24, 2011 at 2:41 PM, <rob@xxxxxxxxx> wrote:

More of an RCLACTGRP issue sort of thing then? But, since you are doing
ACTGRP(*CALLER)...
[ DSPJOB, option 18]

it becomes a bit tough to reclaim the first one of these, eh?
-------Activation Group--------
Name Number
*DFTACTGRP 0000000000000001
*DFTACTGRP 0000000000000002
QLGLOCAL 0000000000000011
QSQCLI 0000000000000012
QTESAGRP 0000000000000056
QTESGUI 0000000000000058
QTESTIFC 0000000000000057

Hence the recommendation to just sign off/on again?



Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 08/24/2011 02:35 PM
Subject: Re: AW: Trigger weirdness with L-Date fields
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Assuming you're doing an RPGIV program...
And assuming you're using the recommended values (for trigger
programs) of DFTACTGRP(*NO) ACTGRP(*CALLER)...

Then RCLRSC is meaningless...

You might be able to figure out the activation group being used...but
it's probably easier to simply sign off and back on.

HTH,
CHarles


On Wed, Aug 24, 2011 at 12:56 PM, James Lampert
<jamesl@xxxxxxxxxxxxxxxxx> wrote:

I could have sworn that I did a RCLRSC every time I updated the trigger
program yesterday, but then again, I've seen RCLRSC fail before.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.