Re: Change commitment control after compilation

@Henrik:
nothing to chew!

A user makes some input to some sort of screen (might be 5250, might be Windows, or x-windows, might be a JSP or whatever). At some time it's finished and the user confirms, that he want's this written to the database. In a well normalized database this will need some inserts and updates to some tables (mostly n operations to m tables) - this is called a transaction!
This should be atomar in the sense, that all this is brought to the database, or nothing and the user get's some information: all is done, or the transaction failed. The easiest and most straight forwarded method to accomplish this is the transaction support of the database: this is well known as Commitment Controll and as long as nothing is wrong with this, I will use and recommend to use Commitment controll as the easiest solution for a common problem!!!!

There might be problems (of course they are) you can't solve with commitment controll, one of these are long lasting transactions, e.g. flight reservation software, or giving an user exclusive access for a known segment of the database, but even in these cases, you will have the need to make an update operation of m records to n tables atomar and again Commitment controll will be the easiest solution for most database systems (db2/400) included.

D*B