Hi All,
We have just had a customer hit a 2GB limit on a sort file. We have multi-segmenting enabled and it works for VLR files but i'm guessing not for sort files?
Problem is, if we convert this file to a VLR or EFF, even with a RSZ of 1, the file grows from 2GB to 3.5GB which seems excessive.
Does anyone have any other method to get around this, or am I stuck with just changing the file to VLR across all our systems?
Thanks,
Chris
What is the key and block size for the sort file?
By default there is a 255 key per block limit which often leads to wasted space if the blocks are large and keys small.
While originally designed for VLR files setting XK parameter or using a smaller block side for the file may allow more keys to be stored in less space.
Hi Mike,
Sorry for the slow response. This was my first forum post since you guys have done away with the mailing list and even though i thought i had set up email notifications I didn't seem to receive on. I'll go play with the settings again.
Here is the *UFI for the original sort file which is almost at its limit.
-------
Keyed file: U:\DATA\DATA.TO\INFSILSTO
Maximum Record size ..........: 0 (Sort file)
Maximum # records ............: (No limit)
Current # records ............: 20852709
Size of key block ............: 4096 bytes
External key size ............: 50
-------
When i convert the file to a VLR using the data dictionary with only the 50b external element.
-----
Keyed file: V:\TEST\DATA\DATA.TO\infsilsto
Maximum Record size ..........: 256 (Variable)
Maximum # records ............: (No limit)
Current # records ............: 20852709
Size of key block ............: 4096 bytes
Record Expansion factor ......: 10%
Total # of Keyed File Segments: 2
External key size ............: 50
----
I'm happy to tweak the settings as you suggest.
Hi Mike,
Any guidance to the best way to recreate this file to avoid the 2GB limit?