Errors detected when using AUDIT MEDIACONTROLS for a DASD migration volume
For each specified volume serial number that identifies a mounted
DASD migration volume, AUDIT makes the following checks for each data
set with a DSCB having the attributes DFSMShsm assigns to its data
sets (other DSCBs are ignored):
- For a dsname with leading qualifiers indicating a migration copy:
- If AUDIT cannot identify the first record as a CDD, it reports *ERR 150.
- When the first record is a CDD:
- If there is no data set record in the MCDS:
- If a catalog entry indicates the data set is migrated, AUDIT reports *ERR 133 (see also Diagnosing Error 133).
- If a catalog entry indicates a nonmigrated data set, AUDIT reports *ERR 149.
- If the data set record exists, but is not flagged as valid:
- If a catalog entry indicates the data set is migrated, AUDIT reports *ERR 133 (see also Diagnosing Error 133).
- If there is no catalog entry, AUDIT reports *ERR 149.
- If a catalog entry indicates a nonmigrated data set, AUDIT reports *ERR 149.
- If there is a valid data set record in the MCDS:
- If a catalog entry indicates the data set is migrated, but there is no alias record, AUDIT reports *ERR 140.
- If a catalog entry indicates the data set is migrated, but the data set record in the MCDS refers to a different copy, AUDIT reports *ERR 149.
- If there is no catalog entry, AUDIT reports *ERR 151.
- If a catalog entry indicates a nonmigrated data set, AUDIT reports *ERR 152.
- If there is no data set record in the MCDS:
- For a dsname with leading qualifiers indicating a backup version:
- If AUDIT cannot identify the first record as a CDD, it reports *ERR 150.
- If the first record is a CDD, but the corresponding data set record in the BCDS has no reference to a backup version with this name, AUDIT reports *ERR 142.
- For a dataset with
- A dsname not generated by DFSMShsm, and
- A CDD as a first record, and
- A catalog entry indicating the data set is migrated, but
- No data set record in the MCDS,
AUDIT reports *ERR 133 (see also Diagnosing Error 133).