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


  1.  Home
  2. RPG400-L
  3. December 2015

Re: Actually using commitment control and QTEMP

Hi Darren,

Use set option COMMIT = *NC or *NONE, and then for each individual SQL
statement that you wish to participate in a commitment control unit of
work, add the WITH clause with a value other than NC or NONE.

Mike


date: Thu, 17 Dec 2015 15:00:24 -0500
from: darren@xxxxxxxxx
subject: Actually using commitment control and QTEMP

I've actually found a use for turning on commitment control in my SQLRPGLE
program. So I did that easy enough with:
exec sql set option COMMIT=*CHG;

Do I have to turn off commitment control to work with QTEMP? If so, how do
I do that? I'd like it on for when my program updates the production
files its designed to work with.


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