Are you sure the VC6009 doesn't appear twice in EXTENT CONTROL? Running DIRM RLDE again can't harm, so do it and then look again at DIRM FREE & USED You could also make DIRMAINT surely rebuilf te VCONTROL file: DIRM CMS LISTFILE VC6009 VCONTROL * then DIM CMS ERASE VC6009 VCONTROL x (where x is the filemode reported by the LISTFILE) and DIRM RLDE to have it recreate the VCONTROL file(s).
And indeed you should code *LX6008 VC6008 1 6677 3390-06* Currently DIRMAINT thinks these disks have 6679 cylinders.... 2011/5/25 Levy, Alan <al...@doitt.nyc.gov> > The dirm used shows: > > > > OwnerUid VDev SYSAFFIN Type Start Size VOLSER Notes > > > DIRECTP A30B * 3390-06 0 6679 VC6008 Excluded > Entry > > > > OwnerUid VDev SYSAFFIN Type Start Size VOLSER Notes > > > DIRECTP A20C * 3390 0 1113 VC6009 Excluded > Entry > > > > The dirm free shows: > > > > VOLUME DEVTYPE -------------- FREE EXTENTS --------------- > > VC6008 3390-06 START= 1 AVAIL= 6678 > > > > VOLUME DEVTYPE -------------- FREE EXTENTS --------------- > > VC6009 3390 START= 1 AVAIL= 1112 > > > > When I added these packs a long time ago, I issued the dirm rlde command. > > > > While the models are artificial, I specify *DASDType Max-Size 3390-06 6679 > in the default section of the extent file. > > Are you saying that all of my mod-6 extent records should say > > > > *LX6008 VC6008 1 6677 3390-06* > > And my default should be 6678 ? > > > > > > *Alan Levy* > > *VM/Linux Administrator* > > *NYC Department of Information* > > *Technology and Telecommunications* > > *718-403-8020* > > > > > > *From:* The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] *On > Behalf Of *Kris Buelens > *Sent:* Wednesday, May 25, 2011 11:24 AM > *To:* IBMVM@LISTSERV.UARK.EDU > *Subject:* Re: dirmaint volume problem > > > > 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 > -- Kris Buelens, IBM Belgium, VM customer support
