Save-while-active restrictions

The following restrictions apply to all of the commands which provide the save-while-active function.

• The save-while-active function is only available on the commands listed in Save-while-active function.
• You cannot use the save-while-active function in the following situations:
  • When all subsystems have ended. If you have ended all subsystems, the save operation is the only user job that is active. It must finish before you can restart your subsystems and applications. The following save operations require that you end all subsystems. Therefore, you cannot use the save-while-active function with these operations:
    • Saving the system library
    • Saving all libraries
    • Saving the entire system
  • When freeing or deleting storage during a save operation. If specifying STG(*FREE) or STG(*DELETE) on a save command, or CHKFORMRK(*YES) on the SAVDLO command, you cannot use the save-while-active function.
• You should not use the save-while-active function when the server is very busy or when there is very little disk storage available. Before you save large amounts of data (such as all user libraries), you should initially use the save-while-active function on a limited amount of data. Using the save-while-active feature on a limited amount of data will help you determine its impact on your server's performance and storage.
• You should not load, apply, or remove program temporary fixes (PTF)s when running a save-while-active operation.
• You must issue separate save commands to use the save-while-active function for objects in libraries, document library objects, and objects in directories. If you need to synchronize objects you are saving with different commands, first end your applications until all of the objects have reached a checkpoint.
  • If you have only one media device, each command must finish before the next can start. If you use the save-while-active function to reduce your save-outage time, save folders and directories first. Save libraries last. Saving the objects in this order will probably provide the greatest reduction in the save-outage time.
  • If you have multiple media devices, and you use the save-while-active function to reduce your save-outage time, save libraries, folders, and directories concurrently. This will probably provide the greatest reduction in you save-outage time.
• You cannot save objects that you create after the save operation begins.
• You cannot save objects that other jobs are using during checkpoint processing.
• Do not use System Service Tools (SST) functions for objects you are currently saving by a save-while-active operation.