Migrating HDAM and HIDAM databases to PHDAM or PHIDAM databases

When you are using the Reorg function or CRF, you can convert HDAM-to-PHDAM databases and HIDAM-to-PHIDAM databases in the single-step reorg.

Create a DBDLIB with the new HALDB DBD members, and specify this library in the IMS DD definition. If DBD members are being deleted from the DBD definition, remove them from this library. The current (old) DBDLIB is placed on the DD specified by the OLDDBD keyword.

Create DELETE.DB DBRC statements for the original HDAM or HIDAM database as the initial statements in the BMC$DBRC DD. Predefine the HALDB INIT.DB and INIT.PART DBRC definitions in the BMC$DBRC statements following the DELETE.DB statements.

To migrate HDAM and HIDAM databases to PHDAM or PHIDAM databases

Modify your standard Reorg function or CRF job to include the following information:

  • Add the DBRCUPDT(Y) and OLDDBD(ddName) keywords to PLUSIN.
  • Supply the current DBDLIB in the ddName DD the OLDDBD keyword specifies.

  • Supply the changed DBDLIB in IMS DD.

    DBD members that are no longer present after the specified changes cannot be in the IMS DD concatenation.

  • In the IDCAMS statements, include the delete or define statements for the HDAM or HIDAM shadow data sets (used during the copy phase of the online reorganization) and the delete or define statements for the HALDB database data sets (not the shadow data set names).

    Image copy control card input should reflect the HALDB data sets.

Note

During the post processing phase, the HALDB definitions are added to your RECONs. If you are using the DELTA IMS DB/DC product, your control blocks are automatically added to your IMS online systems and the database is authorized and started in your IMS online systems. For additional information, see DELTA-IMS-DB-DC-installed.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*