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
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
CP_Owned Slot 6 UP6285<br />
CP_Owned Slot 7 UP6286<br />
CP_Owned Slot 8 UP6287<br />
CP_Owned Slot 9 RESERVED<br />
CP_Owned Slot <strong>10</strong> RESERVED<br />
CP_Owned Slot 11 RESERVED<br />
...<br />
► Move down to the User_Volume_List section. User volumes (PERM) can be specified<br />
individually with the User_Volume_List statement, or with wild cards using the<br />
User_Volume_Include statement. If you are using the labelling convention en<strong>for</strong>ced by the<br />
CPFORMAT EXEC and no other LPAR will be using the same volumes with the same prefix,<br />
then add the following single line to include all PERM space as volume labels all begin<br />
with UM6.<br />
====> /user_v<br />
/**********************************************************************/<br />
/* User_Volume_List */<br />
/* <strong>The</strong>se statements are not active at the present time. <strong>The</strong>y are */<br />
/* examples, and can be activated by removing the comment delimeters */<br />
/**********************************************************************/<br />
User_Volume_Include UM6*<br />
/* User_Volume_List USRP01 */<br />
/* User_Volume_List USRP02 */<br />
...<br />
====> file<br />
Important: If other z/<strong>VM</strong> LPARs might be attaching volumes with the UM prefix, you<br />
should specifically list each volume to be attached to SYSTEM using the User_Volume_List<br />
statement. This will prevent the possibility of multiple z/<strong>VM</strong> systems writing to the same<br />
volume. In this example, the list would be:<br />
User_Volume_List UM6289<br />
User_Volume_List UM6290<br />
User_Volume_List UM6293<br />
User_Volume_List UM6294<br />
User_Volume_List UM63A2<br />
► Save your changes with the FILE subcommand. Verify the integrity of the changes with the<br />
CPSYNTAX command:<br />
==> acc 193 g<br />
==> cpsyntax system config f<br />
CONFIGURATION FILE PROCESSING COMPLETE -- NO ERRORS ENCOUNTERED.<br />
► When you have confirm there are no syntax errors, put the MAINT CF1 disk back online.<br />
<strong>The</strong> following example shows how you did this previously:<br />
==> rel f (det<br />
DASD 0CF1 DETACHED<br />
==> cpacc * cf1 a<br />
CPACCESS request <strong>for</strong> mode A scheduled.<br />
HCPZAC6732I CPACCESS request <strong>for</strong> MAINT's 0CF1 in mode A completed.<br />
==> q cpdisk<br />
Label Userid Vdev Mode Stat Vol-ID Rdev Type StartLoc EndLoc<br />
MNTCF1 MAINT 0CF1 A R/O 6<strong>10</strong>RES 0200 CKD 39 83<br />
MNTCF2 MAINT 0CF2 B R/O 6<strong>10</strong>RES 0200 CKD 84 128<br />
MNTCF3 MAINT 0CF3 C R/O 6<strong>10</strong>RES 0200 CKD 129 188<br />
54 <strong>The</strong> <strong>Virtualization</strong> <strong>Cookbook</strong> <strong>for</strong> RHEL 6