We have some non-IBM DASD which is shared R/W by three z/OS guests. To permit the z/OS folks to relabel their DASD any time they wish, the directory entries use the MDISK "DEVNO" operand, looking a bit (changed for ease of understanding) like...
USER NO_LOGON ... ... MDISK A300 3390 DEVNO A300 RV readpw writepw multpw ... USER ZOSSYS1 ... ... LINK NO_LOGON A300 A00 MW ... USER ZOSSYS2 ... ... LINK NO_LOGON A300 A00 MW ... USER ZOSSYS3 ... ... LINK NO_LOGON A300 A00 MW ... That has been working great for many years. But now the wrinkle. Some very clever high-speed z/OS ISV software is issuing some unsupported (by z/VM) CCWs to that DASD. For those CCWs to work, I'll need to define the DASD in SYSTEM CONFIG using the RDEVICE statement to tell CP to keep its mitts off the CCWs as: RDEVICE rdev-rdev TYPE UNSUPPORTED DEVCLASS DASD ... Unfortunately, the doc for the RDEVICE statement relates: "Note: When you define an unsupported device, you must dedicate the device to a virtual machine. To do this, specify the DEDICATE directory control statement in the virtual machine?s directory statement or issue the CP ATTACH command."... One cannot DEDICATE or ATTACH devices to one guest when they need to be shared by all three guests. Have I missed/forgotten some obscure technique to manage this? Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
