27.12.2012 Views

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

2.2.2 Backup file naming convention<br />

It is recommend that you keep copies of important z/<strong>VM</strong> and Linux configuration files. You<br />

should always keep copies of original configuration files in case you need to go back to them.<br />

Since z/<strong>VM</strong> file names are limited to 16 characters (eight <strong>for</strong> the file name and eight <strong>for</strong> the file<br />

type), only the last four characters of the file type are used. This often requires some<br />

characters to be overwritten. For the original file, the suffix ORIG is used, and <strong>for</strong> the most<br />

recent working copy, the suffix WRKS (<strong>for</strong> “it WoRKS”!) is used. For example, the original USER<br />

DIRECT file is copied to the file USER DIREORIG be<strong>for</strong>e it is modified the first time.<br />

2.2.3 <strong>The</strong> command retrieve convention<br />

2.3 Disk planning<br />

<strong>The</strong> ability to retrieve past commands is a common tool. Often it is nice to retrieve in both<br />

directions in case you “pass” the command you’re looking <strong>for</strong>. <strong>The</strong> default Linux shell, bash,<br />

does this by default with the up arrow and down arrow keys.<br />

<strong>The</strong>re is a convention in z/<strong>VM</strong> to use the F12 function key (labeled PF12 on physical 3270<br />

devices) to retrieve the last command, though it is not defined to all user IDs. <strong>The</strong>re is no<br />

convention retrieve commands in the other direction but it is possible to set another key to<br />

that function. <strong>The</strong>re<strong>for</strong>e, F11 is used to retrieve <strong>for</strong>ward since it is right next to F12. Also, the<br />

same function is useful in the editor, XEDIT. <strong>The</strong> ? subcommand retrieves past commands, so<br />

it is recommended that you assign it to F12.<br />

<strong>The</strong>re are different aspects to consider when planning how to choose and allocate disk<br />

storage. Some aspects include the following<br />

► Conventional ECKD DASD vs. FBA disks over SCSI/FCP<br />

► 3390-3s vs. 3390-9s or large disk support<br />

► Amount of disk storage per Linux image and how to allocate file systems<br />

DASD vs. SCSI/FCP<br />

This book describes how to use conventional ECKD DASD and does not discuss FBA disks<br />

accessed over SCSI/FCP. This is not because either technology is superior, but simply<br />

because DASD seems to be much more common than SCSI/FCP disks. If you were to use<br />

SCSI/FCP disks, cloning with the clone.sh script would have to be modified to account <strong>for</strong><br />

World Wide Port Names and Numbers. Sometimes a combination of these two types of disk<br />

storage is used - when that is the case the ECKD emulated DASD is often used <strong>for</strong> the root<br />

file system and SCSI/FCP disks are used <strong>for</strong> large data storage areas.<br />

3390-3s vs. 3390-9s<br />

Emulated 3390-3s <strong>for</strong>mat to about 2.3GB, while 3390-9s are three times the size or about<br />

6.8GB. Either size will work, though 3390-3s have been recommended over 3390-9s by some<br />

per<strong>for</strong>mance analysts. This book describes mainly using 3390-3s, however, comments are<br />

added where using 3390-9s differs - especially with installing z/<strong>VM</strong>.<br />

Disk storage per Linux image<br />

Disk storage has the following characteristics<br />

<strong>10</strong> <strong>The</strong> <strong>Virtualization</strong> <strong>Cookbook</strong> <strong>for</strong> RHEL 6

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!