REORG INDEX generated twice during RC/Migrator Compare or Alter analysis

Products

• RC/Migrator for DB2 for z/OS
• RC Compare for DB2 for z/OS
• RC/Update for DB2 for z/OS

Issue/Introduction

RC/Migrator for Db2 for z/OS (RCM) Compare or Alter analyze generates REORG INDEX of every index before any DDL and again in the utility section after DDL.

Cause

This can occur if you use a MODELSET from Database Management release  r20 with a Database Management release r19 load library.
In the Database Management r20 model OREORGIX was changed and does not use %PENDDDL and %SQLPOSO to check if -  and where in the flow – the model should be activated.

Resolution

Make sure to use a Database Management release r19 MODELSET with Database Management release r19.

Additional Information

Model OREORGIX:

This model is used to generate an on-line IBM REORG to materialize the changes and apply the pending definition changes to the catalog and data.
 Without this REORG, any subsequently generated table or index DDL that  depends on these  changes being materialized will fail.