I wrote a REXX program that reads through a disk (any disk that can be attached or linked to a CMS vm) and reports what is finds. i.e. VOL1 labels, CMS1 labels, CMS files, gaps between labels, overlaps etc. It is not the first defense, but I find it helpful to answer the question 'What's On MY Disk?'. I summited it to the VMWORKSHOP, I don't know if it has been uploaded yet to their tools page. It's called WOMYD (What'sOnMYDisk).
If not you can contact me and I'll give it to you. Tom On Sun, Jun 22, 2014 at 11:22 AM, Cameron Seay <cws...@gmail.com> wrote: > That's why I love this forum. When I have a question that on the surface > may appear to be pretty simple, you guys educate me in that with enterprise > technologies, nothing is simple. These answers have been extremely > insightful. The main guy that sets our physical environment up chimed in > and and told me that all is well. He has a storage management strategy > that will streamline these issues. It's just that we had a lot of cooks in > the kitchen. We will fix that. Thanks again! > > > On Sun, Jun 22, 2014 at 2:04 PM, John Campbell <soup...@gmail.com> wrote: > > > Ah, yes, "DASD volumes"... > > > > (chuckles) > > > > I spent a LOT of time doing AIX support-- both before p5 hypervisors and > > after-- so, really, what is a "DASD volume"? > > > > Is it a physical volume? (Which, using a hypervisor, may be mapped into > a > > logical volume, or, via a SAN, is declared "physical" also despite being > > mapped across one-- or more-- actual physical devices.) > > > > Is it a logical volume? A logical volume at the hypervisor level looks > > like a physical volume to the instance which likely contains multiple > > logical volumes. > > > > With the abstraction of "volumes" the way they've been of late, the > word, I > > believe, is becoming more and more ambiguous. > > > > Though, really, the query for free DASD -- "devices" -- implies physical > > volumes. > > > > Mind you, with the expanded use of SANs, all bets are off as to where the > > LUNs really map to. > > > > (sighs) > > > > As we move away from the good old days of 2311s, 2314s, 3330s, 3350s, > when > > someone asks "What is a volume?", I believe the answer, more and more, > > becomes "It depends..." > > > > (smirks) > > > > -soup > > > > > > On Sun, Jun 22, 2014 at 1:46 PM, Mark Post <mp...@suse.com> wrote: > > > > > >>> On 6/22/2014 at 08:37 AM, John Campbell <soup...@gmail.com> wrote: > > > > Ah, yes, so Q DASD FREE will report on free space... but will it > return > > > > CONTIGUOUS free space (ISTR minidisk granularity is in "cylinders")? > > Or > > > > will it just be the count of cylinders (or whatever "granularity" the > > > > device, like FBA, which might not be reported in cylinders) that > > haven't > > > > been allocated somewhere within the knowledge of the z/VM system? > > > > > > That command will only report entire DASD volumes. By definition, any > > > volume that has been used for minidisks is attached to SYSTEM, and will > > not > > > be shown. So, yes, as many contiguous cylinders as the volume > contains. > > > > > > > > > Mark Post > > > > > > ---------------------------------------------------------------------- > > > 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/ > > > > > > > > > > > -- > > John R. Campbell Speaker to Machines souperb at gmail > dot > > com > > MacOS X proved it was easier to make Unix user-friendly than to fix > Windows > > "It doesn't matter how well-crafted a system is to eliminate errors; > > Regardless > > of any and all checks and balances in place, all systems will fail > > because, > > somewhere, there is meat in the loop." - me > > > > ---------------------------------------------------------------------- > > 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/ > > > > > > -- > Cameron Seay, Ph.D. > Department of Computer Systems Technology > School of Technology > NC A & T State University > Greensboro, NC > 336 334 7717 x2251 > > ---------------------------------------------------------------------- > 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/
