If its just DASD, define it as a full volume minidisk owned by a userid, and CP LINK to it. Then you can stick to priv class G.
Ray Mrohs Energy Information Administration U.S. Department of Energy -----Original Message----- From: Alan Altmark [mailto:[EMAIL PROTECTED] Sent: Friday, March 18, 2005 10:17 AM To: [email protected] Subject: Re: CPINT Question On Friday, 03/18/2005 at 07:46 MST, Dave Myers <[EMAIL PROTECTED]> wrote: > Thanks for quick responses. > Adding CLASS B to the linux guests did the trick. Hopefully you have hardened the Linux guests so that you trust them to have class B. Maybe it would be better if the Linux guest HCP MSG'd a server that would ATTACH the requested device (if authorized) to the requestor. Or follow Neale's advice and move ATTACH to a different priv class and have PROP monitor the operator's console to make sure the guest is attaching only what you think it ought to. Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
