Triggered Embedded SQL Update Releasing Native Record Lock in Caller

Hi Everyone,

I am getting the message "Operation sequence for member xxxxx not valid".
That in itself is a little strange as I would have expected something
along the lines of "Update without a prior read".
No matter....the sequence of events that leads up to this...

RPG Program A has File X and File Z defined as Update Full
Program A reads File X
Program A Chains and Updates File Z
Trigger Program on File Z runs SQL Update on the same File X record
read prior by Program A
Program A attempts Update of File X record.....BOOM!

Looks like the SQL update being done in the trigger has released the
record that Program A had locked.
I've seen in the archive the same situation but the solution to move
some code around will be a problem due to some of my code being
executed in a trigger.

I was hoping someone might know of a way for the SQL update in the
trigger to not interfere with a native RPG record lock in the caller?

Any help appreciated....thank you,
- Steve