Re: Making Triggers Resilient

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

Hi Mark,

> I was under the impression that triggers run in the caller's job.  That 
> means that it will "inherit" the *LIBL and other attributes.  Following 
> that logic, wouldn't *CALLER run in the caller's (user job) *ACTGRP, not 
> the DB's?

It would appear (based on Barbara's post) that you're correct, it does 
inherit the activation group of the program that made the database call.

I don't follow your logic. Activation groups aren't a global attribute of 
a job. A job can contain many, many AG's, so it's not something that can 
be inherited as part of the job.  Instead, *CALLER means that the AG is 
inherited from the program that calls it.

But, apparently triggers are the exception to that rule -- something that 
I didn't know until now. Instead of inheriting the activation group of 
the database manager, the system activates it in the AG of the program 
that made the database call.

I learned something new today.