you should not use Commitment Scope *JOB.
I meant Commitment Scope *ACTGRP
Most companies never cared about Activation Groups ... and then at point X they decide to run different programs in different activation groups and suddenly commit and rollback does no longer work correctly and nobody knows why.
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: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Birgitta Hauser
Sent: Friday, 26 July 2024 13:54
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: is this the correct understanding for commitment control running in ILE?
Jay,
Dieter Bender (D*B) says it ... and Dieter always lives in a "perfect world"!
As I said it before as long as you do not have a 100% proper and well-designed Activation Group Design (and most companies don't have it!!!) and all commits and rollbacks only occur in a single Activation Group, you should not use Commitment Scope *JOB.
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: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jay Vaughn
Sent: Friday, 26 July 2024 13:05
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: is this the correct understanding for commitment control running in ILE?
DsternB,
Thank you very much. You addressed my points exactly as I was hoping.
Interesting Birgitta says always use *Job and you say never to.
Well in my case these are api pgms in a cgi job so I think actgrp commit scope is the way to go!!
Im curious about your point below… can you elaborate a bit more?…
*********************
<D*B>Only SQL starts commit by automatic - if the first update/insert is made by RLA it will fail</D*B>
*********************
Oh and as to your point about the implicit commit… as I was playing with this yesterday, every time the top level pgm that started the cc running in *new ended, the commit would happen without a commit being coded. If I signed off and back on the record was still there.
So I do believe what I laid out is an accurate assessment of how cc behaves on an api pgm in a cgi job environment.
Thanks!!
Jay
On Jul 26, 2024, at 3:03 AM, Dsternb <dieter.bender@xxxxxxxxxxxx> wrote:
*********************
<D*B>Only SQL starts commit by automatic - if the first update/insert
is made by RLA it will fail</D*B>
*********************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
midrange.com
