Perhaps I am restating the obvious.
1) Select one of the "mystery" datasets and verify the management class is the
one expected and is same as the "non-mystery" datasets.
2) Verify the appropriate number of backups are present for each dataset. If
not, the DBU (delete if backed up ) function may be preventing deletion of the
migrated copy.
There is an appropriate message in the Migration or Backup logs indicating
this is the case. If so, there is a document patch. See GC52-1083-07 dfHSM
Diagnosis Guide
HTH,
<snip>
We have a Management Class defined to expire datasets after a given number of
days.
I know it is working because I found some datasets about to expire, waited for
them to expire, and now I can see they are no longer in the catalog (the
management class stipulates that we keep one backup for a few years after
deleting).
But, I also noticed that some files that have exactly the same management class
and should have been expired/deleted a long time ago are still catalogued. I
recalled one of them and it had no expiration date and confirmed that it
belongs to the same management class.
</snip>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
