I'm assuming, from your question, that you do not have a directory that maps your volume.
I've developed a tool for use during disaster recovery exercises called DISCOVER. If you do not have a directory map of your volume, you can run DISCOVER to at least learn where your minidisks are. Then, by using the output from ICKDSF, which will show you the system areas of the pack, you can get a pretty good idea of what's where, without a directory. If you want, I'll send you the tool. In principle, all it does is use CP DEFINE MDISK to define a 1 cylinder MDISK at progressively higher cylinder numbers, trying to CMS ACCESS that minidisk. If it works, the results from QUERY MDISK will tell how big CMS thinks the minidisk is supposed to be, and DISCOVER then appends this information to a map file, the information being the CMS volser, the starting cylinder, and the size of the minidisk. DISCOVER also has the option to redefine the minidisk at its correct size so it can be used. Handy if you need to discover where MAINT 190 or the parm disks are ... It is interesting how often I've had to use this tool after it was built - in one case someone had to recover data from backups of a defunct VM system, and although you could restore the tapes (they were DDR), there was no directory that said where the minidisks were. Were it not for DISCOVER, I couldn't have helped them. Regards, Bill Stephens Sr. Technology Analyst, High Availability SunGard Availability Services 10th floor 401 North Broad Street Philadelphia, PA 19108 Phone: (215) 351-1099 Fax: (215) 451-2045 [EMAIL PROTECTED]
