RE: Unexpected SQLSTATE returned from embedded SQL

Dieter, thanks again for the follow-up, it helps me understand this issue a little better.
No insert or update related to this particular file

Unfortunately, the "bug" has just bitten us again and I'm working on a HACK of a fix:
Adding an extra check based on CHAIN when sqlstate 02000 occurs . . .

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of D*B
Sent: Thursday, July 16, 2015 1:17 PM
To: RPG programming on the IBM i / System i
Subject: RE: Unexpected SQLSTATE returned from embedded SQL

Gary,

if you don't use commit, as you stated, then record locks could not cause sqlstate 200 (this could only happen with isolation read committed).
The journals won't show up selected records, only update, delete and insert operations are shown in the journal. If you have the id for a sqlstate 200 condition, you could have a look to the journal, if an insert or an update resulting in your search value has happened after the sqlstate 200 condition. For this you would need the record buffer restructered combined with the journal codes and times (if an UDT or oops nerv could do this, I dön't know, I've had my own tool years before oops nerv or udts knew of journals...

DIeter