Objective: Replace an existing software instance

This topic explains when to select the Replace an existing software instance deployment objective.

Overview

Start of changeIf you select the Replace an existing software instance deployment objective, you will create a copy of the source software instance and simultaneously delete an existing software instance. When the deployment is complete, you will have two copies of the software instance – the original (source instance) and the new copy (target instance) – and the software instance you selected to be replaced will be deleted. If the source for the deployment is a portable software instance you will create a native software instance from the content of the portable software instance and simultaneously delete an existing portable software instance. ZONEINDEX subentries for the new target and distribution zones will be added to the global zone associated with the software instance to be replaced.End of change

Why would you select this objective?

Some reasons you might choose to create a copy of a software instance and simultaneously delete an existing software instance include the following:
  • You have a software instance that is no longer running in your installation.
  • You no longer need to fallback to that level of the software.
  • You want to reuse DASD.

The deciding factor is whether you want to replace or overwrite software that currently exists in your installation. If you want to replace existing software, you should select this objective. Otherwise, you should select the Create a new software instance objective.

For information about what will be included in the resulting global zone, see help topic Updates for SMPCSI and SMPPTS data sets.

Example

Figure 1 depicts a sysplex that has three running systems. The systems are running a total of four software instances (ZOSV2R2, ZOSV2R1, DB2V10R1, and CICSTSV5R1). The software instances reside on four volumes (A, B, C, and D). Software instance DB2V9R1 resides on volume C, but is not currently running on a system.

Figure 1. Example system and software instance configuration
Example system and software instance configuration.

Suppose you want to deploy DB2V11R1 from a test system (not depicted) to System 3. To do so, you would add a software instance to z/OSMF that represents the software you want to deploy. You can name that software instance DB2V11R1. Then, in the deployment checklist, you would select DB2V11R1 as the source software instance.

For the objective, you can select to create a new software instance or to replace an existing software instance. You would select to replace an existing software instance because you want to replace software instance DB2V9R1. This software instance is no longer your fallback instance and it is not running in your installation.

If not previously added, you would then add a software instance to z/OSMF that represents the software you want to replace. You can name that software instance DB2V9R1. Then, you would select it as the software instance to be replaced.

When the deployment is complete, software instance DB2V9R1 will be deleted from volume C and a copy of DB2V11R1 will be added to your installation.