PAV can be defined at the minidisk level (any size minidisk) by adding a MINIOPT PAVALIAS statement after the MDISK statement... Example:
MDISK 200 3390 2500 50 LX0001 MR MINIOPT PAVALIAS 1200 2200 3200 The virtual machine will now have a 200,1200,2200,3200 all pointing to the same physical disk and each of which can have a single pending i/o. For grins - you can do this with a CMS disk -- but I would not access more than one of the disks at a time. (I'm ignoring the Linux end of this thing with device mapper and multipath support and how it actually makes use of these base and alias addresses - I'm just talking at the virtual guest level here). Scott Rohling On Tue, Feb 1, 2011 at 8:26 AM, Patrick Spinler <spinler.patr...@mayo.edu>wrote: > On 1/31/11 3:27 PM, Mark Post wrote: > > > > If I'm remembering correctly, and z/VM does do all the work with PAV for > minidisks, then 3-4 should be completely transparent to Linux. > > > > I thought I recalled reading that z/VM only used PAV's for access from > multiple guests, that each guest only had a single pending I/O to each > minidisk. :-( Hope I'm wrong. > > -- Pat > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
