On Mon, Jul 28, 2008 at 10:10 PM, RPN01 <[EMAIL PROTECTED]> wrote: > We started this way, but I felt that this made it harder to isolate, list, > or find the LPAR specific minidisks. With them in the same userid, you have > the entire list at hand.
The other motivation for your approach is that you can backup (and restore) the data from any system in the collection. Unfortunately, it means that you need RACF profiles to cover all of your target MDISKs rather than a single one for the 191. If you plan ahead and use a consistent naming scheme, you could use OPERATOR.%191 When you hold the MDISK statements in a separate "owner" userid, you need also RACF to be involved with users going after "their own" disks. That tends to increase the amount of profiles and administrative effort to manage it. Kris' approach with the link mode "R" on the MDISK is better than alternatives like detach of unwanted disks (to avoid race condition during IPL). Also, in XLINK environment you don't want to LINK and DETACH without a reason. -Rob
