Re: Best way to determine which program is causing execution oftrigger program.

["Rory Hewitt" <roryhewitt@xxxxxxxxx>]

Vern,

Be careful with this assumption - if a user has used DFU to update the file,
then the application program which did the update *will* start with QDZ.
Also interactive SQL (via the STRSQL command), I'd suspect. Also possibly
Query Management Queries and maybe even Query.

In this article (
http://systeminetwork.com/article/add-temporary-trigger-utility-part-2), I
posted code to loop through the call stack until it finds the first program
above the relevant QDB* program which doesn't start with a Q, but I point
out this possible flaw.

Rory

On Wed, Oct 1, 2008 at 9:26 AM, <vhamberg@xxxxxxxxxxx> wrote:

> Stephen
>
> QDBPUT is the IBM program that is writing the data - and the one calling
> the trigger program. It is an IBM one - notice the Q at the start. Your
> caller is higher up the stack, and will NOT start with a Q. Unless you
> mistakenly name your stuff with Q as the first letter.   ;-)
>
> HTH
> Vern