Performance considerations for save-while-active

While you can run save-while-active operations any time, save-while-active operations will affect the performance of other applications you are running.

You should run save-while active operations during times of low system activity. A few interactive jobs or batch jobs that are primarily read-only, are examples of activities that allow better system performance during the save-while-active operation.

In general, the system performs checkpoint processing faster for a small number of larger objects than for a large number of smaller objects.

You should not use the save-while-active function when the system 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 system's performance and storage.