You can migrate the database of a CA Technologies using product from a CA Datacom®/AD Version 10.0, 11.0, and 12.0 source MUF to a CA Datacom®/AD 15.0 target MUF. Use the Active Upgrade process to bring your AD environment to Version 15.0 if you have a CA Datacom®/AD Version 14.0 source MUF.
Note: The term target MUF refers to CA Datacom/AD Version 15.0. The term source MUF refers to CA Datacom/AD Versions 10.0, 11.0, or 12.0.
The current process supports those legacy databases that delivered Backup Transport Generator (BTG) transactions to define their databases fully. Legacy databases that used the BTG process are non-SQL created databases. They do not contain any SQL Data Definition Language (DDL) statements such as, CREATE statements and ALTER statements.
The migration process supports the porting of Versions 10.0, 11.0, and 12.0 to CA Datacom/AD Version 15.0. Therefore, valid CA Datacom/AD source MUFs for the porting/migration process are Versions 10.0, 11.0, and 12.0. The source MUF and the target MUF must be enabled and able to take new work. Because the porting process uses the source MUF and target MUF in the same job, both MUFs must be running before the migration process can start.
Note: Between the start of the porting process and a fallback to the previous release is no longer considered for a CA Datacom/AD using product, no structure changes to any CA Datacom/AD using database are supported by the porting/migration process. Never make any CA Datacom/AD using database structure changes in the porting or fallback processes as delivered.
The following options exist for applying database structure changes. These options can only be processed outside of the time line between the beginning of the porting process and the end of any possible need for a fallback.
The following topics are discussed on this page:
Before you start the porting process, verify that your site has run the installation verification process successfully for CA Datacom/AD Version 15.0.
The migration process migrates or ports a single database at a time. If your source CA Datacom/AD MUF has more than one database, the process can migrate as many databases as you need to the CA Datacom/AD Version 15.0 target MUF. You are not required to have CA Datacom/AD Version 11.0, 12.0 or 14.0 installed at your site if your source for the database is a CA Datacom/AD Version 10.0 MUF. You can migrate your database to the CA Datacom/AD Version 15.0 target MUF directly from CA Datacom/AD Version 10.0. Likewise, you are not required to have CA Datacom/AD Version 12.0 installed at your site if your source for the database is a CA Datacom/AD Version 11.0 MUF. You can migrate your database to the CA Datacom/AD Version 15.0 target MUF directly from CA Datacom/AD Version 11.0. However, fallback has to be back to the version of MUF from which you ported. Therefore, if you ported from a Version 10.0 MUF to Version 15.0, you have to fallback to that specific Version 10.0 MUF.
CA Technologies using product for CA Datacom/AD has a special module that allows the DDRTVCAT process to execute for that given CA Datacom/AD using product. To be successful, that library must be part of the STEPLIB concatenation for this process. This module is a basis module for this process. This module is delivered as part of your CA Datacom/AD using product installation when you first installed this product. A basis module can support more than one database DBID when running this process. Installation Worksheet Item 25 addresses this concern. The current process is set up for the CA Datacom/AD using product library to be placed into the library chain for PGM=DDRTVCAT STEPLIB.
Note: This process does not work if you have SQL-created objects.
The data from the current CA Datacom/AD Version 10.0, 11.0, or 12.0 source MUF database is lost if you reinstall the product from the CA Technologies using product. To make the definitions from the CA Technologies using product in the CA Datacom/AD Version 15.0 target MUF match the definitions in the CA Datacom/AD source MUF:
For an example of the backup or load that is needed, see the information about AD15BKUP or AX15DD in Post-Installation Considerations.
Carefully review the next two jobs. Only one of these jobs is used to migrate your source MUF to Version 15.0. Use job AXPOR01 if you have a Version 12.0 Source MUF. Use job AXPOR02 if you have Version 10.0 or 11.0 as your Source MUF.
|1||Retrieve AXPOR01 from INSTJCL, perform changes as directed, and submit the JCL.||Migrates a database from CA Datacom/AD Version 12.0 source MUF to CA Datacom/AD Version 15.0 target MUF.|
|2||Retrieve AXPOR02 from INSTJCL, perform changes as directed, and submit the JCL.||Migrates a database from CA Datacom/AD Version 10.0 or 11.0 source MUF to CA Datacom/AD Version 15.0 target MUF.|
This job allows an existing database that does not use SQL Objects to move from a CA Datacom/AD source MUF (Versions 10.0, 11.0, or 12.0) to a CA Datacom/AD Version 15.0 target MUF. Because the process is repeatable, you can process more than one database. Follow all the special instructions listed in the member.
Note: If you have a CA Datacom/AD Version 14.0 source MUF, use the Active Upgrade process to bring your AD environment to Version 15.0.
Follow these steps:
If an abend occurs, correct the JCL and repeat the job. Repeat this entire job as often as needed for each database without any required changes.