Re: Unexpected SQLSTATE returned from embedded SQL

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

BTW, Dieter - it is not Ops Nav anymore - I was speaking of the 
web-based IBM i Navigator - you won't be able to say "Oops" anymore and 
sound like an up-to-date person!

:)

On 7/16/2015 2:17 PM, D*B wrote:
> 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