Figure 1 shows the restore phase.

                  a. Promote Copy
┌────────────┐   ◄─────────────────
│            │
│    Prod    ├──────────────────────┐
│            │                      │
└──────┬─────┘                ┌─────┴──────┐
       │                      │            │
       │                      │   Backup   │
       │                      │            │
       │                      └────────────┘
┌──────┴─────┐               b. Promote Purge
│            │
│  Pre-Prod  │
│            │
└──────┬─────┘               c. Package details file updated
       │
       │
       │
┌──────┴─────┐
│            │
│    Test    │
│            │
└──────┬─────┘
       │
       /
       /

The restore is limited to non-editable types. The details of all members, both editable and non-editable, are recorded in the Package Details file.

After recovery of the non-editable members, the build-map of the related editable member is in an inconsistent state. The SCLM Administrator must now act to recover the source into a development group. From this group edit compare can be used to merge any desired changes from intermediate levels, and the member can be fixed and then built, tested, and promoted through the normal development process.

The ability of the members in the package to be backed out is dynamically assessed before any backout operation. This status is established by checking the statistics timestamp of the old and new members, and comparing them to the timestamps recorded in the package details file. Any differences invalidate the member for restoration.

When a restore is requested, the equivalent of normal promote processing is performed from the backup group, with both the Promote Copy and Purge phases.

During recovery, the member in the backup library is purged. This is because once a member has been restored, it cannot be restored again.

You can choose to back out either the whole package, or one or more individual members.

By default, member-level restore is deactivated. To activate this, add the parameter BKMBRLVL=Y to the FLMGROUP macro.

If a promote of a backout package completes successfully, and the same package name is used again in a package, it will overwrite the details of the previous package and members.

Cleanup of backed-up packages can be performed online or through a batch job. The cleanup procedure purges package details from the Package Details file, and deletes related members in the backup data sets that have not already been restored and purged.