SQL State 55019 code -7008 -- RPG400-L

× 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.

I recently had to recompile an SQLRPGLE program that contained an SQL Delete statement. The source code had not changed for 3 years, yet the delete portion of the program failed.

In debug, I could see the SQL code -7008 SQL State 55019.

We've never had journaling enabled for this (or any) file... And the program never contained the EXEC SQL SET COMMIT OPTION = *NONE statement.

I'm just curious as to why this program worked previously (for 3 years), then ceased to work after I recompiled it (for another reason)?
Could my RDi CRTSQLRPGI command have contained something that would implicitly set NO COMMIT? (about a year ago, I had to recreate my environment)
Or was this something with a PTF update?

This is the second time I've encountered this same issue in the past year. I'd like to know when and how it was introduced.

TIA,
Greg
[Logo]<https://www.totalbizfulfillment.com/> Greg Wilburn
Director of IT
301.895.3792 ext. 1231
301.895.3895 direct
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
1 Corporate Dr
Grantsville, MD 21536
www.totalbizfulfillment.com<http://www.totalbizfulfillment.com>

This mailing list archive is Copyright 1997-2024 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.