I got it figured out. I needed to be a little more granular than I was. I thought that the generic profile of STGADMIN.RM.* would be enough, but I had to add MOUNT, DEMOUNT, QUERY.LIB... etc.
Thanks, Dave -----Original Message----- From: Les Geer (607-429-3580) <[email protected]> Reply-to: The IBM z/VM Operating System <[email protected]> To: [email protected] Subject: Re: VMTAPE & RACF Date: Thu, 10 Sep 2009 15:33:28 -0400 Make sure you have followed all the RACF steps in the DFSMS/VM planning guide under section 'Using RACF/VM' That would include the RACF/VM requirements, Setting up RACF/VM, permitting RMSMASTR UPDATE authority to the ICHCONN profile in the FACILITY class, and all the RMS user RACF profiles. Best Regards, Les Geer IBM z/VM and Linux Development >>Did you do the SETROPS (or whatever the RACF refresh command is)? > > > >Yesterday I attempted to configure RACF to control access to DFSMS/RM >because of some errors that were being generated in RMSMASTR. Up until >this point, things worked, but I was getting a strange error code that >I've contacted IBM about. But my question to the list is this: > >After working through the instructions on page 42 of the DFSMS/RM >Planning Guide, I am now unable to get VMTAPE to talk to RMS. When >VMTAPE starts, it displays the following errors: > >10:24:50 VMTAPE 000 VMTRMS000I Sending to RMS master: FSMRMQLB DEV >403E >10:24:50 VMTAPE 000 VMTRMS998I CSL Call Info: Returncode= 8 >Reasoncode= 0 >10:24:50 VMTAPE 000 VMTRMS998I RMS Cmd Reply: Returncode= 8 >Reasoncode= 12 >10:24:50 VMTAPE 000 VMTRMS931E RMS error: Request=FSMRMQLB RC=8 >Reason=12. >10:24:50 VMTAPE 000 VMTRMS931E RMS error: Request=FSMRMQLB RC=8 >Reason=12. > >I have defined a RACF generic profile called STGADMIN.RM.* which I >thought would allow VMTAPE (who is a member of the group STGADMIN) to >access tape drives controlled by RMSMASTR. Being new to RACF, I am not >sure if I've missed a step or not. > >Any thoughts or suggestions? > >Thanks in advance, >Dave Keeton
