BRMS Parallel-Parallel versus Multiple-Library Parallel Concurrent Saves

Resolving The Problem

When to Use Parallel and Concurrent Saves

Due to i5/OS restrictions, you can gain the greatest benefit by designing a strategy that combines concurrent and parallel backup support. You should, if possible, use concurrent backups to reduce backup windows for objects which can only be saved using serial mode; such as system data, security data, configuration data, or folders and documents. Use parallel support when you want to reduce your backup window for large libraries and objects, large directories and files, large spooled files, or large numbers of these objects. In cases when saving large amounts of small data, parallel support is not the ideal choice and may negatively impact save performance.

If a control group without Save While Active is created within BRMS, an individual command of SAVLIB is created. If doing parallel saves, see the notes below

10 Z1 (Example Library)
20 Z2 (Example Library)
30 Z3 (Example Library)
40 Z4 (Example Library)

If a control group using Save While Active *LIB or *SYNCLIB is created within BRMS, the libraries are grouped into an individual command of SAVLIB, using *SYNCLIB is performed by default. If doing parallel saves, see the notes below.

10 Z1 (Example Library)
20 Z2 (Example Library)
30 Z3 (Example Library)
40 Z4 (Example Library)

New at R510: BRMS saves *ALLUSR and Generics are performed always as parallel-serial save, for which the objects can be restored without a media definition, using Native Restore commands.

Notes: