I don't know about the reserve/release part, but when I was a VSE sys.prog. I also had one userid owning the mdisks
and all users linked to that mdisk-owning-user.
Steve G.
| Bill Stephens <[EMAIL PROTECTED]>
Sent by: VM/ESA and z/VM Discussions <[email protected]> 01/31/2006 02:23 PM
|
To: [email protected] cc: Subject: Re: MDISK versus LINK |
FWIW, we've always built the directories for our customers who recover
under VM with a DASD userid owning all the MDISKs, and all other guests
LINK to DASD. When you're recovering MVS (don't know about VSE) you have
to do it this way if you want virtual reserve/release to work (as Steve
Frazier pointed out).
What are the advantages, aside from possible job security, of defining all
MDISKs for every instance of a pack? Sounds like a pointy-haired-boss
decision to me ...
Regards,
Bill Stephens
Sr. Technology Analyst, High Availability
SunGard Availability Services
10th floor
401 North Broad Street
Philadelphia, PA 19108
Phone: (215) 351-1099
Fax: (215) 451-2045
[EMAIL PROTECTED]
___________________________________________
Keeping People and Information Connected (TM)
http://www.availability.sungard.com
