|
midrange.com
Brad,
I should have been clearer. The trigger program will be call by a program with
a name like "QDBPUT". If you display "QDBPUT" it is an OPM program running in
the system state. The ILE manual says that the activation group for *CALLER is
derived by the calling program. In this case an OPM program. Is it ignored?
Does the invocation procedure run down the stack to the first non-system
program? If so why does QCMD not behave this way? Where is this behavior
documented?
Thanks for the help,
David Morris
>>> "Stone, Brad V (TC)" <bvstone@Taylorcorp.com> 01/26 3:31 PM >>>
What john is saying is that the trigger can be fired from a number of
places. And if the first program is running in the default activation
group, the trigger will be called in the default activation group. If
the same job runs a program in a different ag (lets say AGOE) that fires the
trigger, the trigger will be fired in the same ag (AGOE) as that program,
therefore having more than one instance of the program in memory.
Of course in the second case it wouldn't be called by an OPM.
Brad
----------
From: David Morris
Sent: Monday, January 26, 1998 4:02 PM
To: bvstone
Subject: Re: Triggers & AGs
Jon,
I am starting to get confused. How does the system determine the
activation group for programs and service programs that specify *CALLER? The
trigger is called by an OPM program. Why doesn't it run in the default
activation group when *CALLER is specified? Are system state programs ignored?
If they are why does QCMD not behave this way? What about QCMDEXC? It is
supposed to be ignored in the stack.
I haven't noticed any exceptions listed in any manual. If these are exceptions
where are they documented?
Thanks,
David Morris
>>> Jon Paris <paris@ca.ibm.com> 01/26 11:41 AM >>>
>> "I have a trigger program .... trigger pgm is also specified as
Activation Group (*Caller). Inside my trigger, I do a Return without setting on
LR and leaving my Sales & Marketing files open. Am I correct to assume that my
files remain open on subsequent firings of the trigger (during the life of the
job unless I reclaim the AG)." <<
You are correct - you should also be aware that by using *CALLER ou have opened
up the possibility that the trigger program can have multiple invocations
active at any one time (i.e. one in each AG - including the default - that it
gets called in). This may not be what you want.
Jon Paris - AS/400 AD Market Support - paris@ca.ibm.com
Phone: (416) 448-4019 - Fax: (416) 448-4414
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
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.
