I have a VSAM file which is an input to a pgm.
I'm reading it in I-O mode, so that i can update it through the pgm.
The VSAM will be having a huge amount of data, and it may exceed to the maximum limit.
I wanted to define the VSAM in such a way that it can accomodate the maximum amount of data.
Could any one share the attributes for such a KSDS.
Joined: 23 Nov 2006 Posts: 8729 Location: 221 B Baker St
Hello,
I believe you have this part of the analysis somewhat turned around.
The proper way to estimate is to determine how much data & index & + is needed to accomodate the data requirement. Then calculation can begin on how that translates to physical space.
Knowing the biggest possible vsam file in all of mainframe land should not enter into considertation.
Joined: 06 Jun 2008 Posts: 941 Location: Atlanta, GA
Quote:
I wanted to define the VSAM in such a way that it can accomodate the maximum amount of data.
Could any one share the attributes for such a KSDS.
Not without a LOT more information. There's many variables involved in VSAM file allocations and you really need to provide concrete data rather than just trying for the maximum and going backwards. Besides, the space management people at your site might not be happy if you try to allocate such a huge VSAM file without discussing it with them beforehand.
