For each volume record indicating a DASD migration volume, AUDIT
makes the following checks for each DSCB having the attributes DFSMShsm
assigns to its data sets (other DSCBs are ignored):
- If the first qualifier of a data set name indicates a migration
copy, but there is no alias record in the MCDS, AUDIT reports *ERR 140.
- If the DSCB for a migration copy or backup version indicates an
empty data set (TTR of 0), AUDIT reports *ERR 141.
- If the first qualifier of a data set name indicates a backup version,
but there is no backup version record in the BCDS, AUDIT reports *ERR 142.
- If the backup version record corresponding to a DSCB does not
indicate a version scheduled for deletion, and there is no move record
for that version, AUDIT reports *ERR 43.
- If the first qualifier of a data set name indicates a VTOC copy
for a certain volume, but there is no eligible volume (P) record for that volume in the BCDS, AUDIT reports *ERR 143.
- If the eligible volume record corresponding to a VTOC copy DSCB
indicates
- The volume has not been backed up; or
- Its related VTOC copy data sets are on other volumes; or
- Its VTOC copy data set is not (determined by the qualifiers in
its name) the one we started from
AUDIT reports *ERR 144.
- If the first qualifier of a data set name indicates a Dump VTOC
copy for a certain volume, but there is no eligible volume record
for that volume in the BCDS, AUDIT reports *ERR 145.
- If the eligible volume record corresponding to a Dump VTOC copy
DSCB indicates there are no valid dump generations for that volume,
AUDIT reports *ERR 146.
- If the eligible volume record indicates there is at least one
dump generation, but no dump generation record refers to the Dump
VTOC copy we started from, AUDIT reports *ERR 146.
- When there is a catalog entry for the dsname indicating it is
migrated, but the dsname’s first qualifiers are not recognized
as DFSMShsm generated,
- If there is no valid data set record in the MCDS, AUDIT reports *ERR 147.
- If there is a valid data set record in the MCDS referring to the
volume we started from, but indicating the migration copy is in an
SDSP data set, AUDIT reports *ERR 148.
- When there is a valid data set record in the MCDS, but it indicates
a migration copy on some other DASD volume (not in an SDSP data set),
- If the other volume is mounted, but the dsname cannot be found
in its VTOC, AUDIT reports *ERR 147.
- If the other volume is mounted and the dsname is found in its
VTOC, AUDIT reports *ERR 149.
- If the other volume is not mounted, AUDIT reports *ERR
148.
- When there is a valid data set record in the MCDS, but it indicates
a migration copy on a tape volume,
- If a valid TTOC entry can be found for that tape volume, AUDIT
reports *ERR 149.
- If no valid TTOC entry can be found, AUDIT reports *ERR
147.
- If the catalog information data set was found on an ML1 volume
but the data set is not cataloged, AUDIT reports *ERR
196.
- If there is no corresponding Fast Replication backup version for
the catalog information data set, AUDIT reports *ERR
197.
- *ERR 198 indicates that the copy pool backup
version specified by the catalog information data set indicates that
the catalog information was not captured. This catalog information
data set does not correspond to a valid existing copy pool backup
version.
- If the copy pool version that the catalog information data set
indicates that it is associated to is not the catalog information
data set that the copy pool version record indicates, AUDIT reports *ERR 199.
- *ERR 200 indicates that there was an unexpected
error while trying to process the catalog information data set. This
message should be preceded by an ARC1812I message.
- If the catalog locate for the catalog information data set indicates
that this data set is cataloged on a different volume, AUDIT reports *ERR 201.