Fw: Change commitment control after compilation

<Jeff>
One of the major issues using commitment control is the release of record
locks (ALL) when issuing a COMMIT operation.
Take a legacy job where a pgm gets the company master at the start of
processing, processes all details, *then* updates the company master with
the totals. (not a good design, but I *have* seen this). Now, that pgm
calls other pgms, one of which issues a COMMIT at the end of the processing
for a control group. (the pgmr did not know about the first pgm). ALL
record locks released, then pgm 1 fails on update!
Perhaps using different AG's *might* fix this, but ideally, the entire
application would be in the same AG.
</Jeff>

... in this scenario without commitment controll the record lock would be released earlier, with the update and a second triy to update would fail anyway. Go back and think about your design. I'm rather unsure, wether your applications are rock solid!
Why don't you young guys not want to understand, that programmers life would be much easier using commitment controll???

D*B