Re: VM directory entry for shared DASD

[Schuh, Richard]

Title: RE: VM directory entry for shared DASD

And do not forget, a vdsk can only be shared between virtual machines running on the same physical VM image and then only if directory defined.   Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]On Behalf Of Shiminsky, Gary - OIT Sent: Wednesday, September 06, 2006 10:28 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VM directory entry for shared DASD I hope this helps   From the z/VM 5.2  Migration Guide   --- snip -----    Note: z/VM supports virtual reserve/release for the virtual disks in storage function. Virtual disks in storage are temporary FBA minidisks simulated in system storage rather than mapped to real DASD. Therefore, a virtual disk in storage may be faster than other minidisks because it avoids the overhead of I/O operations. VSE guests may benefit from this function by using a virtual disk in storage instead of a permanent minidisk to store label information areas and the cross-system communication file (the "lock file"). The virtual disk in storage function may be used by a guest running any supported version or release of VSE.     0I23I      DASD ON cuu NOT PHYSICALLY SHARABLE                                                                                                                         Explanation:  An ADD command with the SHR option was given for                the disk volume at the indicated address. This disk volume is                 attached to a control unit that does not support RESERVE/RELEASE              commands.                                                                                                                                                   System Action:  For data integrity reasons the SHR option is not              reset. The system continues processing.                                                                                                                      Programmer Response:  If the message occurred during system                   start-up by ASI, you may have to correct the applicable IPL proce-            dure to avoid this message in the future.                                                                                                                   Operator Response:  Report this message to your programmer.      Gary Gary L. Shiminsky "It's What I Do!" Wormhole Xtreme Systems & Communications Sciences, Inc At TSG, OIT Services Data Center State of New Hampshire