Version 14.0 › CA Datacom Tools Products › New Features and Enhancements › Migration from Version 12.0 to Version 14.0

Migration from Version 12.0 to Version 14.0

The following is pertinent in multiple MUF applications.

• A MUF at Version 14.0 must execute with libraries that contain Version 14.0 code exclusively.
• A DBUTLTY step at Version 14.0 must execute with libraries that contain Version 14.0 code exclusively.

A batch user program that communicates to a single MUF should execute with libraries that contain that MUF’s version, but the situation is more complicated when a batch user program communicates to multiple MUFs. Because each MUF is likely to be migrated from Version 12.0 to Version 14.0 at different times, batch jobs that communicate with multiple MUFs cannot execute with the libraries for all MUF versions. Therefore, to allow an easier migration, the CA Datacom/DB interface module set that executes in the user address space supports user applications at both Version 14.0 and Version 12.0. This allows batch user programs that execute with multiple or single MUFs to use this module set at Version 14.0 to communicate with a MUF at Version 14.0 and also with a MUF at Version 12.0. Special actions a user must take to accomplish this are as follows (this batch requirement also applies to CA Datacom CICS Services):

1. Copy the following modules from the Version 14.0 library set to a special library and use that library for those batch jobs that require multiple MUF communication. The modules are:

   DBDUMPR

   DBINFPR

   DBINRPR

   DBSGMPR

2. After the modules are copied, ensure that they are kept current with maintenance changes and that the library is updated as needed.
3. After all the MUFs have been upgraded to the same version, correct the JCL to point to the complete Version 14.0 libraries.

Note:It is possible that for batch user programs simply using only CA Datacom/DB, pointing to the full Version 14.0 might work, but it would not work for applications that use the CA Datacom Datadictionary Service Facility, and It would not work for executions of CA Datacom Datadictionary utilities or CA Dataquery utilities.

An exception exists that user programs that request multiple task areas, and therefore do private multiple tasking, need to run with the interface modules matching the release of the MUF.