FB – Fallback

This section provides information about Fallback.

FB – Definition

The FB (Fallback) operation is valid at either the Production level or HOLD/controlled levels and is used in emergency situations to back out or reinstate one or more modules to a different version. Use the FB command as follows:

To fallback at PROD, a special Action code F task is created (explicitly by the user or implicitly by Code Pipeline). Any previous Production version may be fallen back to; it does not have to be the one immediately prior to the current version.
To fallback at a HOLD level, the user finds the backed up version they wish to reinstate and types the FB command beside it. If an active version already exists at the level, it will be backed up itself in the Code Pipeline Warehouse.

Important

A fallback cannot be performed on a closed container.

Fallback Process at PROD

Fallback can be performed at Production in a number of ways:

The user can create an Action F task to reinstate any previous Production version.
The user can enter FB against the current Production task, and Code Pipeline will automatically create an Action F task to reinstate the immediately previous version.
The user can request a Fallback of a Set that has Promoted modules into Production to reinstate the immediately previous versions of all modules (that is, to back out the entire Set).

Fallback at PROD With an Action F Task

Click Add on the Tool Bar or type A on the Command line for Task Add.
Type F for Fallback in the Special Action field of the Add Task screen, then press Enter to display the Application inventory list.
Use the Type and Name filters to find components in the Repository list as shown in the following figure.
Click on the plus signs to expand the list of possible versions to fall back to, then type S to select the specific module version that the Fallback operation is to recover to.
Press End to return to the Task List display.
From the Task List, type FB beside the entry being backed out (or highlight it with the Slash (/) operation and click Fallback on the Tool Bar.
Approve the Fallback request, if required.

Fallback at PROD with Action F Task

22.01                    ADD TASK TO ASSIGNMENT PLAY000022 Row     1 of     1
Command ===>                                                  Scroll ===> CSR
                                                                     More -->
   Show Deleted: N Checkout Path: DEV1 Action: F   Level Filter: PRD_

    Type     Name     Appl     SubAppl Status
    COB_____ TPROG07 PLAY____ PLAY____ ________
__ - COB      TPROG07 PLAY     PLAY
__ iVer=0003 P QA   -> PRD 2022-05-16 11:11:55 User=USER003
__ iVer=0002 P QA   -> PRD 2022-05-16 11:10:44 User=USER002
__ iVer=0001 TL PRD -> PRD 2022-05-09 13:58:46 User=USER001
------------------------------- Bottom of List -------------------------------

Fallback at PROD With FB Against the Current Production Task

Type FB for Fallback against the current Production Task from the Task List.
The Set Create screen is displayed, because the FB operation must run in a Set. Press Enter to continue.
Approve the Fallback request, if required.

Fallback at PROD With a Set

On the Modify/Approve Set screen (following figure), type F (or FALLBACK) in the Set Control field for a Set that has just promoted modules into Production. (Fallback from a Set is not currently supported at non-Production levels.)
Fallback at PROD with Set
              MODIFY/APPROVE SET S000000019                    Row 1 to 1 of 1
COMMAND ===>

Description ==> CHANGE CYCLE EXAMPLE 2
Owner       ==> USER003                     Release   ==>
Change Type ==> STANDARD                    Create    ==> 2022-05-16 11:13:07
Operation   ==> P                           Start     ==> 2022-05-16 11:13:00
Level       ==> QA                          Implement ==>
Build       ==> NO                          Activate ==>
                                             Queue     ==>
Lock Status ==> LOCKED                      Job/Proc ==>          / ISPWPSX
Aprv Status ==> NOT REQUIRED                Class     ==> A
Exec Status ==> COMPLETE

Set Control ==> F         (CLOSE/BROWSE/FALLBACK)
------------------------------ APPROVALS -------------------------------------

  Enter A to approve, D to deny or P to reset to pending and press Enter

CMD    APPROVER NUM REQD   CODE          USERID     DATE/TIME
        OPS        1     N    APPROVED      USER001    2022-05-16 11:23:00
******************************* Bottom of data ********************************
Press Enter to confirm the details for the new Fallback Set (following figure).
Confirm Fallback Set Details
                     FALLBACK SET CREATE
Command ===>

Confirm Details for new Fallback Set:

      Change Type     S
      Implement Date 2022-05-16   (YYYY-MM-DD)
      Implement Time 11:28:00     (HH:MM:SS - use 24 hour clock)
      Prefix          S___
      Description     CHANGE CYCLE EXAMPLE 2____________________________
      Owner           USER003_
      Process Option ________

Press Enter to continue or End to Terminate the Fallback Request.
Enter L (or LOCK) in the Set Control field to Lock the Set.
Approve the Fallback request, if required.

Fallback at HOLD

If a module has been promoted over the top of another version, and a backup exists in the Code Pipeline Warehouse, an FB operation against the Superseded Backup version will reinstate it.

Important

The Code Pipeline Administrator must specify that backups are to occur at each level in the change cycle where required. Otherwise, when a module is replaced at a level, it will be erased and displayed as Superseded Gone.

Example

Version 11 of a copy module has been promoted over the top of version 10 at the STG1 level. Version 10 is now backed up in the Code Pipeline Warehouse.

To see the inactive Superseded Backup versions, click Show/Hide in the Tool Bar, then click Show_Superseded. The screen shown in the following figure is displayed.

Fallback at HOLD Example

ASSIGNMENT        PLAY000022: CHANGE CYCLE EXAMPLE 2        Row     1 of     2
Command ===>                                                  Scroll ===> CSR
                                                                     More -->
+-----------------------------------------------------------------------------+
| <== Back Hide_Superseded Show_History Hide_Renamed                          |
+-----------------------------------------------------------------------------+
    Type     Name     Lev Op A User     Date MM DD Time Status
     COPY____ TCPYB03_ ____ _ _ ________ __________ _____ ____________________
__ + COPY     TCPYB03 STG1 P    USER003 2022-05-16 11:33 => Superseded Backup
__   COPY     TCPYB03 STG1 P    USER003 2022-05-16 12:33
------------------------------- Bottom of List -------------------------------

Expand the plus sign beside the backed up version to show who did it and in which assignment (following figure).

Expand to View Changes

ASSIGNMENT        PLAY000022: CHANGE CYCLE EXAMPLE 2        Row     1 of     2
Command ===>                                                  Scroll ===> CSR
                                                                     More -->
+-----------------------------------------------------------------------------+
| <== Back Hide_Superseded Hide_History Hide_Renamed                          |
+-----------------------------------------------------------------------------+
    Type     Name     Lev Op A User     Date MM DD Time Status
     COPY____ TCPYB03_ ____ __ _ ________ __________ _____ ____________________
__ - COPY     TCPYB03 STG1 P    USER003 2022-05-16 11:33 => Superseded Backup
  +--------------------------------------------------------------------------+
  |    I: Version replaced by user USER003 in assignment PLAY000022         |
  +--------------------------------------------------------------------------+
__   COPY     TCPYB03 STG1 P    USER003 2022-05-16 12:33
------------------------------- Bottom of List -------------------------------

Note that the Date and Time is displayed for the Last Operation performed on a Task. A version replacement event is not considered to be an Operation. To see when the replacement occurred, type H beside the task to see the full history. The version replacement event is represented by the characters -> and, in this example, it occurred at 11:33.

Full History

22.01                       EVENT HISTORY                   Row     1 of     3
Command ===>                                                  Scroll ===> CSR

   Appl: PLAY____ SubAppl: PLAY____ Type: COPY____ Name: TCPYB03_ Clas: ____

   Op A Lev Targ User     Date       Time Set        Release    Assignment
   __ _ ____ ____ ________ __________ _____ __________ __________ __________
  ->   STG1 STG1 USER003 2022-05-16 11:35
  C    DEV1 DEV1 USER003 2022-05-16 11:33
   P    DEV1 STG1 USER003 2022-05-16 11:34
------------------------------- Bottom of List -------------------------------

Fallback Operation

Reinstate the old version 10 instead of version 11 at STG1 as follows:

Type FB beside the backed up version 10. The Set Create screen (following figure) is displayed. (The FB operation must be performed in a set.)
Fallback at HOLD Operation
                           CREATE AND/OR DEFINE SET DETAILS
COMMAND ===>

Use existing Set ID: __________
or
Specify Details for new Set:
                                                 YYYY-MM-DD HH:MM:SS
    Operation      FB                  Start     2022-06-07 17:20:00
    Change Type    S                   Implement __________ ________
    Set Prefix     ____                Activate __________ ________
    Application    PLAY____
    SubAppl        PLAY____
    Description    CHANGE CYCLE EXAMPLE 2____________________________
    Owner          USER003_
    Release        __________
    Level          STG1
    Process Option ________

For new or existing Set:

    Lock Set     Y   (Y or N)
    Hold Set     N   (Y or N)

Press ENTER to continue or END to terminate/CANCEL
Press Enter. The FB operation is started as shown in the following figure.
Start Fallback Operation
ASSIGNMENT        PLAY000022: CHANGE CYCLE EXAMPLE 2        Row     1 of     2
Command ===>                                                  Scroll ===> CSR
                                                                     More -->
+-----------------------------------------------------------------------------+
| <== Back Hide_Superseded Show_History Hide_Renamed                          |
+-----------------------------------------------------------------------------+
    Type     Name     Lev Op A User     Date MM DD Time Status
     COPY____ TCPYB03_ ____ _ _ ________ __________ _____ ____________________
__ + COPY     TCPYB03 STG1 P    USER003 2022-05-16 11:33 SP: FB   Waiting
__   COPY     TCPYB03 STG1 P    USER003 2022-05-16 12:33
------------------------------- Bottom of List -------------------------------
When the Fallback is complete, FB is shown in the Last Op field for the newly reinstated version 10 (following figure). Version 11 is now backed up in the Code Pipeline Warehouse and is inactive at STG1.
FB in Last Op Field
ASSIGNMENT        PLAY000022: CHANGE CYCLE EXAMPLE 2        Row     1 of     2
Command ===>                                                  Scroll ===> CSR
                                                                     More -->
+-----------------------------------------------------------------------------+
| Select(/) Add Approve Close Join Reset Show/Hide Work ++/--                 |
+-----------------------------------------------------------------------------+
    Type     Name     Lev Op A User     Date MM DD Time Status
    COPY____ TCPYB03_ ____ __ _ ________ __________ _____ ____________________
__ + COPY     TCPYB03 STG1 FB   USER003 2022-05-16 11:48
__ + COPY     TCPYB03 STG1 P    USER003 2022-05-16 11:33 => Superseded Backup
------------------------------- Bottom of List -------------------------------
Type V beside either version to see all of the versions for the component. The Component Version List screen (following figure) is displayed. Version 5 has been reinstated and is active at STG1, while version 6 has been backed up and is now inactive.
Component Version List
22.01                   COMPONENT VERSION LIST              Row     1 of     3
Command ===>                                                  Scroll ===> CSR
                                                                     More -->
  Inactive: Y

   Appl: PLAY____ SubAppl: PLAY____ Type: COPY____ Name: TCPYB03_

   Lev iVer bVer rVer Op A User     Date MM DD Time Status
   ____ ____ ____ ____ __ _ ________ __________ _____ _________________________
__ PRD 1    0    0    TL   USER001 2022-05-09 13:15
__ STG1 5    1    1    FB   USER003 2022-05-16 11:48
__ STG1 6    5    1    P    USER003 2022-05-16 11:33 => Superseded Backup
------------------------------- Bottom of List -------------------------------