× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. March 2005

Re: Making Triggers Resilient


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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.