Smart Reorg restrictions and requirements

Common restrictions

Only one database (DBD) can be processed in a single Smart Reorg job in any mode.

Unconditional Reorganization mode restrictions

• Building shared secondary indexes is not supported because IMS Index Builder does not support them. For more information, see the IMS Index Builder User's Guide.
• Checkpoint and restart capability is not provided.
• User-written Data Conversion exit routines are not supported.
• The Smart Reorg Driver supports only a subset of the control statements of the stand-alone IPR Unload utility, the IPR Reload utility, IMS Index Builder, the Concurrent Prefix Update of IMS HP Prefix Resolution, and IMS HP Image Copy. The system default values of some parameters for the Image Copy task are different from those for the stand-alone IMS HP Image Copy. For a list of supported control statements, see Control statements for the Smart Reorg Driver.
• Any limitations of the stand-alone utilities are also limitations of the Smart Reorg utility.
• Certain characteristics of a DBD cannot be changed between the unload process and the reload process. For details, see NEWDBD control statement.
• The following restrictions apply to IMS HP Image Copy processing:
  • The following database organizations are not supported:
    • HDAM or HIDAM databases that have external logical relationships that need Prefix Resolution and Update.
    • HISAM databases that have logical relationships because IMS HP Prefix Resolution does not support such databases. For details, see External logical relationships of HDAM and HIDAM, Logical relationship of HISAM, and Logical relationships that do not require Prefix Resolution and Update.
  • Type-A Image Copy does not support the image copy stacking feature. Use Type-B Image Copy if you want to stack image copies.
  • Type-A Image Copy cannot be used if PSINDEXes are built with the PSINDEXBLD=YES option. Use Type-B Image Copy if you want to build PSINDEXes.
• IMS catalog databases are not supported.

Conditional Reorganization mode and Reorganization Diagnosis mode restrictions

• All restrictions in Diagnosis-only mode restrictions and requirements and in Unconditional Reorganization mode restrictions apply when running the job in Conditional Reorganization mode or in Reorganization Diagnosis mode.
• Unload data set cannot be used as the input for reorganization in Conditional Reorganization mode or in Reorganization Diagnosis mode. When the Smart Reorg utility runs the reorganization process in a job that runs in these modes, it unloads segment data from the database for the reorganization. Therefore, you must ensure that DASD space for shadow data sets is always available during the parallel reorganization phase.
• For HALDBs, only a single partition can be processed in a single Smart Reorg job that runs in Conditional Reorganization mode or in Reorganization Diagnosis mode.
• DBD changes are not allowed in Conditional Reorganization mode or in Reorganization Diagnosis mode.

Diagnosis-only mode restrictions and requirements

• The use of IMS Tools KB is mandatory.
• All STEPLIB libraries must be APF-authorized.
• For a database that uses VSAM data sets, SHAREOPTIONS other than (1,3) must be specified for each VSAM data set of the database.
• When DB Sensor collects sensor data from an online database, the collected data element values might not reflect the latest database condition. For a list of data elements that have the potential of not storing the latest data, see Considerations for collecting sensor data from a database that is being updated