Mike: Thanks for your accurate answer.
We dont have TAPEDSN in effect (we just control access to tape datasets by TAPEVOL profiles). Tapes used by HSM, in our shop, have a very distinctive naming convention, so i do not think that a generic RACF protection would interfere with user tapes. On the other hand, we do have RMM installed, but not fully exploited yet. Our current HSM setting is TAPESECURITY(RACF/RACFINCLUDE). My main concern is: Let suppose that i A) define a generic TAPEVOL profile covering all tapes used by HSM, with a proper ACL. B) delete the HSMHSM profile. Will HSM work properly? Should i expect any HSM failure? Will HSM show error messages each it uses a new tape because of trying to RACF protect it? Thanks in advance, Juan G. Mautalen -----Mensaje original----- De: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] En nombre de Mike Wood Enviado el: Lunes, 14 de Noviembre de 2005 06:09 a.m. Para: [email protected] Asunto: Re: [IBM-MAIN] RACF and DFHSM tapes Juan, How you protect HSM tapes depends very much on how you have RACF set up. Do you have TAPEDSN as well as using TAPEVOL? Using a generic TAPEVOL profile is not a good idea because it will cause all matching scratch tapes to be protected. If you only allow HSM access all other tape users will fail. HSM uses the TAPEVOL profiles to prevent others from accessing its tapes. If you had TAPEDSN in use you could perhaps use generic DATASET profiles for the HSM tapes instead. Once that was in place you wouldnt need to use TAPESECURITY(RACF/RACFINCLUDE). You should make sure that your tape management system is ensuring ful 44 character data set names are verified to avoid anyone making up a prefix to go with the 17 characters stored in the tape label. BTW, HSM will quite happily maintain the TAPEVOL profiles while you set up and test that the generic DATASETs work ok; once you are happy its working you can change the HSM SETSYS and deelte the TAPEVOLs for HSM. Mike Wood RMM Development On Thu, 10 Nov 2005 15:05:52 -0300, Mautalen Juan Guillermo <[EMAIL PROTECTED]> wrote: >--Cross posted to the RACF-forum-- > >Hi, > >We have TAPEVOL class active, and cartridges used by HSM are currently >protected by DFHSMx multivolumes tapevol profiles (tape volumes are >automatically added based on the last non blank character of the tape >volume label. For instance, HSM983 is added to DFHSM3 profile). This is >working well, but we have tons of HSM cartridges, because they are old >models with very small capacity. > >I want to switch to an schema in which HSM tape volumes are protected >by generic RACF tapevol profiles (the tape labels naming convention >allows generic protection). Is this possible? What should i specify for >the TAPESECURITY parameter of DFHSM? Is it as simple as NON defining >the HSMHSM tapevol profile and deleting all DFHSMx profiles? > >Unfortunately, DFHSM documentation is not clear enough for me. > > >Thanks for your help, > > >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 ---------------------------------------------------------------------- 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
