A minidisk is a continuous range of cylinders on a real disk, that the guest 
sees as a virtual disk. For example, the meaning of this:
MDISK 700 3390 0001 10016 MM2101

700 - this is the virtual address of the minidisk as seen by the Linux guest
3390 - this is the type of the real disk that the minidisk is on
0001 - The minidisk starts at cylinder 1 of the real disk on which it is located
10016 - The minidisk is 10016 cylinders long
MM2101 - this is the volume serial of the real disk that the minidisk is on.

More info about the MDISK directory statement is here:

http://publib.boulder.ibm.com/infocenter/zvm/v6r2/topic/com.ibm.zvm.v620.hcpa5/dmdisk.htm?resultof=%22%6d%64%69%73%6b%22%20

If you do not have a directory maintenance product (e.g. DIRMAINT or 
VM:Director), then in general case, you have to find gaps in free space by 
hand. But in your case it looks like your minidisks span the whole real disks 
(but I'm just guessing from the size):
MDISK 700 3390 0001 10016 MM2101
MDISK 701 3390 0001 10016 MM2201
So you may have an easier job of finding free real disks and assigning them 
from cyl 1 to the end as minidisks for the Linux guests.

HTH 
Tomas


-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Cameron 
Seay
Sent: Friday, February 15, 2013 4:07 AM
To: [email protected]
Subject: Allocating DASD to new users.

I am trying to copy either of these guests and replicate them for a class I am 
teaching:

USER LINUX001 LINUX001 1G 4G G
INCLUDE LNXDFLT
CPU 00
CPU 01
NICDEF F000 TYPE QDIO DEV 3 LAN SYSTEM VSWITCH1 MDISK 191 3390 0001 150 MM2001 
MDISK 700 3390 0001 10016 MM2101 MDISK 701 3390 0001 10016 MM2201 MDISK 900 
FB-512 V-DISK 409600 MR
*
******************************
*
USER LINUX002 LINUX002 1G 4G G
INCLUDE LNXDFLT
CPU 00
CPU 01
NICDEF F000 TYPE QDIO DEV 3 LAN SYSTEM VSWITCH1 MDISK 191 3390 0301 150 MM2001 
MDISK 700 3390 0001 10016 MM2104 MDISK 701 3390 0001 10016 MM2204 MDISK 900 
FB-512 V-DISK 409600 MR

My question: Disks 191 and 900 are exactly  the same for both users. For disks 
700 and 701, the disks where Linux is going to live, the disks are different 
slightly in their labeling: 700 is MM2101 on for user LINUX001 AND MM2104 for 
user LINUX002, etc.  I know how to use DISKMAP somewhat. But I'm not completely 
clear about how to apportion DASD for these users. I sure don't want to 
overwrite an address and I know DISKMAP will warn you about overlaps but I 
would hate to mess up the addressing. I was with the VM sysprog when he defined 
these, but I forgot exactly what I'm supposed to do.  Do I find more minidisks 
labeled MMxxxx and assign them sequentially in DISKMAP?  I have never allocated 
DASD before. I am going to need about
30-40 guests and I have the DASD for it.

Thanks!


--
Cameron Seay, Ph.D.
Department of Computer Systems Technology School of Technology NC A & T State 
University Greensboro, NC
336 334 7717 x2251

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit http://wiki.linuxvm.org/

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to