PowerExchange adds support for DB2 12 for z/OS for bulk data movement sources and targets and CDC data sources.
If you are migrating a DB2 CDC data source to DB2 12, you do not need to upgrade the DB2 for z/OS ECCR capture directory tables. No changes have been made to the structure of these tables since DB2 11.
Before you migrate, check the DB2 DSN6SPRM RESTRICT_ALT_COL_FOR_DCC parameter setting. PowerExchange reports this setting in message PWXEDM177155I in the ECCR output. How this parameter is set determines whether you will need to cold start the ECCR during the DB2 migration, as follows:
If the RESTRICT_ALT_COL_FOR_DCC parameter is set to NO, the ECCR will be able to process all DB2 log data that was generated during the DB2 catalog upgrade process and update the contents of the ECCR capture directory tables. A cold start is not required.
If the RESTRICT_ALT_COL_FOR_DCC parameter is set to YES, the first time you start the ECCR after migrating to DB2 12.1.100, you must perform a cold start. In a data sharing environment, you might need to cold start the ECCR an additional time, depending on where the ECCR runs:
When the first member of the data sharing group is migrated to DB2 12.1.100, cold start the ECCR, regardless of where the ECCR runs.
If the ECCR runs on another member of the data sharing group, when that member is migrated to DB2 12.1.100, cold start of the ECCR again.
A cold start of the ECCR is
not
required after you migrate any other member in the data sharing group.
When you upgrade from DB2 12.1.100 to 12.1.500, no ECCR cold start or other special action is required.
No special operational considerations apply to PowerExchange bulk data movement in a DB2 12 environment.
For more information, see the
PowerExchange Installation and Upgrade Guide
and the "DB2 for z/OS Change Data Capture" chapter in the