z/VM is differen: there is no VTOC on the disk that describes its contents. Minidisk definitions only exist in the CP directory, so if you don't have that, you must to techniques like Rob suggests. If you'd still have the object directory (as opposed to the source directory that is a CMS file), then there is the DIRENT tool on the VM download library that can somehow reconstruct a source directory form the object.
I would still use DEFINE MDISK, even is that gives a R/W minidisk: be sure to use "ACCESS vdev Z/Z". By using Z/Z as accessmode, CMS will use the disk in R/O mode. 2010/11/17 Brian France <b...@psu.edu> > 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... > -- > > -- > > Brian W. France > Systems Administrator (Mainframe) > Pennsylvania State University > Administrative Information Services - Infrastructure/SYSARC > Rm 25 Shields Bldg., University Park, Pa. 16802 > 814-863-4739 > b...@psu.edu > > "To make an apple pie from scratch, you must first invent the universe." > > Carl Sagan > -- Kris Buelens, IBM Belgium, VM customer support
