My customer didn't share PPRC with z/OS, but used it with Tetragon controller and more recent with DS8000. No problems what so ever. The DS8000 itself was shared with z/OS, but we got separate address ranges for z/VM, that z/OS didn't see, and we didn't see the z/OS dasd. But, I can imagine that suspend/resume functions require address to be offline in other systems than where the command is executed. Anyhow, I wouldn't like when z/OS storage admins started playing with suspend/resume of my VM disks, nor vice versa, that's one reason not to put each-other's devices online all the time.
2008/11/25 Kline, Martin <[EMAIL PROTECTED]>: > I am installing z/VM for the first time in many years. We currently have a > z/OS sysplex and want to put z/VM on some of the same DASD. > > I followed the initial install, creating the res, page, spool and work > volumes, then left the z/VM system up. > > The next morning the storage admins complained that all of their PPRC > suspend and resume processing failed. Until z/VM was dropped, the PPRC > functions failed. > > The solution recommended by several people on IBM-MAIN was to mark all of > the PPRC devices 'notsupported' in z/VM. > > The documentation indicates PPRC is fully supported by z/VM and its > guests, but if the support is that every PPRC device must be > marked 'notsupported', I'd have to say that's a contradiction. Similarly, > there is nothing in the documentation about having to do anything special > when sharing DASD - such as marking the devices 'notsupported' - before > starting z/VM. > > Researching the archives, it appears some people are successfully using > PPRC with z/VM. > > Is anyone sharing PPRC volumes between z/VM and z/OS systems, and if so, > what steps do I need to take? > -- Kris Buelens, IBM Belgium, VM customer support
