Ensure data integrity with commitment control

Commitment control lets you define and process a number of changes to database files in a single unit (transaction). It can ensure that complex application transactions are logically synchronized, even if the job or system ends. Two-phase commitment control ensures that committable resources, such as database files on multiple systems, remain synchronized.

You implement commitment control in your database by executing commit and rollback operations. Using SQL, you use the COMMIT and ROLLBACK statements.

• Transactions
  A transaction is a group of changes that appear as a single change, such as the transfer of funds from a savings account to a checking account.
• Benefits of using commitment control
  Recovering a complex application requires detailed application knowledge. Programs cannot be restarted. In this case, commitment control helps solve these problems.
• Usage notes: Commitment control
  The commit and rollback operations are available in several iSeries™ programming languages, including the RPG/400^®, COBOL/400^®, PL/I, SQL, and the i5/OS™ control language (CL). You can open logical files for output under commitment control when underlying physical files are journaled to different journals. Commitment control can also be used in a batch environment.