> > As far as the volume labels are concerned, there are programs (DDR, > ICKDSF, etc.) that verify the label before destroying the disk, so the label > isn't all that onerous. >
I never said that label should be dropped. It keeps from having to create a Windows Registry to record identifying > information. That central area where the DEVDESC information that you ask > for is stored is likely to become just such an area. > Windows what?? I am a Mac person. :-) Mac has a "properties" directory and there's nothing wrong with that. And there are many other properties of devices apart from name/description that can be classified as registry entries. For example, we are in the process of upgrading our DASD. We have thousands > of disks that must be copied. Any shop that moves things around for whatever > reason is likely to have problems with the DEFINE command changes you > suggest. > ?? But you won't use DEFINE for moving DASD. You are going to move to a lower address range if you can and then even disk labels can remain the same (or use offline/online in SYSTEM CONFIG). And If you move minidisks, then a minidisk called "My Sandpit" should still be called "My Sandpit". Ivica
