Rolling back UMS upgrade

Edit online

This section enables you to rollback to the Unified Management Server for z/OS version from which you upgraded, for instance, you can upgrade from UMS 1.2.0.8 to UMS 1.2.0.9 and rollback from UMS 1.2.0.9 to UMS 1.2.0.8.

Before you begin

Important: Any updates added after an upgrade will be lost when you roll back to the previous version.
Notes:
  • You can rollback an upgrade only for UMS 1.2.0.8 or later versions.
  • Make sure you can access the backup files that you made before an upgrade, as listed in the Installing a program temporary fix (PTF) section before you begin with the steps to upgrade to the new version (for example, UMS 1.2.0.9). 

Procedure

  1. To perform an upgrade, perform the following steps:
    1. Receive and apply PTF for the new version (for example, UMS 1.2.0.9).
    2. Optional: Take a backup of the current directories and data sets active on the new version (for example, UMS 1.2.0.9):
      • USS
        • workspace directory {components.izp.workspaceDirectory}
        Important: Retain the tags, extended attributes, and owner of the directory in your backup copy.

        For more information, refer to Taking backup and restoring the workspace directory.

      • MVS
        • Your copy of SIZPSAMP (for example, SAMPLIB)
        • UMS PARMLIB data set {components.izp.dataset.parmlib}
        • UMS generated JCLs {components.izp.dataset.jcllib}
        • UMS generated environmental info {components.izp.dataset.hlq}.ENVIRON
  2. To rollback an upgrade, perform the following steps:
    1. Restore and reject PTF for the new version (for example, UMS 1.2.0.9).
      Note: If the new version (for example, UMS 1.2.0.9) is the minimum version for any of your installed experiences (for example, Db2® Administration Foundation), then you need to restore and reject its PTF. For more information, refer to UMS PTF compatibility.
    2. Restore the directories and data sets of the old version (for example, UMS 1.2.0.8) to replace the directories and data sets that are active on the new version (for example, UMS 1.2.0.9).
      Notes:
      • Remove the workspace directory completely from the new version (for example, UMS 1.2.0.9) before restoring the workspace directory from the old version (for example, UMS 1.2.0.8) to avoid file corruption.
      • Ensure the tags, extended attributes, and owner stay consistent when moving and copying workspace directories.
    3. Run IZPIPLUG only when SIZPAUTH data sets are not used for cross-memory.
    4. Start Zowe.

Results

Unified Management Server upgrade is rolled back successfully.