If there is no BCDS information for a dataset, then as far as HSM is concerned the dataset has no backup. Unless you patch HSM, it will not delete a dataset that has no backup.
Determining how this occurred may be more trouble than it is worth if the datasets were migrated long ago. You could start tracking newly migrated datasets to determine if the situation repeats and possibly catch it while there is enough data to correct the cause. If you don't care that a migrated dataset has no backup, you can manually delete it. If you do care about the backup, you can restore the dataset, manually back it up, and then delete it. :>: -----Original Message----- :>: From: IBM Mainframe Discussion List [mailto:[email protected]] On :>: Behalf Of Uriel Carrasquilla :>: Sent: Tuesday, October 09, 2012 1:19 PM :>: To: [email protected] :>: Subject: Re: DFSMSHSM Management Class Question :>: :>: I ran the HLIST command on both, the dataset properly deleted and the :>: one that was not. :>: Even when they both have the same management and storage class, I found :>: that for the dataset properly delete, it had no MCDS information and the :>: BCDS information was present. :>: That is not the case for the one that was supposed to be deleted but it :>: was not. :>: It had the MCDS but no BCDS information. :>: Why would the BCDS be missing? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
