Migration steps for an existing IMS catalog in systems that use ACB libraries
Like other IMS databases, the IMS catalog is defined by a DBD and accessed through PSBs. The migration procedure for the IMS catalog differs depending on which version of IMS you migrate from, and if you are migrating multiple IMS systems that share the catalog. If you are migrating from IMS Version 13, the ACBs for the catalog must be generated from the DBDs and PSBs that IMS 15.5 supports. If you are migrating from IMS 14, you do not need to re-generate the catalog ACBs. Additionally, when the ACBs for the other databases and program views in the IMS system are re-generated for the new IMS release, the IMS catalog must be updated with those ACBs to keep the IMS catalog in sync with the active ACBs in use by the IMS system.
Ensure that enough storage is allocated to the IMS catalog to accommodate the insertion of a complete IMS 15.5 set of the existing DBD and PSB resources.When migrating from IMS Version 13, the IMS catalog holds a complete set of your existing resources and a complete set of IMS 15.5 resources.
Updating an IMS catalog for a new release can take a long time. Before you populate the IMS catalog, consider tuning your buffer pools based on the number and types of segments in the IMS catalog so that the utility you use for population doesn't do many buffer steals.
If you are migrating from IMS Version 13, you must generate the catalog ACBs from the DBDs and PSBs that IMS 15.5 supports by using the IMS 15.5 ACB Generation and Catalog Populate utility (DFS3UACB). The DBDs and PSBs for the catalog changed between IMS Version 13 and IMS 15.5. Step 3 is required.
If you are migrating from IMS 14, you do not need to generate new catalog ACBs from the DBDs and PSBs. The DBDs and PSBs for the catalog did not change between IMS 14 and IMS 15.5. Skip step 3.
The following steps update an existing IMS catalog for a new version of IMS.
Procedure
If you have any application programs that read the IMS catalog, review the structure of the IMS catalog to ensure that the application programs can handle any changes appropriately.
After testing is complete and you are certain that you do not need to fall back to the previous version of IMS, you can remove the DBD and PSB resource instances for the past IMS version from the IMS catalog by using the IMS Catalog Record Purge utility (DFS3PU10).