Thanks to everyone for their help; The OPERATIONS auth or using OPTION LNKNOPAS with the ESM deferring to CP seems like the easy way to give VMBACKUP what it needs.
-------------------------------------------------------- This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens Sent: Thursday, December 29, 2005 4:54 AM To: [email protected] Subject: Re: VMBACKUP with RACF question With the SEPCIAL authorisation, you don't get access to all resources, but, you can give yourself any authorisation you like... (or change any other RACF setup) The OPERATIONS attribute is what VMBACKUP needs: RAC ALU VMBACKUP OPERATIONS. When a user with OPERATIONS accesses a resource, RACF will write a record in its SMF logfile, so be prepared for the log disks to fill quicker. But, as you say you gave VMBACKUP R/O access to all minidisks, VMBACKUP won't be able to restore to minidisks. RACF uses the most restrictive permission: so if an explicit permission for VMBACKUP exists, RACF uses that, if not, RACF will find the OPERATIONS attribute and grant R/W permission. Kris, IBM Belgium, VM customer support
