Backing Out Source Promotions

Copyright © Cloud Software Group, Inc. All Rights Reserved

Chapter 7 Promotion Backouts : Backing Out Source Promotions

Backing Out Source Promotions

If you want to undo application changes introduced by a change request, the backout function restores the associated objects in the source system to their state before the promotion.

If the change request contains a rule to execute, the backout function does not reverse the resulting effects. Depending on the effect of your rule to execute, if any, you must ensure that you have a backup of the MetaStor or of the appropriate tables, and then restore the affected data from the backup made prior to promotion of the change request.

User Access

Before you back out a promotion, ensure that users who can access objects in the affected change requests are logged out of the system. To maintain integrity in your system, all users should be logged out of the system. You should also prevent other users from logging in by selecting the option Suspend User Access from the Change Request Management menu.

Procedure

To back out the affected change request, select the option Manage Promoted Requests from the Change Request Management menu and complete the following steps:

1.

Type B in the line command field beside the change request you want to back out.

2.

Press Enter.

Confirm with PF22.

3.

Type the name of the backout library.

The default library name is PR#nnnn, where nnnn is the change request number. You can restore the rules directly to the requestor’s library by specifying the library name in this field. All available promotion rights are also obtained for that library. For non-rule objects with rights set to User, the promotion rights defer back to the developer who created the original change. If promotion rights are set to Group, the rights for non-rule objects revert back to the originating group library.

4.

Type the TDS segment to which the objects should be restored.

If you enter an invalid segment number, the Promotion system attempts to restore objects on the segment from which they were unloaded. If this fails, objects are restored on segment 0.

5.

Press Enter.

Confirm with PF22.

6.

Restore user access.

After backing out the affected change request, restore access by selecting the Restore User Access option from the Change Request Management menu.

Backing Out Multiple Change Requests

Start with the most recent change request and work backwards. Check the message log for discrepancies between the change request you are backing out and others submitted since then.