RE: Commitment Control with SQL...

As a quick follow up... I was going through the journal entries and
noticed there is no 'SC' type entry, indicating that no Commit Cycle was
started? I thought this automatically started when the first record is
added, updated or deleted?

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Steven Harrison
Sent: Thursday, 6 January 2011 12:07 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Commitment Control with SQL...

Hi All,



I am using SQL stored procedures to perform the CRUD operations on my
database tables. These are called from an RPG service program. There are
also still legacy files involved so I start commitment control using the
STRCMTLCTL command in the main program before any files are opened or
SQL statements are performed. The SQL tables do not seem to be opening
under commitment control though? Changes made to the SQL database tables
are permanently stored regardless of whether a commit or rollback is
called. And during execution if I view the resources under commitment
control in the activation group the SQL tables do not appear? Does
anyone know if I'm missing something I should be aware of? I was under
the impression that if I started commitment control manually before any
SQL statements were performed then all transactions in the activation
group, regardless of whether native IO or SQL should run under the same
commitment definition?



Cheers,



Steve