I know that I'm probably in the minority here, but I like to use the MDISK vdev 3390 DEVNO rdev md rp wp mp
statement, which allows one to map a volume's virtual address to its real address as the DEDicate statement does, but makes it clearer which address is which, and as a side benefit allows sharing the volume if desired. I use the more conventional MDISK statement only when mapping minidisks. J. Leslie Turriff VM Systems Programmer University of Central Missouri Room 400 Ward Edwards Building Warrensburg MO 64093 660-543-4285 660-580-0523 [EMAIL PROTECTED] >>>Ray Mansell <[EMAIL PROTECTED]> 10/31/06 1:42 pm >>> It's hugely more difficult to map (and keep consistent over time) virtual addresses onto real ones, one to one, than it is to determine on which real volume a particular guest's minidisk resides. Ray Mansell Mike Lovins wrote: >The main reason I asked the question was because my Z/VM specialist does not want to keep track of virtual address. He said that when a virtual drive 0750 has a problem it is harder to trackdown which one is really having a problem. I thank he doesn't need to worry about that because the device will call IBM or Hatachi or whom ever and tell them which device is having the problem... ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
