One way it's possible is to use a storage class with the Guaruntee'd Space
attribute and specify different volumes for the Data Index. Of course,
you have to understand what storage group SMS is going to assign the
dataset to and chose volumes within that storage group. I ran a test here
There used to be a legitimate performance reason for doing this 20 years
ago when accesses to the index alone on a hot VSAM file could saturate a
single real 3380/3390 drive. With today's emulated DASD, DASD Subsystem
cache several orders of magnitude larger, multiple PAV accesses to a
Please! I appreciate everyone's input on this problem...
To answer why... This is a very high I/O file with delays. Mainline, the
company assisting with the performance study, suggested splitting the DATA
and INDEX component.
Thanks for all the replies...
*
*
*George Rodriguez*
*Specialist II -
