VSAM CI SIZE



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

VSAM CI SIZE

Postby ewansyo » Thu Mar 14, 2013 8:41 pm

How does the CI SIZE affect the ESDS VSAM file in terms of processing speed? Does larger CI SIZE much faster?
ewansyo
 
Posts: 2
Joined: Thu Mar 14, 2013 8:14 pm
Has thanked: 0 time
Been thanked: 0 time

Re: VSAM CI SIZE

 

Re: VSAM CI SIZE

Postby c62ap90 » Fri Mar 15, 2013 12:33 am

I always start define as CISZ (4096) and then depending on, for example, Splits - I contact our Systems Programmer for VSAM file tuning.

Some more info...
http://pic.dhe.ibm.com/infocenter/pdthe ... pvsm51.htm
An average CISZ of 4K is suitable for most applications. A smaller CISZ means faster retrieval for random processing at the expense of inserts (that is, more CISZ splits and therefore more space in the data set). A larger CISZ results in the transfer of more data across the channel for each READ. This is more efficient for sequential processing, similar to a large OS BLKSIZE.
c62ap90
 
Posts: 125
Joined: Thu Oct 11, 2012 10:24 pm
Has thanked: 1 time
Been thanked: 6 times

Re: VSAM CI SIZE

Postby Robert Sample » Fri Mar 15, 2013 1:15 am

For an ESDS, I'd probably go with 18432 which is most space-efficient. However, if the application is running under CICS 4096 might work better as there is less data written at a time. If the application is running only batch ESDS with no alternate indexes, then 32768 might be your best CI SIZE. There is no one "true" answer to a question like yours -- it depends upon the site, whether the ESDS file has alternate indexes, whether the ESDS file is used online only or batch only or both, and other factors.
Robert Sample
Global moderator
 
Posts: 3367
Joined: Sat Dec 19, 2009 8:32 pm
Location: East Dubuque, Illinois
Has thanked: 1 time
Been thanked: 222 times

Re: VSAM CI SIZE

Postby ewansyo » Fri Mar 15, 2013 9:45 am

Hi,

Thank you both for the helpful responses. :)

The ESDS file has no alternate index and will be used only as an online log, we would only do write to this file. So does it mean that 32768 might be good for this type of file?
ewansyo
 
Posts: 2
Joined: Thu Mar 14, 2013 8:14 pm
Has thanked: 0 time
Been thanked: 0 time

Re: VSAM CI SIZE

Postby NicC » Fri Mar 15, 2013 1:06 pm

If the application is running only batch ESDS with no alternate indexes, then 32768 might be your best CI SIZE.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Re: VSAM CI SIZE

Postby Robert Sample » Fri Mar 15, 2013 4:58 pm

For an online log, 4096 is probably your best choice. You want logs to be written fairly quickly, and hence a smaller CI SIZE makes sense.
Robert Sample
Global moderator
 
Posts: 3367
Joined: Sat Dec 19, 2009 8:32 pm
Location: East Dubuque, Illinois
Has thanked: 1 time
Been thanked: 222 times


Return to VSAM/SMS

 


  • Related topics
    Replies
    Views
    Last post