True, they are.
The problem was that I needed this:
C/EXEC SQL SET OPTION commit=*none, closqlcsr=*endmod
I did not know. Still not sure exactly what the commit=*none does but it works.
<i>SET OPTION commit=*none</i>
That tells SQL that you aren’t using commitment control for this program. If you don’t use commitment control, then SQL is going to rollback any changes unless you tell it that commitment control shouldn’t be applied to these transactions. This will cause UPDATE, INSERT and DELETE statements to appear not to be working.
An alternative could be to COMMIT the changes.
I think Tom got it turned around
If SQL is using commitment control, then unless a commit is issued, the changes are rolled back.
OPTION commit=*none tells SQL that you don’t want to use commitment control and then the Changes are complete as the commands are issued.
In interactive Sql use F13 to check commit level — you probably have it set to none.