Re: Trigger / 5250 / .Net

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Where is the trigger program in relation to the table?  Where is the table
the trigger is writing to located?

Usually, issues like this are a sign that the trigger program expects the
*LIBL to be a certain way and the external app isn't setting it up.

Best practice is to have the trigger program in the same library as the
table.  Though IIRC, that's for SAVE/RESTORE mostly.  I think that even a
ADDPFTRG with *LIBL is just using the *LIBL to find the trigger.  When it
gets attached to the PF, the program is qualified.  Double check with
DSPFD TYPE(*TRG).

Probably the trigger can't find the file to write to.  May want to use
EXTNAME(var) to open the file with a fully qualified name.


HTH,
Charles

On Thu, Jun 6, 2024 at 4:20 PM Kirk Yates <kirk.yates@xxxxxxx> wrote:

> I have a trigger program that writes a single id field to another file if
> an insert or update is made.  Running a simple sql update statement from a
> 5250 strsql interface and everything works great.
>
> If the same sql command is run from a .net interface, the data in the file
> is updated, but the trigger program doesn't catch that a change was made.
>
> Library is defined as TEST if that makes any difference.  Looked at the
> data in the file and the record was updated.
>
> What else should I be checking?
>
> Thank you for your help.
>
> --
> Kirk Yates
>
> --
> 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.