Modifying Function Options › Identifying Standard Function Options › Using Commitment Control

Using Commitment Control

This option specifies whether the program that implements the function runs under i OS Commitment Control and, if so, whether it contains the main commit points. i OS commitment control provides a means of automatically grouping a number of database updates into a single transaction for the purposes of recovery: either all or none of the updates take place.

If you link together several functions as one transaction group, CA 2E determines where the commit points are located.

• If M (*MASTER) is specified, the program runs under commitment control. This program is the controlling program and contains the commit points. The program ensures that commitment is active by calling a CA 2E supplied program, Y2BGCTL. It also includes the appropriate commit points.
• If S (*SLAVE) is specified, the program runs under commitment control. No automatic start or commit points are included. You can add commit points by using the COMMIT built-in function. Commit operations can be performed by a calling program (typically *MASTER) function.
• If N (*NONE) is specified the program does not run under commit control.

Note: Any physical (PHY) file updated by programs running under commitment control must be journaled.

For more information about commitment control and journaling files, see the i OS Programmers Guide.