MAINT's virtual 405 is also defined in USER DIRECT. Based on your Q V 405 comment from MAINT, it appears this is some type of system minidisk on real volume 540W01. This is most likely an expected CMS disk for the system and is NOT a minidisk you probably want your Linux guest to access.
There is no relationship - in most case - between virtual addresses across
different VMs like MAINT and LINUX1. MAINT has a large number of virtual
addresses related only to system administration. Also, in most cases,
there is no relationship between real/physical addresses and guest virtual
addresses like 0405.
For your LINUX1 guest, VADDR 191 is 50 cylinders (1-50) which is probably a
bit large for a Linux 191 CMS disk. The reason your original VADDR 100
failed at logon was because you exceeded the length of the 3390-3 MV0405
(51 + 3338 cyls). VADDR 101 appears to be a full pack minidisk covering
all of MV0406.
You need to MAP MV0405 to find out what space is available for VADDR 100
after your 191 minidisk and any other minidisks on that volume. That map
should show that cyls 51-156 are available for VADDR 100. If you want to
allocate MV0405 as a full pack minidisk to LINUX1, you will need to move
the VADDR 191 to another volume and then define VADDR 100 the same as VADDR
101 - 0001 for 3338 on MV0405.
Jon Nolting - System z IT Architect (zITA)
IBM US West IMT based near Seattle
(206) 587-2244 (Work) - T/L 277-244
(425) 281-5750 (Cell)
(206) 587-2244 (Fax)
(425) 222-7969 (Home)
From: Kok Leong Chan <ch...@sg.ibm.com>
To: LINUX-390@VM.MARIST.EDU
Date: 02/01/2009 07:59 PM
Subject: Re: Missing DASD cylinders. DASD corrupted?
Sent by: Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
Hi,
Thanks Dave (Jonathan and Bernie too) for the hints. Yes, you're all
correct, I do have a virtual/real address issue.
But something about this still escapes me:
As the MAINT user, I have a virtual dasd at 0405:
q v 405
DASD 0405 3390 540W01 R/W 156 CYL ON DASD 0403 SUBCHANNEL = 003
I also have a real dasd at 0405 and the volume serial is MV0405:
q dasd details 0405
0405 CUTYPE = 2107-E8, DEVTYPE = 3390-0A, VOLSER = MV0405, CYLS = 3339
CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY
-SUBSYSTEM Y Y Y - N N
-DEVICE Y - - Y N N
DEVICE DETAILS: CCA = 65, DDC = --
DUPLEX DETAILS: --
CU DETAILS: SSID = 0085, CUNUM = 0001
Now in the USER DIRECT entry for user LINUX1, there's a MDISK for virtual
DASD 100:
USER LINUX1 LINUX1 1024M 1024M g
INCLUDE LINDFLT
MDISK 191 3390 0001 050 MV0405 MR READ WRITE MULTIPLE
MDISK 100 3390 0051 3338 MV0405 MR READ WRITE MULTIPLE
MDISK 101 3390 0001 3338 MV0406 MR READ WRITE MULTIPLE
When I logon as LINUX1, I see this:
LOGON LINUX1
00: HCPLNM1151E LINUX1 0100 has not been linked because it is not within
CP volme extents.
And guest LINUX1 won't have a virtual DASD at 100.
After some testing, virtual DASD 0100 will link when I set the cylinder
range to be 51 to 156 instead.
It seems that LINUX1 doesn't get the real DASD 0405 but the virtual DASD
0405 instead.
Am I missing something?
Chan K. L.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
