Considerations for converting to HALDB
The following considerations apply when you convert to a HALDB by using the ISPF user interface.
When databases are offline, conversion options are available by using ISPF panels or by using the batch conversion method.
Converting full-function databases requires that IMS HALDB Toolkit evaluate partition sizes and boundaries. Partitioned databases which use the PDB/PDF product are considered full-function databases and can be converted as such.
The conversion process for PDBs/PDFs uses partition high keys (for HIDAM/HISAM to PHIDAM) or the number of partitions (HDAM to PHDAM).
You can also choose to select the partition boundaries again. In this case, the partition definition from the PDB is ignored and the database is treated in the same way as any full-function database.
- New database definitions must exist in the IMS catalog staging data sets before running the ISPF user interface.
- The shadow database is unloaded by using the active database definition obtained from the IMS catalog directory data sets, then reloaded by using the pending database definition obtained from the IMS catalog staging data sets.
- JCL for DBDGEN is not generated because the pending database definition obtained from the IMS catalog staging data sets is used.
- JCLs for image copy are not generated because the image copy utility does not support the pending database definition obtained from the IMS catalog staging data sets. You must take an image copy manually after the conversion.