Eliminating your save-outage time

 

Use the save-while-active function to eliminate your save-outage time.

Use the following general procedures to eliminate your save-outage time for particular save operations. These save-while-active procedures do not require any applications to be ended to perform the save operation. However, these save-while-active methods do require additional recovery procedures.

IBM^® highly recommends that you use these procedures only for objects you are protecting with journaling or commitment control.

• Recommended procedure for eliminating save-outage time
  This procedure outlines how you can use the save-while-active function to eliminate save-outage time. You will not end the application jobs.

• Monitoring your save-while-active operation
  Do the following procedures as they apply if you are using the save-while-active function to eliminate your save-outage time.

• Considerations for recovery procedures after eliminating save-outage time
  This topic discusses some of the considerations for save-while-active recovery procedures. In general, the system cannot preserve application boundaries because they are defined by the application. It is left up to you to provide for any of the appropriate recovery procedures when you use the save-while-active function to eliminate your save-outage time.

• Recommended recovery procedures after eliminating save-outage time
  If you perform save-while-active operations to eliminate save outage time and you specified *NOCMTBDY for the SAVACTWAIT pending record changes value, you can be left with objects that are saved with partial transactions.

• Example: Eliminating save-outage time for libraries
  This example shows a typical use of the save-while-active function to eliminate a save-outage time. Your exact use of the function may differ, based on your specific application requirements.

• Example: Saving objects with partial transactions
  This example shows a typical use of the save-while-active function to eliminate save-outage time by not waiting for commitment boundaries. Your exact use of the function may differ, based on your specific application requirements.

• Example: Eliminate save-outage time for a directory
  This example shows a typical use of the save-while-active function to eliminate save-outage time in a directory. Your exact use of the function may differ, based on your specific application requirements.

• Example: Restoring libraries after eliminating save-outage time
  This example shows a typical restore procedure after you eliminate save-outage time in a library. Your exact use of the function may differ, based on your specific application requirements.

• Example: Restoring objects with partial transactions
  If you perform save-while-active operations that can result in objects that are saved with partial transactions, it is recommended that you use Backup, Recovery, and Media Services (BRMS).

• Example: Restoring a directory after eliminating save-outage time
  This example shows a typical restore procedure after you eliminate save-outage time in a directory. Your exact use of the function may differ, based on your specific application requirements.

 

Parent topic:

Saving your system while it is active

Related concepts
Eliminating save-outage time: Overview Considerations for recovery procedures after eliminating save-outage time