Juan, Read on through that hsm book a few pages and you get more details and then find this statement; '5. If no RACF tape volume sets are defined to DFSMShsm but all tapes are protected by an existing RACF generic profile, then specify SETSYS TAPESECURITY(RACF|RACFINCLUDE). '
My understanding of this is that when no specific hsm tape volume sets are defined hsm will not attempt to maintain them, but will know the hsm tapes are protected by RACF (generic TAPEVOL profile). However, following up the caution from Walt; I advise you to test any changes first and be sure to include hsm EOV processing, writing to scratch tapes and recycle...... Be sure it still all works Mike Wood RMM Development On Mon, 14 Nov 2005 14:42:19 -0300, Mautalen Juan Guillermo <[EMAIL PROTECTED]> wrote: >Walt: > >There is a paragraph in the HSM documentation stating that generic >TAPEVOL protection should work. But it is somewhat vague, without any >details. >It says: > >--1.9.5.3 Protecting DFSMShsm Tapes > >--Tip: If you have not defined RACF tape volume sets for DFSMShsm, but >you want RACF to protect --all the tapes through a RACF generic profile, >specify the SETSYSTAPESECURITY --(RACFIRACFINCLUDE) >command. > >So, i am not trying to do something undocumented. >My interest comes from the fact that we have around 30.000 HSM tapes (in >a separate RACF dataset), and we want to consolidate both current RACF >datasets into a single one, and i like to reduce the number of TAPEVOL >profiles before making the consolidation. > > >JUAN MAUTALEN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
