×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Thu, Apr 9, 2026 at 11:31 AM Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
wrote:
They are potentially still in the same order doing work once the trigger
goes off.
<snip>
I wonder if a delay for a second after update would help.
I believe you're under the mistaken impression that the trigger is run "out
of band" or asynchronous to the RPG program.
This is not the case. When the RPG WRITE/UPDATE op-code is hit, and
control passes to Db2, control will not return to the RPG program until the
trigger is finished.
Like others, I suspect the program is a mismatch in isolation levels, which
shouldn't occur as an SQL Trigger normally inherits the isolation level of
the application.
With an RPG trigger, you have to have code to check the "Commit Lock Level"
field of the trigger buffer passed in.
It'd be helpful for you to confirm which table/record is being waited on.
Also, it'd be helpful to see the code for the trigger.
Charles
midrange.com
