Am 05.01.2022 um 16:37 schrieb Robert Wenzel <robert.wenzel@xxxxxxxxx>:

10. The array is block-inserted to the work file for the specific number of
array entries (based on the number of elements/rows populated to the array)
(SQLCode = -803).

Can anyone tell me why DB2 does not commit those rows between the SQL
INSERT and the next OPEN cursor statement?

Have you checked you exception join? And does the exception join really avoid any duplicate key entries?

I would try to re-write the portion of the program with a loop and then debug on which insert it fails - if it wouldn't fail, then you really may have a bug in the OS or SQL/PC, but this is not often the case - more often their is a small bug in the join or program logic.

FYI - the SQLRPGLE program is compiled with COMMIT (*NONE).

With COMMIT(*NONE) there shouldn't be any delay between the INSERT and the time when the record(s) show(s) up in any later SELECT.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.