|
On Aug 5, 2022, at 12:38 PM, Rich Loeber <rich@xxxxxxxxx> wrote:
I'm assuming so. The SQL from ACS runs successfully and produces the desired results.
I'm not seeing any errors on the system although it is hard to find out where to look for them.
Rich Loeber
Kisco Systems LLC
https://www.kisco.com
________________________________
On 8/5/2022 1:35 PM, Birgitta Hauser wrote:
Library List set correctly?
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
Modernization - Education - Consulting on IBM i
"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 losing them? Not training them
and keeping them!"
"Train people well enough so they can leave, treat them well enough so they
don't want to." (Richard Branson)
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx><mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rich
Loeber
Sent: Freitag, 5. August 2022 19:26
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx><mailto:midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Trigger Program Issue
I have a trigger program that runs on *READ events (I know, not
recommended). It works just fine from native applications, even SQL
statements executed from STRSQL. But, when I run the same SQL statement
from ACS, the trigger does not appear to be reacting.
I've looked at options when registering the trigger program and played with
them a bit, but no dice.
Any ideas why the trigger doesn't appear to run when an SQL statement is
issued through ACS?
Rich Loeber
Kisco Systems LLC
https://www.kisco.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto: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<mailto: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<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
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
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.