Re: Commitment Control with SQL... -- 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.

You have to specify that the files are under commitment control. For SQL, it's either in the compile command or in the SET OPTIONS command in the program itself. For traditional I/O, it's the COMMIT keyword on the file specification.

Joe

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

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.