×
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.
Our shop is in the process of turning on journaling for production tables.
I've been out of a journaling environment for several years. I am
currently testing this on our dev box. I am surprised to find that
specifying *NONE for the commitment control parameter of RUNSQL command and
in the attributes of STRSQL does not cause an error or a rollback when I
update, insert, or delete records from a journaled table. I seem to recall
from the last shop in which I used journaling that, if we updated,
inserted, or deleted records from a journaled table and used COMMIT(*NONE),
the "changes" would last only as long as the job was active; the "changes"
would be rolled back as soon as the job ended. I am not seeing that
behavior here.
We have several CLLE programs that use RUNSQL COMMIT(*NONE), and I am
surprised to find that the updates made via these commands are retained
after the job has completed. (We have SQLRPGLE programs, but all use only
SELECT queries.) FWIW, we are at v7r1 with fairly recent PTFs and TRs.
What am I missing?
- Dan
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
