
The Save-While-Active function lets you continue using applications while they are being backed up.
As of the operating system release IBM i5/OS V5R3M0, the Save-While-Active function is available in two different forms:
Saving database objects at a transaction boundary
This option requires that all work processes are at a transaction boundary so that the backup can start. This function is available in all releases of the operating system. When restoring the backup, it is guaranteed to be in a consistent state. However, very long running transactions might prevent some work processes from reaching a transaction boundary within the time frame that is allowed for the backup. The backup might fail.
Saving database objects with partial transactions
This option is new starting with IBM i5/OS V5R3M0. You can use it to save objects even when the work processes are not at a transaction boundary. Tables that are backed up using this option can contain data that was part of uncommitted work, so you have to apply journal changes after restoring the backup to complete or roll back incomplete transactions and ensure database consistency. Note that the incomplete transactions can only contain uncommitted DML statements (INSERT, UPDATE, DELETE) to allow a backup. You must commit or roll back transactions that contain DDL statements such as ALTER TABLE before you perform the backup. You must avoid running an online backup while transports containing ABAP dictionary changes are being imported into the system
To execute the Save-While-Active function, specify the parameter SAVACT(*SYNCLIB) for save commands SAVLIB and SAVOBJ. If you are saving objects at a transaction boundary, specify the wait time, for example one hour, in parameter SAVACTWAIT(3600) and leave the rest default. If you are saving objects with partial transaction, specify the Pending record changes field in the parameter, for example SAVACTWAIT(3600 *NOCMTBDY *LOCKWAIT). When using this field, you cannot save to a target release prior to V5R3M0.
For more information about the Save-While-Active function, see the IBM Information Center.