I would check out the current DEF CL suggestions from IBM in SYS1.SAMPLIB (I think it is there). You should be able to see what they suggest for CI Size, and space.
Also, use the worksheet in the HSM manual to determine what would be a good size. The xCDS datasets grow based on functions. Just raising it 300 cylinders may or may not be sufficient. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Michael Bieganski > Sent: Wednesday, November 06, 2013 8:42 AM > To: [email protected] > Subject: Size limits on hsm cds files? > > Hi, > We have an hsm ocds cds file sized cyl(4000,0) > a bcds1 cds file sized cyl(4000,0) a bcds2 cds also sized cyl,(4000,0) > an mcds1 cds file sized cyl(4000,0) and an mcds2 file also sized > cyl(4000,0) > About every 3 months or so, 1 or more of these start creeping into the 90%+ full > range and we do a re-org. > (we cannot take advantage of the ca reclaim function unfortunately) > > These cds files have been size of CYL,(4000,0) for a couple years and I think > increasing their sizes one at a time,as particular reorgs come up to be performed > might help reduce the number of reorgs I have to do during the year. > > So, wouldn't CYL,(4300,0) be the largest absolute size I can go with the > BCDS2 (without doing anything like extended attribute etc)? > Is there any rule that requires the bcd2 be the exact same filesize as the bcds1? > Would there be any danger with say, backvol cds, by having the bcds1 4000 cyls > but have the bcds2 bigger at 4300? > I've also heard that HSM doesn't like coding secondaries when creating the cds > files.......true?? > > thanks ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
