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



Hi,

a trigger program is activated by the database manager.
The database manager calls either the program QDBPUT (for input triggers) or
QDBUDR (for update insert delete and read triggers).
You simply have to go back in the call stack and determine the program that
is located before the trigger program.
You may use the API QWVRCSTK to retrieve the call stack or send a message
to the program previous to QDBPUT or QDBUDR and determine the sender

Here is an article (it is written in German, but I think the examples are
understandable)
http://www.sss-software.de/inn/enews/iNN-eNews0412.html#Tekki3

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and loosing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von James Lampert
Gesendet: Thursday, 04. September 2008 01:07
An: Midrange Systems Technical Discussion
Betreff: Trigger question

I may have asked this before, but . . .

Is there an easy way, in a trigger program, to find out what program
initiated the change that tripped the trigger?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.