Concurrent Releases

This article explains how to manage concurrent releases.
dm18
This article explains how to manage concurrent releases.
You can install this release of your product and continue to use an older release in another SMP/E environment. If you plan to continue to run a previous release, consider the following points:
  • When you install the product into an existing SMP/E environment, this installation deletes previous releases in that environment.
  • If you acquired your product with Pax ESD, select different target and distribution zones for your new release from where your current release is installed. The new zones use different libraries than your current release.
    CSM
    installs a product into a new SMP/E environment by default. You can select an existing SMP/E environment from your working set. For more information, see the online help that is included in
    CSM
    .
  • Define DDDEF entries in your new zones to point SMP/E to the proper libraries for installation. Ensure that they point to the new release libraries.
 We recommend that you install in separate environments.
Compatibility with Previous Releases
To keep your previous product versions, you can install the new versions on the same subsystem as the previous version.
To ensure that you can recover data from the previous version when creating JCL for object comparison, set the Recovery field to Y and specify a data set in the Recovery DSN field when comparing
Db2
objects. See Compare
Db2
Objects in the
Db2
Catalog Customization Tasks during post-install processing.