Re: determining pgm that tripped the trigger?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2011-03-09 12:38, David Gibbs wrote:

James Lampert wrote:

In a trigger program, what's the easiest way to determine what
program tripped the trigger?

Since the trigger is invoked in the current job, you might be able to send a message up the message queue to find what program caused the program to invoke.

david

For a batch job, once a suitable problem instance is identified, I
usually build a test environment containing it, then create a test
trigger from the production version with a little code to filter on the
values I'm looking for, something like this:

If ORIGINAL_CUSTOMER = 9999 or NEW_CUSTOMER = 9999
XXX = 1;
EndIf;

Then I put a breakpoint on the assignment, run the job, and wait until
it breaks. Looking at the program stack tells me exactly where the
problem came from. I can even add the offending program to the debug and
browse the variables in it for more information. Works pretty well in
situations where the problem could come from a lot of different programs.

hth

- --
Pete Hall
pete@xxxxxxxxxxxxxx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk14K2IACgkQXczQcKdXKg6NnQCeIxVpd3uzJ8303RuRJxTgrqYJ
AKwAoICKoEwqT0TI+hF0RdTEwh1Au/a2
=eVXh
-----END PGP SIGNATURE-----