Esmie, In the example you provide they use a DATA CISZ of 12288, which will work with an INDEX CISZ of 2048.
In the definition you provided earlier you specify a DATA CISZ of 4096 which cannot work with an INDEX CISZ of 2048, so IDCAMS increases the INDEX CISZ. It's not a mystery; it's the documented behavior. For some reason you don't want to use a very small DATA CISZ then expect to use a larger INDEX CISZ. Either way, DFSMShsm does not care what CISZ is used. It will use whatever CISZ is allocated for the DATA and INDEX extents. Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of > esmie moo > Sent: Tuesday, May 05, 2009 7:50 AM > To: [email protected] > Subject: Re: [IBM-MAIN] DEFINE CLUSTER MYSTERY > > David, > > I checked the SYS1.PARMLIB. In the example they are using (see below) 2048 > > DEFINE CLUSTER (NAME(?UID.MCDS) VOLUMES(?MCDSVOL) - > CYLINDERS(?CDSSIZE) FILE(HSMMCDS) - > STORCLAS(?SCCDSNM) - > MGMTCLAS(?MCDFHSM) - > RECORDSIZE(435 2040) FREESPACE(0 0) - > INDEXED KEYS(44 0) SHAREOPTIONS(3 3) - > SPEED BUFFERSPACE(530432) - > UNIQUE NOWRITECHECK) - > DATA(NAME(?UID.MCDS.DATA) - > CONTROLINTERVALSIZE(12288)) - > INDEX(NAME(?UID.MCDS.INDEX) - > CONTROLINTERVALSIZE(2048)) > > > --- On Wed, 5/6/09, O'Brien, David W. (NIH/CIT) [C] <[email protected]> > wrote: > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
