Philip, The general "best practices" for Linux on System z calls for allocating MDISKs (never whole DASD) to Linux guests under z/VM. In short, that means:
1) CP ATTACH rdev MAINT (attaching the new DASD to MAINT (or any other suitable authorized ID). 2) Run CPFMTXA against that new while volume, formatting labeling the DASD with the label you want z/VM to see, and allocating it all as PERM (0-END PERM) 3) Using whatever directory update process you use, allocate a new MDISK on that new volume (maybe cylinders 1-END if you need that much space). Just don't allocate cylinder zero for actual use (allocate it to some "holding" userid that is never logged on, perhaps something like "$HOLD0$"). 4) If you wish, LINK to that new MDISK R/W and run LXFMT to format it in a manger that Linux will see a Linux filesystem thereon. See LXFMT on the Sine Nomine web site. 5) Attach the new MDISK to your server (or, if you did it right, the server *should* find it the next time it is logged on due to the MDISK statement in its directory entry). 6) Do whatever you need on the Linux server to use the new MDISK. This method allows CP to see the one real device volser, CPFMTXA ensures that a dummy OS VTOC is written to the real volume so that z/OS doesn't write on it, and lets you change Linux volsers (labels) without having to take the DASD offline and online from VM. The Linux guest sees the volser on the cylinder zero where its MDISK begins. There can be many MDISKs on one real DASD, each MDISK with its own cylinder zero. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Philip Hitti" <[email protected]> Sent by: "The IBM z/VM Operating System" <[email protected]> 01/03/2009 01:27 AM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Volume label we cloned several Suse Zlinux machine under Z/vm from the base system by giving the same Mdisk addresses MDISK 1000 3390 DEVNO F010 MR MDISK 1001 3390 DEVNO F011 MR which create duplicate label as 0x1000 and 0x1001. How we can create the differet volume label of the linux machines or change the volume label of linux machines. Philip The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
