Version 14.0 › CA Ideal › New Features › CA Mainframe Software Manager › Concurrent Releases

Concurrent Releases

You can install this release of CA Datacom and continue to use an older release in your production environment. If you plan to continue to run a previous release, consider the following points:

• When installing into an existing SMP/E environment, this installation deletes previous releases.
• If you acquired your product from tape or with Pax-Enhanced 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.

  Note: CA CSM installs into a new CSI by default.

• 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.

Parallel releases

Typically you should upgrade and test a development environment before upgrading your production environment. Because programs compiled with CA Ideal Version 14.0 will not run in a CA Ideal r2.2 or r11.0 environment, the programs updated in your Version 14.0 development environment can be re-compiled in batch with r2.2 or r11.0 to run in these environments until the production environment is upgraded to Version 14.0.

The following procedure is for running and testing programs in a development environment on a new release of CA Ideal and running the same programs in your current production environment that uses a different release of CA Ideal.

• Save your current release installed software load libraries for continued use by production. The ADRLIB, ADRPNL, and ADROUT data sets used by the current release development environment need to be saved for the batch procedure.
• Upgrade the development system to the new release. Plan for an interim period with the new release in development and the current release in production.
• Developers can continue development with the following warning: During the interim period, ongoing maintenance of production applications should not use any new release features, since these would not be recognized in the current release production environment. New applications that will be moved into production after the interim test period may use new release features. This should thoroughly test the new release code in the development environment.
• For any maintained programs that must be moved from development to production during the interim period, the following steps should be followed:
  1. Develop the changes to the application on the new release development system.
  2. Run a CA Ideal batch job to compile the application program(s) and mark status to production.

     This batch job must use the current release's load libraries and ADRLIB, ADRPNL, and ADROUT data sets. The new release development source, object, and panel VLS libraries should also be included.

  3. Run the CA Ideal object transport utility unload next or as the second step of the batch compile and mark. The new release load library for the object transport should be used for the unload process and the current release load library should be used for the loading of the application into the current release production environment.

     This loads the application into the current release production environment.

Note: If the QCODE value in the SCF options block was changed in the current release development environment to modify the enqueue names, the same value must be used for the new release development environment. When transporting, ensure that the correct load library is supplied so that the enqueue names match the system with which they are running.

CA IPC

The following information provides an overview of the Version 14.0 enhancements for the CA IPC product. For more information, see the Product Documentation Changes (PDCs), and PTFs available through CA Support online.