Re: Remote SQL Insert doesn't fire trigger

[Robert Rogerson <rogersonra@xxxxxxxxx>]

Art,

</snip>
I connected with IBM iACS run Sql scripts and found the QZDA* job that was
started. I tried to do a STRSRVJOB on that job but it says it's
already being debugged or traced. </snip>

In Run Sql Scripts go to Edit -> Preferences and make sure the the Incluse
debug messages in job log is not checked.

I think that should solve the already being debugged issue.

Rob


On Wed, Apr 7, 2021 at 5:20 PM Wyatt, Chris (BWPKG-ROM) via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> Any chance the library list on the ODBC definition does not include the
> library with the trigger program?
>
> Chris Wyatt
> ERP Business Analyst
> barrywehmiller
> BUILDING A BETTER WORLD THROUGH BUSINESS
>
> +1 (630) 759-6800 x 80163167
> chris.wyatt@xxxxxxxxxxxxxxxxxxxxxx
>
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Art
> Tostaine, Jr.
> Sent: Wednesday, April 7, 2021 3:59 PM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: Remote SQL Insert doesn't fire trigger
>
>
> [EXTERNAL E-MAIL]
>
>
>
>
> I have a client connecting via ODBC. When they do an INSERT INTO the
> trigger we added via ADDPTFTRG doesn't fire.  We created it as a *BEFORE
> *INSERT trigger.  I'm trying to debug the trigger program that's supposed
> to send an email to a customer.
>
> I connected with IBM iACS run Sql scripts and found the QZDA* job that was
> started. I tried to do a STRSRVJOB on that job but it says it's already
> being debugged or traced.
>
> If I do a STRSQL from green screen and do the same INSERT INTO the trigger
> fires.
>
> I tried adding a service entry point but that's not working on our new IBM
> i. I have to find out what's wrong with SEP's.
>
> I believe the trigger should fire for all database inserts. How can I
> prove that it is by debugging?
>
> Thanks, Art
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit:
> https://urldefense.com/v3/__https://lists.midrange.com/mailman/listinfo/midrange-l__;!!JWpd780U2qK2pF4!Hk0xCPN4GfQ55_hzgaNEWjqpWsz45L1JsVVRwxL-XXHMxJxx7K9htArN4lQulJ8w3RXDA612YEc8$
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
> https://urldefense.com/v3/__https://archive.midrange.com/midrange-l__;!!JWpd780U2qK2pF4!Hk0xCPN4GfQ55_hzgaNEWjqpWsz45L1JsVVRwxL-XXHMxJxx7K9htArN4lQulJ8w3RXDAyEvfB76$
> .
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link:
> https://urldefense.com/v3/__https://amazon.midrange.com__;!!JWpd780U2qK2pF4!Hk0xCPN4GfQ55_hzgaNEWjqpWsz45L1JsVVRwxL-XXHMxJxx7K9htArN4lQulJ8w3RXDA9jLNh7F$
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com