There's also DITTO.

-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf 
Of Rob van der Heij
Sent: November 17, 2010 15:43
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: A how to ?...

On Wed, Nov 17, 2010 at 9:32 PM, Brian France <b...@psu.edu> wrote:
> Folks,
>      Our storage folks have come across a dasd volume that apparently by
> it's name was one of our VM volumes. Now, none of my 3 vm's have this volume
> on line and I would like to just have a look see as to what was on the
> volume. Is there a utility to do this? We have Vmdirect but I don't believe
> by adding this volume into the pool a map is going to give me anything since
> no users have it. IF this was z/OS, I would simply use ISPF 3.4 to list the
> contents of the volume and this is what I was wondering about, it something
> like that existed in z/VM. Maybe this is something that can't be done due to
> the nature of it all. Thanx in advance...

This is VM, anything can be done ;-)

With DDR (or "trackread" in CMS Pipelines) you can see the virtual
cylinder number. If you would scan the entire pack cylinder by
cylinder, it would nicely show you where the mini disks were. If it's
a CMS mini disk, the VOL1 record has the number of cylinders that CMS
had, and you can normally skip the rest of that mini disk in your
scan.

Alternatively, you can DDR real cylinder 1 to a small T-disk and try
ACCESS to have CMS tell you what was there. That information gives you
the amount to increment your cursor and try the next disk. I've also
seen people use DEF MDISK but I like it less because it goes R/W...

| Rob


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.

Reply via email to