Checking TTOC entries for a migration volume

If AUDIT finds the TTOC base record, it checks the sequence of CDDs against the sequence of TTOC entries found in the base record and zero or more TTOC extensions. If a TTOC extension is missing, AUDIT reports *ERR 111.

• For a CDD with a corresponding data set record in the MCDS:
  • If the block count in the previous TTOC entry does not agree with the number of blocks read since the previous CDD found, AUDIT reports *ERR 135.
  • If there is no catalog entry or the catalog entry indicates a nonmigrated data set, AUDIT reports *ERR 132.
  • If the catalog indicates the data set is migrated, but the data set record is flagged invalid, AUDIT reports *ERR 133 (see also Diagnosing Error 133).
  • If the catalog indicates the data set is migrated, but the corresponding TTOC entry is flagged invalid, AUDIT reports *ERR 136.
• For a CDD with a corresponding catalog entry:
  • If the catalog entry indicates a nonmigrated data set, AUDIT reports *ERR 132.
  • If the catalog entry indicates a migrated data set, but there is no data set or alias record in the MCDS, AUDIT reports *ERR 133 (see also Diagnosing Error 133).

At the end of the volume:

• If the valid block count in the TTOC does not agree with the number of valid blocks read, AUDIT reports *ERR 137.
• If the total block count in the TTOC does not agree with the total number of blocks read, AUDIT reports *ERR 138.