Commitment control with save-while-active

This information applies if you are using commitment control and save-while-active to eliminate your save-outage time. This information applies only if you are not specifiying *NOCMTBDY for handling pending record changes on the SAVACTWAIT parameter.

If an object receives updates under commitment control during the checkpoint processing phase of a save-while-active operation, the server saves the object at a commitment boundary. The server saves all objects that reach a checkpoint together at the same common commitment boundary.

During the save preprocessing phase of a save-while-active request, the server ensures that it saves the objects commitment boundary as follows:

Related concepts
Performance considerations for save-while-active
Related tasks
Checkpoint processing with save-while-active

Commitment control with save-while-active and *NOCOMTBDY

This information applies if you are using commitment control and save-while-active to eliminate your save-outage time. This information applies only if you specified *NOCMTBDY for handling pending record changes on the SAVACTWAIT parameter.