One more voice in the chorus of those who despise using the rdev in the volser of any disks except for spare packs. Here, the storage management folks do a dasd refresh every two years. When they init the packs that are to belong to VM, they are given volsers of the form VMrdev. When I copy the packs that are in use, I can easily determine the use of any given disk in the farm because all of the used dasd have volsers that are comprised of a mnemonic prefix and a sequence number.
Regards, Richard Schuh ________________________________ From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Michael MacIsaac Sent: Wednesday, July 28, 2010 5:53 AM To: [email protected] Subject: Re: Dasd Volser standards documented Phil, > I was wondering if there was an IBM document which gave suggestions > for DASD volser conventions and/or limitations. 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 characters. The first character is recommended to signify the LPAR. The second character is recommended to be the function of the DASD: S for spool, P for page, M for minidisk, V for VM (or CP Owned) and T for temporary disk. This system has worked fairly well for us on our own systems, but of course is not perfect. Hope this helps. "Mike MacIsaac" <[email protected]> (845) 433-7061
