Repository Structure

The Control‑M/Tape Repository is composed of the following files:

• media database
• trace file
• stacking database

  Note: Place Control‑M/Tape databases and the Trace file only on disks that do not get defragmented while Control‑M/Tape is running. If your site uses a disk defragmenter, place the Control‑M/Tape TRC, MDBD, MDBI, STKD and STKI datasets in an "exclude list" to prevent the defragmenter from processing them.

Control-M/Tape Media and Stacking databases are managed by IOA Access Methods. The following IOA Access Method restrictions exist for the Control-M/Tape database:

• Allocation of new Media Database extensions is not automatically defined. They can only be defined manually, using the IOADBF utility with the EXTEND option.
• Secondary allocations for the index file are not allowed.
• Dual database option is not allowed.
• The data files must be defined with TYPE=F in the IOA Access Method member definition because TYPE=V is not allowed for Control-M/Tape data file.