Re: Trigger Program Issue

[Charles Wilt <charles.wilt@xxxxxxxxx>]

I'm with Birgitta.... library list issue.

Was the trigger program defined with a qualified name?

Does the trigger program do file access that's dependent on the *LIBL?

Pretty easy to check the LIBL of your ACS session...
SELECT * FROM QSYS2.LIBRARY_LIST_INFO;

Charles

On Fri, Aug 5, 2022 at 11:25 AM Rich Loeber <rich@xxxxxxxxx> wrote:

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