156 z/VM and Linux on IBM System z: The Virtualization Cookbook for Red Hat Enterprise Linux 6.0
9.1 Formatting DASD for minidisks
In 4.6.2, “Formatting DASD for minidisks” on page 53, DASD was formatted to become
minidisks for the cloner and the golden image. The CPFMTXA command can be used to
format one DASD at a time, but the CPFORMAT EXEC is a wrapper around CPFMTXA that
allows the formatting of multiple DASD.
To have access to enough DASDs to define four more user IDs, LINUX01 - LINUX04, with
two 3390-3 volumes each, eight 3390-3s will be needed. In the examples used in this book,
3390-9s are being used, and two thirds of the 63A9 volume is available. So only two more
volumes are needed: 63AA and 63AB. Consult your worksheets in 2.7.2, “z/VM DASD
worksheet” on page 17 to determine how many volumes you need for four new virtual
machines.
To format DASD for minidisks, perform the following steps:
1. Logon to a 3270 session as MAINT.
2. Query the devices that will be used for the remaining Linux user IDs:
==> q 63aa-63ab
DASD 63AA FR63AA , DASD 63AB FR63AB
3. Attach the volumes to MAINT using the * wildcard:
==> att 63aa-63ab *
63AA-63AB ATTACHED TO MAINT
4. Invoke the CPFORMAT command against these volumes using the as perm parameter:
==> cpformat 63aa-63ab as perm
...
DASD status after:
TargetID Tdev OwnerID Odev Dtype Vol-ID Rdev StartLoc Size
MAINT 63AA MAINT 63AA 3390 UM63AA 63AA 0 10017
MAINT 63AB MAINT 63AB 3390 UM63AB 63AB 0 10017
5. Detach the seven volumes from MAINT with the DETACH command:
==> det 63aa-63ab
63AA-63AB DETACHED
6. Attach the newly formatted DASDs to SYSTEM so they can be used for minidisks:
==> att 63aa-63ab system
DASD 63AA ATTACHED TO SYSTEM UM63AA
DASD 63AB ATTACHED TO SYSTEM UM63AB
The volumes will now be available to be used for minidisks in the USER DIRECT file. They will
also be available after the next IPL because their new labels match the pattern specified by
the User_Volume_Include UM* statement in the SYSTEM CONFIG file.
Commenti su questo manuale