Re: SQL commitment control and trigger programs

[Charles Wilt <charles.wilt@xxxxxxxxx>]

To expand upon Craig's answer...

If your trigger is an RPG trigger, then it should be looking at the
commitment control flag in the trigger buffer and opening it's files with
or without commitment control as required.

This usually entails checking for changes in the use of commitment control
and closing and re-opening the file(s) as needed.

Charles

On Fri, Oct 11, 2019 at 7:07 AM Craig Richards <craig@xxxxxxxxxxxxxxxx>
wrote:

> Daniel,
>
> I believe the only way to control this properly is to include the trigger
> processing in the same commit block.
>
> NB that although the trigger fires on changes to your file (obviously) it
> WILL NOT fire on changes made via a ROLLBK.
> The expectation being that you should have included everything (including
> the trigger processing) in the commit block.
>
> regards,
> Craig
> --
> This is the RPG programming on IBM i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/rpg400-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com