Thank you for the advice Russ. I will look into it. Regards Jack
On Fri, Oct 10, 2025, 23:07 Russell Witt < [email protected]> wrote: > Jack, > You might look at Vaulting in combination with retention. In CA 1 for > example, you could have a 5-year retention and also have a vault rule that > says "keep it until it expires AND its Last-Use date is at least 1 year in > the past". I am not that familiar with RMM; but you might be able to use > the vaulting system to trick it into what you are attempting to do. No-one > ever looks at vaulting anymore (not with everything being replicated > Virtual-Tape), but vaulting still exists in the tape management systems and > can be re-purposed. > Russell WittCA 1 ArchitectBroadcom > On Friday, October 10, 2025 at 05:27:24 AM CDT, Jack Zukt < > [email protected]> wrote: > > Hi Radoslaw > Thank you for your comments > > Regards > Jack > > On Fri, Oct 10, 2025, 10:30 Radoslaw Skorupka < > [email protected]> wrote: > > > W dniu 10.10.2025 o 11:18, Jack Zukt pisze: > > > Hi, > > > > > > I have tried the RMM manuals but, once again, I can not find what I am > > > looking for. So, I hope that one of you will be able to help me. > > > > > > We have been asked if it is possible to retain a tape file for five > years > > > AND one year after the last use. So, if the file had been used three > days > > > before its five years original expiration date, it would keep for > another > > > year starting that use. And, id during that additional year it was used > > > again, then, new reset to the expiration date. This would be a > > COUNT(1825) > > > plus a REFDAYS(365), which, I think, it is not feasible. > > > Your help, as usual. will be highly appreciated, > > > Regards > > > Jack > > > > I would consider deeper change. > > You don't have to keep the tape. You need to keep datasets. > > Just keep them on disk, then use DFSMShsm to migrate it. And backup. > > Then all the parameters reside in the Management Class. > > Pros: > > easier to maintain > > no dependency on tape devices (VTS, physical ATL), volume size, etc. > > users need not to have any knowledge about tapes > > you manage datasets, not volumes. Some VRS constructs are related to the > > fact you have to keep or scratch whole volume, while you want to protect > > datasets. > > better tape utilisation (not as important in virtual tapes) > > no more multivolume issues > > > > My €0.02 > > > > -- > > Radoslaw Skorupka > > Lodz, Poland > > > > ---------------------------------------------------------------------- > > 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 > > > ---------------------------------------------------------------------- > 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
