CI's per CA of Index component



Help for IBM's record-oriented filesystem VSAM, ESDS, KSDS, RRDS, LDS and Storage management Subsystems

CI's per CA of Index component

Postby rickatagf » Wed Feb 04, 2009 8:40 pm

Trying to understand why all the VSAM KSDS files at my installation have the number of CI's per CA on the Index component on track boundries. Is this something that is a VSAM limitation or is it something (site dependent) that's doing it to us? For example, one particular file has 8192 Data componet (and Ci/CA of 90), and 4096 Index component where the CI/CA is 12. Both Data and INdex IDCAMS allocations are in Cylinders and I'm confused why 'something' is preventing Cylinder boundries on CI's per CA for Index component.
rickatagf
 
Posts: 1
Joined: Wed Feb 04, 2009 8:23 pm
Has thanked: 0 time
Been thanked: 0 time

Re: CI's per CA of Index component

 

Re: CI's per CA of Index component

Postby expat » Tue Feb 17, 2009 5:29 pm

You say that the SPACE allocation for both is done with CYLINDERS.

What happens when you define a cluster using CYLINDERS in the CLUSTER section of the define. The Index gets allocated in tracks.

To force the INDEX portion to be allocated in CYLINDERS, you need to specify the space allocations in the component levels of the define cluster, not at the cluster level.
expat
 
Posts: 382
Joined: Sat Jun 09, 2007 3:21 pm
Has thanked: 0 time
Been thanked: 1 time

Re: CI's per CA of Index component

Postby ESHudders » Mon May 18, 2009 8:51 pm

The CI/CA value for the index is not important as it is for the data.
ESHudders
 
Posts: 1
Joined: Mon May 18, 2009 8:47 pm
Has thanked: 0 time
Been thanked: 0 time


Return to VSAM/SMS

 


  • Related topics
    Replies
    Views
    Last post