When you specify the AUDIT DATASETCONTROLS (MIGRATION) parameter,
AUDIT makes the following checks for each valid data set (
D) record in the MCDS (or for only those specified
by the DSNAMES or LEVELS parameter):
- If a data set record indicates a valid migrated copy, but the
data set is uncataloged, AUDIT reports *ERR 03.
- If a data set record indicates a valid migrated copy, but the
data set’s catalog entry does not refer to volume serial MIGRAT,
AUDIT reports *ERR 09.
- If a data set record indicates the migration copy is on a given
tape volume, but the TTOC base record (or indicated extension) does
not exist, AUDIT reports *ERR 17.
- If a specified data set name has no data set record, AUDIT reports *ERR 19.
- If a data set record indicates that a migration copy is on a certain
volume, but there is no migration volume record for that volume serial
number, AUDIT reports *ERR 20. (The error could
apply to any of the tape volumes spanned by a multivolume migration
copy.)
- If a data set record indicates the migration copy is on a given
DASD (or tape) migration volume, but the migration volume record indicates
the volume is a tape (or DASD) volume, AUDIT reports *ERR
21.
- If a data set record created by HSM Release 3 or later indicating
that a migration copy is not in an SDSP data
set, but no alias (A) record exists for the
migration copy, AUDIT reports *ERR 22.
- If a data set record indicates the existence of a VSAM-associations
(O) record, but no such record exists, AUDIT
reports *ERR 23.
- If a VSAM-associations record refers to a migrated VSAM component,
but there is no catalog entry for the component, or the catalog entry
is something other than a non-VSAM entry referring to single volume
serial MIGRAT, AUDIT reports *ERR 24.
- If a VSAM-associations record refers to a migrated VSAM component,
and its catalog entry properly indicates a migration copy, but no
alias record exists for the VSAM component, AUDIT reports *ERR 25.
- If a data set record indicates the existence of a back up migrated
data set (L) record, but no such record exists,
AUDIT reports *ERR 26.
- If a migration volume’s TTOC has no valid entry for a migration
copy supposedly starting on that tape, or continuing from another
tape, AUDIT reports *ERR 29. This error may
occur if AUDIT DATASETCONTROLS is executed while migration is currently
updating a given TTOC record. If this should occur, run AUDIT DATASETCONTROLS
while migration is inactive.
When the scope of the audit is
not limited
by either DSNAMES() or LEVELS(), AUDIT makes additional checks:
- If a VSAM-associations record refers to a data set record that
does not exist, or that does not refer back to the VSAM-associations
record, AUDIT reports *ERR 27.
- If an alias record refers to a data set record that does not exist,
AUDIT reports *ERR 28.
- If an invalid record type is found in the MCDS, AUDIT reports *ERR 30.