If you start journaling and commitment control on new programs it will not
affect your old programs.
In RPG (native I/O) you have to explicitly specify the key word COMMIT
within the F-Specs. As long as this key word is not included nothing
changes.
If your SQL Programs are compiled with COMMIT(*NONE) nothing will change,
... but when recompiling make sure they are again compiled with
COMMIT=*NONE.
The easiest way is to add a SET OPTION statement in each (embedded SQL
Source) with the commit key word (COMMIT=*NONE or
COMMIT=AnyOtherCommitLevel).
SET OPTION overrides the compile command, so you'll never have to remember
which program/module has to be compiled with Commitment Control and which
one not.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
Modernization ? Education ? Consulting on IBM i
Database and Software Architect
IBM Champion since 2020
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
"Train people well enough so they can leave, treat them well enough so they
don't want to. " (Richard Branson)
"Learning is experience ? everything else is only information!" (Albert
Einstein)
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Greg
Wilburn
Sent: Friday, 1 December 2023 22:18
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Journaling and Commitment Control
Our legacy ERP system does not have journaling enabled on any of their
database files. I'm currently working on a UI modernization project, and we
would like to use commitment control in the new applications we're creating
(over the ERP database).
The ERP system using RPG record level access for everything. However, I do
have some custom programs accessing/updating these files using SQL. Those
programs set the commit option to *none.
So my question is this... if we enable journaling on these files, will that
affect any of the existing programs with the commit option = *none?
I've been reviewing the 2019 Articles on IT Jungle, and it seems like we
should be OK.
https://www.itjungle.com/2019/06/19/guru-classic-looking-for-commitment-part
-1/
TIA,
Greg
[Logo]<
https://www.totalbizfulfillment.com/> Greg Wilburn
Director of IT
301.895.3792 ext. 1231
301.895.3895 direct
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
1 Corporate Dr
Grantsville, MD 21536
www.totalbizfulfillment.com<
http://www.totalbizfulfillment.com>
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a
message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
midrange.com
