Using the AUDIT DATASETCONTROLS (BACKUP) command

When you specify the AUDIT DATASETCONTROLS (BACKUP) command, the following checks are performed for each valid data set (B) record in the BCDS (or for only those specified by the DSNAMES or LEVELS parameter):

If a backup version (C) record indicates the version is on a given tape backup volume, but the TTOC (T) base record for that volume does not exist, AUDIT reports *ERR 17.
If the latest backup version (C) record indicates a version number that is higher than the version number in the MCBGEN field of the associated data set backup (B) record, AUDIT reports *ERR 35.
If there is a discrepancy between the MCBVER and MCCGEN fields of a backup version entry, AUDIT reports *ERR 36.
If a backup version (C) record has a sequence number that is not the same as the sequence number of the associated retained version (Z) record, AUDIT reports *ERR 37.
If a retained version (Z) record exists and the associated backup version (C) record’s sequence number field indicates no retained version (Z) records exist, AUDIT reports *ERR 38.
If a retained version (Z) record exists and the associated data set (B) record does not contain a value greater than zero in the sequence number field, AUDIT reports *ERR 38.
If a data set record (or retained backup record) refers to a backup version for which there is no version record, AUDIT reports *ERR 39.
If a data set record refers to a backup version record (or retained backup record) that does not refer back to the data set record, AUDIT reports *ERR 39.
If the entry in a data set record’s (or retained backup record's) version index and the backup version record itself indicate that version is on a certain backup volume, but there is no backup volume (X) record for that volume serial number, AUDIT reports *ERR 41. (The error can apply to any of the tape volumes spanned by a multivolume backup version.)
If the entry in a data set record’s version index and the backup version record itself indicate that version is on a certain migration volume, but there is no migration volume (V) record for that volume serial number, AUDIT reports *ERR 42.
If a backup version is found on its indicated migration volume, but no move (M) record exists for that version, AUDIT reports *ERR 43.
If the entry in a data set record’s (or retained backup record's) version index and the backup version record itself indicate that version is on a certain DASD backup volume, but the backup volume record indicates the volume is a tape (or vice versa), AUDIT reports *ERR 44.
If the entry in a data set record’s version index and the backup version record itself indicate that version is on a certain migration volume, but the volume is not mounted or (according to its VTOC) does not contain the backup version, AUDIT reports *ERR 47.
If a specified data set name has no data set record, AUDIT reports *ERR 48.
If the backup version record (B) indicates retained backup version records exist, but they are not found, AUDIT will report MSG 912.

When the scope of the audit is not limited by either DSNAMES() or LEVELS(), AUDIT makes additional checks:

If an invalid record type is found in the BCDS, AUDIT reports *ERR 30.
If a (L) record calls for backing up a migrated data set, but no MCDS record exists for that data set, AUDIT reports *ERR 46.

When you specify the AUDIT DATASETCONTROLS(BACKUP) parameter, AUDIT also checks to ensure version (C) records have an associated entry in a data set (B) record (or in a retained backup version (Z) record). The check is made for each version (C) record or for only those specified by the LEVELS parameter. A fully qualified backup version name can be used with the LEVELS parameter to process a single MCC record. If the backup version record refers to a BCDS data set (B) record that does not exist, or the (B) record exists but does not refer to the version (C) record, AUDIT reports *ERR 40.

If the backup version record refers to a retained version (Z) record that does not exist, or the (Z) record exists but does not refer to the backup version (C) record, AUDIT reports *ERR 40.

Important: Each FIXCDS command generated with this error is dependent on previous FIXCDS commands. If NOFIX is used, the offsets in the output data set are invalid.