Re: Question on SQL After Trigger Locking a Record

I imagine RPGII doesn't involve transaction boundaries etc.
when you display the locks what do you see?
worth trying COMMIT *NONE or similar in the body with SET TRANSACTION?

ciao






On Thursday, April 9, 2026 at 06:56:31 PM GMT+2, Richard Schoen <richard@xxxxxxxxxxxxxxxxx> wrote:





OK, today I have a question about an SQL trigger on a DB2 file.

Customer has a table they want to put a trigger on. That all works.

And the trigger simply does an insert to another table.

However as soon as they added his trigger, the end-user programs (Old RPGII interactive rpg programs) that use the table in question experienced lock-wait conditions.

They are potentially still in the same order doing work once the trigger goes off.

When a trigger goes off I thought it just received an image of the record (similar to a journal entry).

This RPGII program does multiple reads, but it also appears to release the records after each read.

Anyone have thoughts on why a trigger could cause the downstream programs to suddenly lock up waiting on records once a trigger is added.

Input appreciated.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>