IMS catalog

The following topics describe the purpose and content of the IMS catalog database and administrative tasks to maintain the IMS catalog.

Overview of the IMS catalog
The IMS catalog contains trusted metadata and definitions of the IMS databases and application program views that are defined to IMS.
Backup and recovery of the IMS catalog
The IMS catalog is a HALDB database, so you can use standard HALDB backup and recovery procedures to back up and recover an IMS catalog, but you must make sure that the records in the recovered IMS catalog match that application control blocks (ACBs) that are active in the IMS system.
Cleaning up the IMS directory data sets
In an IMS-managed ACBs environment, the Catalog Directory Recovery utility (DFS3RU00) can also be used to clean up the IMS directory data sets when the directory online updates aborted abnormally.
Maintaining the IMS catalog
The IMS catalog is an IMS HALDB full-function database, so even though it should not require much maintenance, the same maintenance considerations that apply to other HALDB full-function databases apply to the IMS catalog.
Removing DBD and PSB instances from the IMS catalog
You can remove the segments that represent individual DBD and PSB instances from the DBD and PSB records in the IMS catalog by using the IMS Catalog Record Purge utility (DFS3PU10).
Using HALDB utilities with an unregistered IMS catalog
All HALDB utilities are supported for an IMS catalog database that is registered in the RECON data set and managed by DBRC. Some restrictions apply to an unregistered catalog.
Format of records in the IMS catalog database
The IMS catalog database contains a unique record for each PSB and DBD defined during ACB generation. Each type of record, and each type of segment within a record, has a predefined format.
IMS catalog secondary index
The IMS catalog secondary index provides a short processing path for determining which PSBs refer to a specific DBD.
IMS catalog activity records
Certain types of activity against the IMS catalog can be logged in z/OS® System Management Facility (SMF) as a type-29, subtype-3 record.

Parent topic: Database administration