In applications multiple steps have to be consolidated and executed as a unit (Transaction). That means either all steps or none of the steps must be performed. Example: an order has to be completely delivered or not at all.No problem if everything is okay, but what if there is suddenly not enough inventory for one position?Everything has to be reset … and this can become tricky, because multiple programs were executed, multiple rows in different tables were updated and may be even constraints or triggers were activated.The solution is Commitment Control. Even though Commitment Control is not new, it is only rarely used in (traditional) IBM i applications. … but it is essential for keeping data consistent, especially when using techniques such as referential integrities and triggers.… and it is even for traditional applications important.… so, it is time to start!