This is what the 6.1 CMS Admin and Planning says: A single CMS file can contain up to approximately (231-1)-132,000 disk blocks of data, grouped into as many as 231-1 logical records, all of which must be on the same minidisk
2**31 = 2147483648 So: (2147483648-1) - 132,000 = 2,147,351,647 With 512 byte blocks - this should be around 1TB ... though it depends on the logical record length.. Glad you found a workaround.. just trying to understand limits. Seems CMSDDR is likely the one with limits. Scott Rohling On Tue, Jul 12, 2011 at 7:48 AM, Smith, Wayne H Mr CTR DISA CDB12 < wayne.smith....@csd.disa.mil> wrote: > I believe I've found a solution to my problem. I've defined 4 "small" > MDISK overlays on the 17G MDISK; each section can be CMSDDRed. I assume > I was running into some type of CMS file size restriction. I don't > really need to know what the restriction is/was. I can accomplish my > task by splitting up the MDISK. > > > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On > Behalf Of Victor Ochoa Avila > Sent: Tuesday, July 12, 2011 2:14 > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: CMSDDR failing > > Hi Wayne, I've used PIPEDDR in 10GB MDISK and work fine, no problem. > > Download the new version of here > > > > http://www.vm.ibm.com/download/packages/ > > It is a great tool of Bruce Hayden. > > > Regards > > ATTE > > Victor Hugo Ochoa Avila > BBVA America > Mexico D.F > > > 2011/7/11 Scott Rohling <scott.rohl...@gmail.com> > > > Sorry - I meant that 512*2097152 = 1073741824 .. > which is the real block count when starting at 0 > > Exactly 1 gigabyte... > > > Scott Rohling > > > On Mon, Jul 11, 2011 at 4:21 PM, Scott Rohling > <scott.rohl...@gmail.com> wrote: > > > I'm wondering if CMSDDR has some kind of internal limit > of 1G.. I notice that: > > > 512*2097151=1073741824 (512 byte blocks) > 1024*1024*1024=1073741824 (1K cubed) > > Scott Rohling > > > > On Mon, Jul 11, 2011 at 4:06 PM, Smith, Wayne H Mr CTR > DISA CDB12 <wayne.smith....@csd.disa.mil> wrote: > > > > > I'm having issues using CMSDDR. The output is > copied below. Any thoughts? > > The device I'm CMSDDRing is an MDISK defined on > an EDEV. The size of the MDISK is 17 gig. > > I *can* use CP DDR to copy the MDISK to another > MDISK of equal size defined on the same EDEV. I ran CP DDR because the > error message seemed to imply that there was an I/O error reading the > input device(A497). CP DDR could read the entire MDISK so I believe the > error message is misleading. > > > > A couple random pieces of information: > > - We are running z/VM 5.4; CMS Level 24, > Service Level 002 > > - I've used CMSDDR to create CMS files from > other smaller MDISKs defined on the same EDEV. > > - The MDISK on which I'm trying to create > the new file is larger than the MDISK I'm trying to CMSDDR. > > - I've tried CMSDDR with a small and large > (2 gig) virtual machine size. > > - The CMSDDR invocation which fails does > create a file on the target MDISK. I believe it contains blocks > 0-2097151. > > > > cmsddr dump a497 temp xxxx z > > > > z/VM DASD DUMP/RESTORE PROGRAM > > HCPDDR696I VOLID READ IS LXA497 NOT VOLSER > > DUMPING LXA497 > > DUMPING DATA 07/11/11 AT 20.42.35 GMT FROM > LXA497 > > INPUT BLOCK EXTENTS OUTPUT BLOCK > EXTENTS > > START STOP START > STOP > > HCPDDR705E I/O ERROR A497 IRB 00000000 000311D0 > 0E000000 00000000 00000000 > > SNS 80000000 00000004 00000000 00000000 00000000 > 00000000 00000000 00000000 > > CCW 63031820 40000010 > > INPUT 000002097152 OUTPUT 000002097152 > > 00000000 02097151 00000000 > 02097151 > > END OF DUMP > > BYTES IN 1073829304 BYTES OUT 0020546574 > > BLOCKS NOT COMPACTED ON TAPE - 0000000000 > > END OF JOB > > Ready(00004); T=0.80/1.42 16:42:54 > > > > > > > > > -- > Victor Hugo Ochoa Avila > z/OS & z/VM systems programmer > Mexico, City. >
