Commitment Control Scoping

ILE introduces two changes for commitment control:
  • Multiple, independent commitment definitions per job. Transactions can be committed and rolled back independently of each other. Before ILE, only a single commitment definition was allowed per job.
  • If changes are pending when an activation group ends normally, the system implicitly commits the changes. Before ILE, the system did not commit the changes.
Commitment control allows you to define and process changes to resources, such as database files or tables, as a single transaction. A transaction is a group of individual changes to objects on the system that should appear to the user as a single atomic change. Commitment control ensures that one of the following occurs on the system:
  • The entire group of individual changes occurs (a commit operation)
  • None of the individual changes occur (a rollback operation)
Various resources can be changed under commitment control using both OPM programs and ILE programs.

The Start Commitment Control (STRCMTCTL) command makes it possible for programs that run within a job to make changes under commitment control. When commitment control is started by using the STRCMTCTL command, the system creates a commitment definition. Each commitment definition is known only to the job that issued the STRCMTCTL command. The commitment definition contains information pertaining to the resources being changed under commitment control within that job. The commitment control information in the commitment definition is maintained by the system as the commitment resources change. The commitment definition is ended by using the End Commitment Control (ENDCMTCTL) command. For more information about commitment control, see the Backup and Recovery topic.