Running Parallel Versions/Releases When Upgrading CA Ideal

Document ID : KB000029815
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction:

This Knowledge Document will describe what you need to do if you need to run parallel releases of CA Ideal.

 

Background:

CA Ideal is “upwardly compatible” meaning that a program compiled with CA Ideal 1.0 will still RUN in CA Ideal Version 15.0, but programs compiled with Version 15.0 cannot be RUN in 14.0.

 

Typically you should upgrade and test a development environment before upgrading your production environment. Because programs compiled with a higher release of CA Ideal will not run in a CA Ideal environment at lower release, the programs updated in your newly upgraded  development environment can be re-compiled in batch with the old, lower version of CA Ideal to run in these environments until the production environment is upgraded.

 

Environment:

z/OS

 

Instructions:

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 (SC00OPTS) was changed in the current release development environment, 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.