At our customers' sites that use HSM, we use TAPESECURITY(EXPIRATIONINCLUDE)) and let the tape management system (CA-1) handle tape security issues in conjunction with normal RACF dataset protection. None of the HSM volsers are entered into RACF. Making HSM an External Data Manager to CA-1 handles the expiration issues.
:>: -----Original Message----- :>: From: IBM Mainframe Discussion List [mailto:[email protected]] On :>: Behalf Of Arye Shemer :>: Sent: Wednesday, November 27, 2013 7:05 AM :>: To: [email protected] :>: Subject: DFSMSHSM TAPESECURITY(RACF) :>: :>: Hello dear experts. :>: :>: I have a customer who is considering using HSM (never used HSM before). :>: :>: We are trying to understand if when using TAPESECURITY(RACF) option of :>: HSM :>: :>: We also have to add manually each HSM VOLSER into the RACF TAPEVOL :>: HSMABR :>: profile. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
