Definitely NOT trying to inspire another "I remember when all we had
were zeroes to bang together, because ones hadn't been invented yet!"
conversation, but... I learned to despise VOLSERs associated with real
device addresses when I was still too young to legally buy my own beer.
It seemed like a great idea at first, but entropy - in the form of
recalcitrant hardware and intractable operations staff - conspired with
physically removable / relocatable 3330 disk packs to make a special
kind of hell.
RDEV addresses in volume labels? "Don't touch it. It's evil!"
Stick with something that associates the volumes with their intended
purpose, instead of the rdev address. Except when you're plugging in
your IPL address, and perhaps other rare special occasions, you really
shouldn't ever have to *care* what the rdev address is.
Here endeth the rant...
-dan.
*From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu]
*On Behalf Of *Mark Pace
*Sent:* Wednesday, July 28, 2010 9:21 AM
*To:* IBMVM@LISTSERV.UARK.EDU
*Subject:* Re: Dasd Volser standards documented
And with the ease of copying DASD via Flashcopy, I move volumes from
device to device for various reasons, VOLSERs
