Placing Control-M/IOA Files on Appropriate Disk Packs
The following disk or file characteristics enable Control‑M to perform optimally:
- disks that are not very active and are not connected to heavily utilized disk strings and disk channels
- disks that do not contain MVS system files
- disks that do not contain a PAGE or SWAP dataset
- at a multi-CPU site: disks that are not physically reserved (and therefore cannot be physically locked) by other CPUs
- disks whose head movement is minimized by placing Control‑M/IOA files near the VTOC
- files (IOA RES, IOA LOG, Control‑M AJF and History file) that are split over several disks (after installation)
- disk types that are newer, for example, 3390 and others discussed in "Placing Certain Control‑M/IOA Files on Special Disk Devices"