Just tried dirmap, and it doesn't seem very useful either: It only knows about 3390 mod 9 and less, but we use 3390 mod 27 and mod 54 devices. Dirmap marks these as extending past the end of the device. Any chance of it catching up with current technology and usage?
-- Robert P. Nix Mayo Foundation RO-OC-1-13 (new loc) 200 First Street SW 507-284-0844 Rochester, MN 55905 ----- "In theory, theory and practice are the same, but in practice, theory and practice are different." -----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Bill Stephens Sent: Friday, November 18, 2005 6:53 AM To: [email protected] Subject: Re: Deleted a VM ID and now trying to restore it DISKMAP is not particularly flexible; its main advantage is that it's free. One of its shortcomings is that it has no way of reporting free space above the last allocated minidisk on a volume. So, DISKMAP would report the space between MDISK 191 3390 100 5 ... and MDISK 291 3390 110 5 ... as free, but it would not report space after the last allocated minidisk as free. To get around this, I defined a $DASD$ userid in the directory which had a 1-cylinder minidisk allocated at cylinder 3339 on all 3390-3 packs. This allowed DISKMAP to report any free space remaining at end-of-volume.
