RE: Commitment Control

Richard

It really depends on the application, however if you are using commitment
control you must plan ahead and write down all of the scenario's in which
you will commit and all of the scenarios in which you will roll back.

Things get really complicated, when you want to start reading back changes
that you have not yet committed on a different ODP.

My opinion (not advice) is to handle scenarios where commitment control
would be useful manually, ie. Your own flag on a record L=Live and
P=Pending. Or do the lot in a work file and process the updates in the end.

That way you can ensure your business logic is captured in any custom
rollback routines you use.

My advice however is to use commitment control if it is easy to implement
and you don't have code your business logic around it.

If you want to use commitment control in RPG it is a keyword against the F
file on a per file basis I think it is COMIT in RPG and COMMIT in RPGIV/ILE.

Prior to the file being opened the STRCMTCTL command must have been issued,
you can have different levels of commitment control based on activation
groups but you might get away with doing that for the time being.

Hope this is of some help

Neill



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Reeve
Sent: 25 January 2009 16:40
To: midrange-l@xxxxxxxxxxxx
Subject: Commitment Control

All,

I am being tasked with identifying weaknesses/inefficiencies in a
system that uses both COBOL and RPG (all flavors). I am noticing that
commitment control is being used intermittently and inconstantly. Oddly
enough, in my 20 years on the AS400 (or whatever the name of the day is) I
have never used commitment control. Although I understand the basic
concept,. I now need to work with it. Can any of you suggest a place to
start and/or explain to me in a nutshell how to use commitment control (and
maybe not to use) in COBOL and RPG programs.

Any help would be much appreciated.


Warmest Regards,

Richard Reeve