I have not tested this, but I disagree. To use your example below, ..."on day 100 ... elided ... will be deleted immediately". In my experience the "extra backup" counter will begin at day 100, add 50 and the "extra backup" will expire on day 151.
Since I also run EXPIREBV on a daily basis, this may be setting the "extra backup" counter. The dfHSM manuals are really quite good about providing the details. See :" Availability management of SMS-managed storage" in http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2S6A1/CCON TENTS?SHELF=dgt2bkb1&DN=SC35-0421-13&DT=20120123164451 (watch the wrap) HTH, <snip> I think I found out what the SMS Retain Days Extra Backup Versions exactly means and want to make sure I am right. If I am right, I am not happy with it. A dataset has a mgmtclas with attribute SMS retain days extra backups = 50. On day 10 backup#1 is taken. On day 100 the dataset is updated and backup#2 is taken. If I am right, backup#1 receives an expiration date of day 60 and will be deleted immediately. So if I discover the next day that the update was incorrect, I want to restore backup#1, but it is not there anymore. </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
