Folks, Well whilst its no longer connected to an IBM Mainframe we do have a selection of HDS SAN's 2xAMS and 2xWMS. As some one who has to sort out the mess his boss makes of its config from time to time I can understand the sort of issues that may have resulted in this question. However as Peter has pointed out a given "mini disk" will be be on spread over multiple physical disks. In fact the mapping can be quite complex. On the HDS SAN one defines "Raid Groups" each of which contain several disks in RAID-1, RAID-5 or RAID-10. Each of these is split into one or more SAN LUNs each of which has a number within the SAN. Just to make life interesting multiple SAN LUNs can be combined into a Composite LUN. Each of these SAN LUNs may then be made available to multiple hosts as a HOST LUN. I guess this will map to a physical device on the Mainframe. VM then sub-divides this into MiniDIsks. How you walk back up the chain from a MINI DIsk to a collection of real disks in the SAN will depend on your environment. If you actually have a collection of SANS then its possibly worth looking at some of the third party software that will manage multiple SANS. For example we have HDS HiCommand Storage Services Manager which will produce all sorts of reports, but its Oracle based and the box it runs on is incredibly slow so I find it less that useful. I would expect IBM to have something similar in Tivoli... So its some times "needs must" what I ended up doing in our environment was going into the HDS GUI and dumping the LUN Mapping into a "config file" and then feeding it through a Script File (I used VB Script because that's what most folks understand where I work). The script file produces a CSV file that can be read by a spread sheet or database of your choice. I can then sort this in a number of ways to get out the info I need. You will probably have to do something similar yourself...
Dave G4UGM -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of peter.w...@ttc.ca Sent: 19 January 2010 19:22 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: serial number's In a word I think the answer is NO. In a modern DASD subsystem, you are using RAID of some sort at the device level. This means that any given data is spread across several physical disk volumes, unless a particular file is small enough to fit within one data block on the disk volume. But finding out where it is, and depending on the RAID setup, any other copies, would be impossible except possibly by scanning the physical disks for the data. That's my opinion anyway. Peter -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Gimblet, Tom Sent: January 19, 2010 14:09 To: IBMVM@LISTSERV.UARK.EDU Subject: serial number's Is there a way to identify the storage frame serial number of the minidisk/dasd assigned to a userid. For example userid ABC001 has minidisk 201. What is the serial number of the storage frame minidisk 201 resides? Ideally we would like to have this ability from zLinux (map linux device to storage frame serial) but would be happy if we could do so from CP. Need this capability on IBM, EMC, HDS storage. Thanks Thomas Gimblet 347 643 3194 _____ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot be guaranteed on the Internet. The sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on the basis of information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is property of the TTC and must not be altered or circumvented in any manner.
