And if you still do not have a solution, I would open an SR with IBM RMM to get clarification.
Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Greg Shirey > Sent: Thursday, July 07, 2016 6:18 AM > To: [email protected] > Subject: Re: DFHSM CDS backup versions > > As far as HSM and RMM "talking" to each other, there is this, from the RMM > Implementation and Customization Guide, I think for version 1.13: > > You can use the TVEXTPURGE parmlib option in the DFSMSrmm EDGRMMxx parmlib > member to control the action DFSMSrmm takes when DFSMShsm calls EDGTVEXT. A > benefit of this interaction is that DFSMSrmm can prevent DFSMShsm from > overwriting its own control data set backup, automatic dump, ABARS, and copies > of backup or migration tapes. Although DFSMShsm checks its own migration and > its own backup tapes, DFSMSrmm checks them as well. > > HTH, > Greg Shirey > Ben E. Keith Company > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Vince Getgood > Sent: Thursday, July 07, 2016 5:25 AM > To: [email protected] > Subject: Re: DFHSM CDS backup versions > > All, > Thanks for the hep so far. Please bear in mind that I "inherited" this site > from another contractor, and have no documentation about what was done or why. > He set this up. > > I also have no prior experience with RMM. > > <snip> > Try changing the "count" in the VRS to a "more reasonable (FSVO reasonable) > value. > e.g. 10 and see if the tapes release. > </snip> > > I'll try that, thanks. > > <snip> > HSM and RMM are independent products. Some shops use RMM with FDR instead of > HSM. Others use HSM with CA-1 instead of RMM. The two products will not talk > to each other unless you tell them to. > </snip> > > I can't find anything in the RMM or HSM manuals that tells me how to make them > "talk" to each other. HSM is definitely releasing migration and backup tapes, > just not CDS backup tapes. > > RMM talks about defining HSM to RACF, and setting RMM & HSM options (which as > far as I can tell has all been done). The only inconsistency I can see is > that the RMM manual says to code SETSYS TAPESECURITY(EXPIRATION), and we have > SETSYS TAPESECURITY(RACF). > > If you can point me at the relevant part of the manual, I'll happily read it! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
