Previous Topic: Step 3. Execute DQBATCH Program (optional)

Next Topic: Migration/Porting Phase for Non-SQL Created Databases

Migration/Porting Phase for Non-SQL Created Databases

Migrating 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 Version 14.0 target MUF is described in this section.

Note: To clarify terminology, the term target MUF refers to CA Datacom/AD Version 14.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 fully define their databases. Legacy databases that used the BTG process can be termed non-SQL created databases, because they do not contain any SQL Data Definition Language (DDL) statements, for example, 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 14.0, that is to say, valid CA Datacom/AD source MUFs for the porting/migration process are Versions 10.0, 11.0, and 12.0. Both 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 executing before the migration process can start.

Note: Between the time the porting process begins and the time that a fallback to the previous release is no longer a consideration for a CA Datacom/AD using product, the porting/migration process does not support any kind of structure changes to any CA Datacom/AD using database. Also, do not under any circumstances make any CA Datacom/AD using database structure changes in the porting or fallback processes as delivered.

Two options exist for applying database structure changes, if needed, but both of the following 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.

Database Migration of a CA Technologies Using Product that Uses CA Datacom/AD

Before you start the porting process, verify that your site has successfully run the installation verification process for CA Datacom/AD Version 14.0.

The migration process migrates or ports a single database at a time. If, however, 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 14.0 target MUF. If your source for the database is a CA Datacom/AD Version 10.0 MUF, you are not required to have CA Datacom/AD Version 11.0 or 12.0 installed at your site. You can migrate your database to the CA Datacom/AD Version 14.0 target MUF directly from CA Datacom/AD Version 10.0. Likewise, if your source for the database is a CA Datacom/AD Version 11.0 MUF, you are not required to have CA Datacom/AD Version 12.0 installed at your site. You can migrate your database to the CA Datacom/AD Version 14.0 target MUF directly from CA Datacom/AD Version 11.0. However, fall back has to be back to the version of MUF from which you ported, that is, if you ported from a Version 10.0 MUF to Version 14.0, you have to fall back 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 has to be part of the STEPLIB concatenation for this process. This module is called a basis module for this process. Expect this module to be 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 (see Installation Worksheet). 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.

If you reinstall the product from the CA Technologies using product , the data from the current CA Datacom/AD Version 10.0, 11.0, or 12.0 source MUF database is lost. Therefore, to make the definitions from the CA Technologies using product in the CA Datacom/AD Version 14.0 target MUF match the definitions in the CA Datacom/AD source MUF, after you unload or back up the database from the CA Datacom/AD supported source MUF, load the data back to the database newly defined to the CA Datacom/AD Version 14.0 target MUF. For an example of the backup or load that is needed, see the information about AD14BKUP or AX14DD in Post-Installation Considerations.

Step

Description

Purpose

1

Retrieve AXPOR01 from INSTJCL, perform changes as directed, and submit the JCL.

Migrates a database from CA Datacom/AD Version 10.0, 11.0, or 12.0 source MUF to CA Datacom/AD Version 14.0 target MUF.