This article might help you to understand about the online backup without commit boundary, which will be available from i5/OS V5R3Mo; it can be easily used for SAP systems. SAP has also mentioned the new parameter NOCMTBDY that will help you for the online backup and which will later help you to save the objects for the system with the help of SAP Application Server ABAP, SAP Application Server JAVA, or SAP Master Data Management (SAP MDM).
Initial with i5/OS V5R3M0 the option also exists of backing up an online database as soon as the accompanying work procedures are not at a COMMIT boundary. In the same way as for older releases, the online backup is nominated by the use of the parameter SAVACT (*SYNCLIB) in the backup command (SAVLIB or SAVOBJ). The parameter SAVACTWAIT (wait time) has three mechanisms from V5R3M0 onward.
- You have to wait for some time till the objects locks. Uncertainty a backup is occupied while the system is dynamic, formerly the save operation will effort to obtain a "Shared read no update" (*SHRNUP) lock for the mainstream of objects. If it does not prosper inside the time given here, the backup will terminate. Throughout usual SAP system operation, there should be no locks on database objects which would prevent a backup being taken.
- Wait time for pending record changes. If this value is set to *NOCMTBDY, then the backup will not wait for exposed transactions to spread a COMMIT boundary. This comprises the SQL statements INSERT, UPDATE and DELETE.
- The wait time for other pending changes. This boundary comprises variations made by DDL statements, for example, ALTER TABLE. Transactions which use SQL statements of this type must reach a COMMIT boundary before a backup can be executed.
Hope this article will help you have an idea about Online backup as of V5R3M0