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?
________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Staller, Allan [[email protected]] Sent: Tuesday, October 09, 2012 3:50 PM To: [email protected] Subject: Re: DFSMSHSM Management Class Question <snip> 2) how do I verify that the appropriate number of backups are present? I know that 3 of them must exist when the dataset is not deleted. One backup when deleted. I confirmed that there is a backup when the dataset is not longer catalog by recalling it with "hrecover". </snip> HLIST DA(' dsname') BOTH Also verify you are using EXPIRATION BY DAYS and not EXPIRATION BY NON-USEAGE. They are represented in the DFSMS online panels by: EXPIRE DATE/DAYS and EXPIRE NON-USEAGE respectively. With EXPIRATION BY NON-USAGE *any* reference (even just to look at the vtoc without opening the dataset) to the dataset will reset the expiration counter to the date of that reference. The online help panels are very good for these two items. Read them carefully. BTW, given that the dataset exists, based on the previous entries in this thread, anywhere from 0 to 3 backups may be validly present. HTH, ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
