And with the ease of copying DASD via Flashcopy, I move volumes from device to device for various reasons, VOLSERs with the device address does not work for me.
YMMV. On Wed, Jul 28, 2010 at 9:06 AM, Rob van der Heij <rvdh...@gmail.com> wrote: > On Wed, Jul 28, 2010 at 2:52 PM, Michael MacIsaac <mike...@us.ibm.com> > wrote: > > > In the Virtualization Cookbooks, some of which are Redbooks and thus "IBM > > documents", we recommend using the last four characters of the volser as > the > > DASD rdev. If this convention is followed it guarantees unique labels and > > makes it easy to know which DASD is which. But that leaves only two > > That's definitely not the "old school tradition" where we were told to > avoid volser based on real device address. You'd name the volume after > the data or purpose, not on where it is sitting. Today it's probably > less common to find a volume restored on another HDA when you get back > in the office. Since your approach probably will have exceptions too, > you'll have to use the right info anyway (rather than code 'DETACH' > substr(volser,2) for example - the "lookup" stage is your friend for > that...) > > | Rob >
