Step 5: Verify Media Database Integrity

This step consists of the CONVIDB job, which runs the CTTIDB utility after the conversion to verify the integrity of the Media Database. For more information about utility CTTIDB, see the Control-M/Tape chapter of the INCONTROL for z/OS Utilities Guide.

CTTIDB issues messages if database inconsistencies are detected. Examples of such inconsistencies are:

• errors in chain links that connect volumes in a multi-volume chain
• active volumes that do not contain datasets
• scratch volumes that contain active datasets
• discrepancies between Media Database records

If the CTTIDB utility reports errors, it may point to problems that were overlooked or missed in the preparation of the CA-1 Tape Management Catalog (TMC). In this case, correct the original data and repeat the conversion process from where the Media Database is formatted (in the Automatic Conversion steps described in Step 2: Automated Conversion Steps).

You can also correct problems directly in the Control-M/Tape Media Database. For more information about the CTTIDB utility, see the chapter that discusses media database integrity verification in the Control-M/Tape Implementation Guide, and the Control-M/Tape chapter of the INCONTROL for z/OS Utilities Guide.

CTTIDB also generates Media Database statistics that can be used for comparison with the CA-1 TMC. The statistics provided include

• the number of used data records
• the number of used index records
• the number of free data records
• the number of free index records
• the total number of records according to type (that is, volume, dataset, and scratch)

For information about the structure of the Media Database (for example, data records and index records), see the Control-M/Tape chapter of the INCONTROL for z/OS Administrator Guide.