Determination if the Hash File Size has increased.
Moderators: chulett, rschirm, roy
Determination if the Hash File Size has increased.
Hi ,
Due to some obscure requirement we had to resize one of our hash file
1. Now how do i determine whether the hash file size has changed or it is able to accomodate data > 2 GB.
2. I tried using ANALYSE.FILE hashfilename.
But i got a error stating the 'VERB ANALYSE.FILE is not present in the VOC'
How do we add the entry or verb in VOC.
Thanks in advance,
Gokul
Due to some obscure requirement we had to resize one of our hash file
1. Now how do i determine whether the hash file size has changed or it is able to accomodate data > 2 GB.
2. I tried using ANALYSE.FILE hashfilename.
But i got a error stating the 'VERB ANALYSE.FILE is not present in the VOC'
How do we add the entry or verb in VOC.
Thanks in advance,
Gokul
Hi,
ANALYZE.FILE
IHTH,
ANALYZE.FILE
IHTH,
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Code: Select all
Hi,
ANALYZE.FILE
How do we add the Verb ANALYSE.FILE in VOC?
Thanks,
Gokul
ANALYZE.FILE is a standard verb in the VOC, if it is missing then you have removed this (and perhaps other) VOC entries - which might cause problems in DataStage; the VOCabulary file is the crucial file from which everything is ultimately done; you should be very wary of modifying this file.
If you do a "LIST VOC WITH @ID LIKE ...ZE..." do you get any result?
If you do a "LIST VOC WITH @ID LIKE ...ZE..." do you get any result?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Hi,
I'm guessing you didn't notice that the correct syntax is with a Z not an S and it is:
Regarding hash files that are not account files
you'll need to build an entry in the voc file (corrected syntax)
Then you can use the alias file name in your ANALYZE.FILE command.
Bare in mind you might want to remove this entry later
IMPORTANT NOTICE:
Messing around with your VOC file is dangerous and entirely at your own risk if you do not know what your doing !!!.
IHTH,
I'm guessing you didn't notice that the correct syntax is with a Z not an S and it is:
Code: Select all
ANALYZE.FILE <HashFile Name>
you'll need to build an entry in the voc file (corrected syntax)
Code: Select all
SETFILE HashFilePath HashFileName OVERWRITING
Bare in mind you might want to remove this entry later
Code: Select all
DELETE.FILE [DICT | DATA] [filename]
Messing around with your VOC file is dangerous and entirely at your own risk if you do not know what your doing !!!.
IHTH,
Last edited by roy on Thu Aug 04, 2005 5:53 am, edited 1 time in total.
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Thanks Arndw,
Since i was testing in a separate Project the modification of VOC did not matter much. I created a new Project and in that ANALYZE.FILE was working.
After using RESIZE Command to increase the size of hash file.
The Ouput of ANALYZE.FILE is given as follows
Comparing 2 o/ps only Load Factor seems to be different.
[/color]
Thanks,
Gokul
Since i was testing in a separate Project the modification of VOC did not matter much. I created a new Project and in that ANALYZE.FILE was working.
I had created a hash file whose statistics given by ANALYZE.FILENow my query is how we determine whether the RESIZE command actually changes the size of hash file
Code: Select all
File name ..................... D_DSTemp1
Pathname ...................... /home/w951hdx/temp/DStemp1
File type ..................... DYNAMIC
Hashing algorithm ............. GENERAL
No. of groups(modulus)......... 2 current (Minimum 1)
Large record size ............. 1628 bytes
Group size .................... 2048 byets
Load Factors .................. 80%(split),50%(merge) and 46%(Actual)
Total size .................... 8192 bytes
The Ouput of ANALYZE.FILE is given as follows
Code: Select all
File name ..................... D_DSTemp1
Pathname ...................... /home/w951hdx/temp/DStemp1
File type ..................... DYNAMIC
Hashing algorithm ............. GENERAL
No. of groups(modulus)......... 2 current (Minimum 1)
Large record size ............. 1628 bytes
Group size .................... 2048 byets
Load Factors .................. 80%(split),50%(merge) and 57%(Actual)
Total size .................... 8192 bytes
Code: Select all
Then How we determine whether the RESIZE has actually changed the size of hash file
Thanks,
Gokul
Doing a RESIZE on an empty file will not change the size (Hence the 8Kb in both cases). Put some data into the file and then do a before/after compare of the RESIZE results.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Do a "UVFIXFILE {yourfilename} " and it will tell you what you want to know.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The second parameter of RESIZE is interpreted as a MINIMUM.MODULUS setting; the third parametr is interpreted as GROUP.SIZE 2 only if the parameter value is 8.
RESIZE is primarily used by dynamic hashed files to reclaim free space within the file structure. As Arnd noted, there probably isn't any in an empty hashed file.
RESIZE is far more important in tuning static hashed files, where the three parameters are hashing algorithm (= file type), actual modulus and separation.
RESIZE is primarily used by dynamic hashed files to reclaim free space within the file structure. As Arnd noted, there probably isn't any in an empty hashed file.
RESIZE is far more important in tuning static hashed files, where the three parameters are hashing algorithm (= file type), actual modulus and separation.
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.