Skip to content

Strategy Analysis

Last update November 13, 2014

After a strategy has been created for migration, alteration, or comparison, the next phase is strategy analysis. When a strategy is analyzed, an executable output data set or table is generated to perform the operations that the strategy describes. The analysis output contains the DDL and JCL to perform the operations. The output can be reviewed and edited before it is executed. When the output is executed with the Batch Processor, the actual changes are made to the DB2 objects.

As a part of the analysis, you can also create DDL and JCL to reverse the operations defined in the analysis DDL, so that you can recover from an executed strategy. 

During every strategy analysis, CA RC/Migrator™ for DB2 for z/OS checks for DB2 features that are not currently supported. If the product detects an attempt to operate on objects that exploit unsupported features, warning messages are directed to an output data set named RCMTOLR. If you do not want to use RCMTOLR, you can disable RCMTOLR data set creation by customizing the MIGRATOR parmlib member in hlq.CDBAPARM. However, we strongly recommend using RCMTOLR and checking for warning messages generated by the analysis before executing the strategy.

Note: RCMTOLR will report what was detected. However, RCMTOLR is unable to detect every unsupported feature.

The analysis phase performs validation and cross-reference checking to help ensure the integrity of the resulting structure. For example, the analysis function checks for conflicting referential integrity key changes. For edited objects, the original object definition is verified to help ensure there were no changes to the object since the edit. The analysis function produces a comprehensive report that details all warnings.

Was this helpful?

Please log in to post comments.