Upgrade in Place process

This chapter describes the Upgrade in Place, which upgrades an environment to a later version and/or maintenance level with close to zero downtime and minimal risk. This is accomplished by maintaining the same software library names and database files. The upgrade also provides a process for falling back to the previous software level, provided that the compatibility mode has not yet been changed.

Note:

The Upgrade in Place process cannot achieve absolute zero downtime, as it involves renaming IOA files. If you are upgrading Control-O or Control-M in a CTMPLEX configuration and you require absolute zero downtime, use the Express Upgrade process or the Full Upgrade process.
Using the Upgrade in Place process to upgrade from V9.0.00, V9.0.01, V9.0.02, V9.0.03, and V9.0.04 to V9.0.18 is possible only after the pre-requisite PTF PG03154 (WI10124) (and pre-requisites) is applied to the environment. After PTF PG03154 is applied, the Upgrade in Place process can only be used for upgrading to version 9.0.18, and later. That means if the pre-requisite PTF PG03154 is applied on V9.0.01 then it will be impossible to apply the V9.0.02, V9.0.03 and V9.0.04 maintenances from this point, and the only option is to upgrade to version 9.0.18.
If the environment has non-SMP/E managed clones, then, once the pre-requisite PTF PG03154 is applied to the base environment, it MUST be deployed to ALL non-SMP/E managed clones using the Change Deployment process, before upgrading the base environment to V9.0.18, or any later upgrade or maintenance level.
The Cloning and Change Deployment activities are blocked during the Upgrade in Place process, from when the Create Mirror Libraries step is completed and until after the Activate Upgrade step is completed.
After a successful Upgrade in Place, if you have multiple IOA environments at the same INCONTROL software level that are non-SMP/E- managed and have no ICE, you can perform a Multisystem Upgrade to upgrade those IOA environments.
IMPORTANT: The following considerations MUST be taken into account before the upgrade process begins:
- In Step 2.7 – Activate Upgrade all INCONTROL and Third Party Address Spaces (for example, CICS) that hold IOA data sets must be stopped in order to complete the step.
- Step 3.2 - Set Compatibility Mode enables changing the compatibility mode to the upgraded level. No INCONTROL address spaces may be active during this step in order to avoid working in mixed compatibility modes.
- If Control-M/Enterprise Manager is installed at your site and connected to this environment, consider upgrading it to the new level prior to performing Step 3.2 - Set Compatibility Mode. Otherwise, its compatibility mode must not be changed, and the latest features will not be available.