Friends:
In EXTENT CONTROL, we need to define START and SIZE of the region.
So, if the dasd have 6678 cylinders in total, and you skip the cylinder
zero, remains 6677 usable cylinders (from 1 with 6677.
The entry must be: LX6008 VC6008 1 6677 3390-06
Regards,
______________________________________________
Clovis
From:
Kris Buelens <kris.buel...@gmail.com>
To:
IBMVM@listserv.uark.edu
Date:
25/05/2011 12:24
Subject:
Re: dirmaint volume problem
Sent by:
The IBM z/VM Operating System <IBMVM@listserv.uark.edu>
I don't see a real problem for sure: VCONTROL files are for DIRMAINT's
internal use. What do you get with "DIRM USED volser" and "DIRM FREE
volser". And, if you changed the EXTENT CONTROL, did you issue DIRM RLDE?
And, these days a "3390 model" is something artificial, it is just used to
define a DASD with some "well known" number of cylinders: n*1113. And,
for your case: a 3390 model 6 never existed as a real thing in the past
(as opposed to model 1, 3 and 9)
Where I think I do see some problem is the end-cylinder. CP responds it
has 6678 cylinders, that is from cylinder 0 through 6677. When looking at
the EXNENT CONTROL file entries, I think you tell DIRMAINT the last
cylinder is 6678. An MDISK that would include this cylionder would not be
LINKable.
2011/5/25 Levy, Alan <al...@doitt.nyc.gov>
I have volumes in the volume extent file which lists the type as 3390-6.
LX6008 VC6008 1 6678 3390-06
LX6009 VC6009 1 6678 3390-06
The VC6008 VCONTROL file shows:
DEVTYPE= 3390-06
MAXBLK= 6678
ARCH= CKD
EXCLD= 0 6678 DIRECTP A30B *
The VC6009 VCONTROL file shows:
DEVTYPE= 3390
MAXBLK= 1112
ARCH= CKD
EXCLD= 0 1112 DIRECTP A20C *
I issued Q DASD xxx details and here is the output:
A30B CUTYPE = 2107-E8, DEVTYPE = 3390-0C, VOLSER = VC6008, CYLS = 6678
CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY
-SUBSYSTEM Y Y Y - N N
-DEVICE Y - - Y N N
DEVICE DETAILS: CCA = 0B, DDC = --
DUPLEX DETAILS: --
CU DETAILS: SSID = A003, CUNUM = A300
A20C CUTYPE = 2107-E8, DEVTYPE = 3390-0C, VOLSER = VC6009, CYLS = 6678
CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY
-SUBSYSTEM Y Y Y - N N
-DEVICE Y - - Y N N
DEVICE DETAILS: CCA = 0C, DDC = --
DUPLEX DETAILS: --
CU DETAILS: SSID = A002, CUNUM = A200
When I look thru the CPFMTXA allocate list it shows both correctly as
mod-6. How do I get the VC6009 dasd to show correctly as a mod-6 and not a
mod-1 ? Why does the vcontrol file show DEVTYPE= 3390 and not DEVTYPE=
3390-06 ?
Thanks.
Alan Levy
VM/Linux Administrator
NYC Department of Information
Technology and Telecommunications
718-403-8020
--
Kris Buelens,
IBM Belgium, VM customer support
