DFSMSrmm cleanup data set records

Most customers today are using VTS to create tapes. When the tapes go scratch, after x number of days, the data is usually deleted from the VTS. For example this is the case with TS77xx EXPIRY-HOLD=x days, meaning after RMM has scratch the tape, the tape is kept for x days as specified in EXPIRY-HOLD and then the data is deleted and is not recoverable.

When that happens, when the scratch mount request occurs, the virtual tape volser may not get re-used for quite some time, in some cases weeks or months, as the TS77xx will go down the list of all the scratch virtual volumes before it re-uses the older scratch volumes.

RMM Keeps the data set records in the CDS even when the tape is scratched for recovery purposes and are only deleted when the tape volser is re-used.

This contributes to growth of CDS and customers have to REORG and enlarge their CDSs.

Idea being proposed is to have a new parmlib option, such as DSNCLEANUP(nnnnn) where nnnnn is the number of days you specify, for example DSNCLEANUP(10), meaning 10 days after the tape has been scratched, to delete the data set records for the tape. Since DFRMM doesn't do any maintenance dynamically and all of it is being done through batch processes, then, the idea would to include it as part of PGM=EDGHSKP and come up with a new parameter called CLEANUP which would then read DSNCLEANUP specified in EDGRMMxx.

A similar idea was opened back in 2021:

ZOS-I-2250