Hello Everyone,
We do use the last 3 digits example DS6900 is real dasd 0900.
But the naming convention has to be set my your sites standards and
balanced against what you need and what you do with your DASD.
In our case, we make sure that
Operators/Applications/Systems/CE/outside IBM VMer's/etc. can come in
and look to see where
All dasd are and where they are connected.
And yes YMMV!
Ed Martin
Aultman Health Foundation
330-363-5050
ext 35050
From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of Mark Pace
Sent: Wednesday, July 28, 2010 9:21 AM
To: [email protected]
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 with the device address
does not work for me.
YMMV.
On Wed, Jul 28, 2010 at 9:06 AM, Rob van der Heij <[email protected]>
wrote:
On Wed, Jul 28, 2010 at 2:52 PM, Michael MacIsaac <[email protected]>
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
