The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM
The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM
The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
HCPDIR494I User directory occupies 43 disk pages<br />
Your new directory is online. Do not <strong>for</strong>get the new password!<br />
Note that this XEDIT macro will only work on a vanilla USER DIRECT file because it searches <strong>for</strong><br />
the original user IDs next to passwords. If you want to change your password again, it should<br />
be much easier as you can use the XEDIT CHANGE subcommand. For example to change all<br />
passwords from lnx4vm to vm4lnx, invoke the following commands:<br />
==> x user direct c<br />
====> c/LNX4<strong>VM</strong>/<strong>VM</strong>4LNX/* *<br />
DMSXCG517I 798 occurrence(s) changed on 345 line(s)<br />
Congratulations, your z/<strong>VM</strong> system is now customized and ready <strong>for</strong> Linux. It is<br />
recommended that you back up your system to tape.<br />
4.<strong>10</strong> Backing up your z/<strong>VM</strong> system to tape<br />
Your system is now customized with a running TCP/IP stack, a highly available<br />
VSWITCH, a startup and shutdown process and with a user ID <strong>for</strong> shared files. You have<br />
changed the passwords. This would be a good time to back up the system to tape.<br />
<strong>The</strong>re are five system volumes that should be backed up 6<strong>10</strong>RES, 6<strong>10</strong>SPL, 6<strong>10</strong>PAG, 6<strong>10</strong>W01 and<br />
6<strong>10</strong>W02 (or just the first three if you are using 3390-9s). If you changed the labels of the last<br />
four at install time, then use those labels. You also have configured a sixth volume that is<br />
important to Linux: that is the first 320 cylinders of the volume with LNXMAINT on it.<br />
To backup these volumes to tape, refer to chapter 8. Load the System Image, Step 11.<br />
Store a Backup Copy of the z/<strong>VM</strong> System on Tape in the manual <strong>The</strong> z/<strong>VM</strong> Guide <strong>for</strong><br />
Automated Installation and Service, GC204-6099.<br />
4.11 Relabeling system volumes<br />
In previous books, the z/<strong>VM</strong> installation was described using “standard labels” on the<br />
CP-owned volumes (e.g. 6<strong>10</strong>RES, 6<strong>10</strong>SPL, 6<strong>10</strong>PAG, 6<strong>10</strong>W01 and 6<strong>10</strong>W02). In this book, changing<br />
the last four labels to include the real device address in the last four characters of each label<br />
is recommended (the label of the “res pack”, e.g. 6<strong>10</strong>RES cannot be modified at install time).<br />
This alleviates the possibility that another vanilla z/<strong>VM</strong> system with the same labels is<br />
installed onto volumes accessible by your z/<strong>VM</strong> system. If that happens, it is likely that one of<br />
the systems will not IPL correctly.<br />
To understand this possibility, refer to Figure 4-16 on page 65. <strong>The</strong> z/<strong>VM</strong> system with the<br />
lower device addresses starting at E340 should IPL fine (though you may see a warning at<br />
system startup time about duplicate volume labels). However, if the z/<strong>VM</strong> system starting at<br />
device address F000 is IPLed, the 540RES volume will be used, but the remaining volumes in<br />
the system are searched <strong>for</strong> by volume label, not by device address. Because z/<strong>VM</strong> system<br />
1’s addresses are lower than z/<strong>VM</strong> system 2’s, system 2 will be using system 1’s volumes.<br />
This is not good <strong>for</strong> either system!<br />
64 <strong>The</strong> <strong>Virtualization</strong> <strong>Cookbook</strong> <strong>for</strong> RHEL 6
Change language