Application Migration Considerations › Application Migration Considerations › Replacing Online Applications › Enqueuing Considerations

Enqueuing Considerations

• An enqueue remains active against a program in VLS format from the time the program is first called until the RUN of the application that accessed the program terminates.
• The object transport utility LOAD obtains exclusive enqueues against the portions of the programs loaded into the VLS libraries.
• The DISABLE RUN command forces users off an active application only after the transaction boundary following the disable time. This means some programs could still remain enqueued even after the disable time arrives. Review Disabling and Enabling an Active Online Application earlier in this chapter.
• Another CICS region running VLS programs and panels of the same name in physically different VLS libraries can lead to failure of the object transport utility ADXSSP24 'PROD' program in use. Please try later. This happens when the SC00OPTS QCODE parameters in each region are not properly set.
• If you replace active programs and panels without disabling the application first, the results can be unpredictable. Under most circumstances, you receive IDADOMLD07 - Global storage DT discrepancy for PGM pgm-name VER ver found, however, other messages are possible.

It is also possible that the transport or mark status fails if a physically different program of the exact same name is running in another region and both regions have the same QCODE setting. For more information about enqueuing considerations for multiple regions, see the “Establishing Multiple Environments” chapter.

Upgrading from an Earlier Version

CA Ideal is "upwardly compatible" meaning that a program that is compiled with an earlier release can still run in the most current release of CA Ideal. However, programs compiled with a higher release of CA Ideal cannot run in a CA Ideal environment at lower release. Therefore, the programs that are 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.

Note: Always upgrade and test a development environment before upgrading your production environment.

Use the following procedure 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. Save the ADRLIB, ADRPNL, and ADROUT data sets used by the current release development environment 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. These features would not be recognized in the current release production environment. New applications that are moved into production after the interim test period can 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 load libraries of the current release and ADRLIB, ADRPNL, and ADROUT data sets. Ensure that the new release development source, object, and panel VLS libraries are 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 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.