DFSMShsm has done recall tape takeaway for quite some time. If a recall needs a tape that is being used as recycle input (or, IIRC, TAPECOPY), the using task is forced to give the tape up.
On Thu, 14 Mar 2024 at 12:46, Allan Staller < [email protected]> wrote: > Classification: Confidential > > <QUOTE> > Gadi, Mike has a good point. Doing HSM tape recycles could help free up > any tapes with a low number of datasets on them. This is true for > migration tapes and backup tapes. Be warned that if you don't do tape > recycles on a scheduled basis the process could possibly run for a long > time. As an example, I think that could then impact HSM process of recalls > from tape. I believe the place I last worked at did tape recycles every day > </QUOTE> > > You might want to consider "sneaking up" or your eventual goal. > Let us say your goal is to eventually get to a 25% recycle percentage. > Day 1 you could do a 5% recycle, Day 2 could be a 10% recycle,.... > > Also, you can issue a HSM RECYCLE command to find out (in advance) how > many tapes will be included. > > BTW, you can also segregate Backup and Migration recycles. By default all > tapes (Backup and Migration) are included with Migration being processed > first. > > HTH, > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
