There are two references to a hashed file like - D_HashedFileXXX and HashedFileXXX.
Inside HashedFileXXX directory you have two files - DATA.30 and OVER.30.
Check the size of these too.
How to calculate the size of the text file
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Just for interest, do the calculations like I did earlier. Keep one byte per delimiter and use 14 bytes/record as the storage overhead. Post your calculations, so I can be certain you understand.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Ray-"Just for interest, do the calculations like I did earlier. Keep one byte per delimiter and use 14 bytes/record as the storage overhead. Post your calculations, so I can be certain you understand. "
I did not follow you Ray exactly . Why we need delimiter while calculating for Hashed files?
We downloaded Datastage client from the IBM site so Unsupported utilities was not provided to us.
I am not sure how to calculate for Hashed files.
I did something like this
10+3+8+14=35 bytes per line For 15446662 records equates to 540633170 bytes
May be i need to know more about Hashed files
Thanks
paddu
I did not follow you Ray exactly . Why we need delimiter while calculating for Hashed files?
We downloaded Datastage client from the IBM site so Unsupported utilities was not provided to us.
I am not sure how to calculate for Hashed files.
I did something like this
10+3+8+14=35 bytes per line For 15446662 records equates to 540633170 bytes
May be i need to know more about Hashed files
Thanks
paddu
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You need the delimiter because it's in there (though it's a "field mark" in hashed files).paddu wrote:Why we need delimiter while calculating for Hashed files?
10+3+8+14=35 bytes per line \
For 15446662 records equates to 540633170 bytes
By default hashed files are only filled to 80% of capacity, so your calculation is in the ballpark. ALlowing for the 80% (the "split load" tuneable parameter), your calculation would yield 675,791,463 bytes, whereas you observed slightly more than this.
There are other complexities relating to headers, free space, overflowed groups and oversized records, that I deliberately avoided. Your calculation, as I noted, is in the ballpark.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.