I have started leaning about the different stages of DS. I have few queries regarding hashed file stage.
1. What are the possible situations, where we can use hashed file stage?
2. What should be the input file type for a hashed file stage? (Whether xml? text?)
3. In what format will we be getting the output file?
4. Also, I have learnt that hashed file stage can be used as a lookup file. How?
5. Could anybody please explain the application of a hashed file with the help of a simple DS job example/demo?
I belive as a start you should read the DS pdf, which will answer all your querries!
Lavanya Srinivasan wrote:Dear Experts,
I have started leaning about the different stages of DS. I have few queries regarding hashed file stage.
1. What are the possible situations, where we can use hashed file stage?
2. What should be the input file type for a hashed file stage? (Whether xml? text?)
3. In what format will we be getting the output file?
4. Also, I have learnt that hashed file stage can be used as a lookup file. How?
5. Could anybody please explain the application of a hashed file with the help of a simple DS job example/demo?
DS Help Files , Search on this forum and plus there is a Article written by Ray on the newsletter of this forum which will help you understand the Hashed File better.
Do I recall that you don't actually have the DataStage software? That's going to make your quest a little... difficult.
Check the archives here for the Newsletters the site puts out periodically, one has an excellent overview of hashed files written by our fan favorite poster Ken Bland.
-craig
"You can never have too many knives" -- Logan Nine Fingers
Do I recall that you don't actually have the DataStage software? That's going to make your quest a little... difficult. Confused
Check the archives here for the Newsletters the site puts out periodically, one has an excellent overview of hashed files written by our fan favorite poster Ken Bland.
Yes you are right. I am the same person. Sure I will do that.
Hash Files can be used for various purposes. If you are beginer. one primary purpose of a hash file is to use it as a look up table. Consider the following scenario:
- You have to load data into a fact table with valid customers. All the valid customers are present in some table
So every time you do a load into the fact table you do a look up against the customer hash file(that can be loaded from a customer table).
By doing this you are ensuring that onlu valid customers are present in the fact
Server jobs (and therefore hashed files) are fully supported in version 8.0.
The principal difference for server job developers is that the repository is no longer stored in hashed files, but in a separate database, which is the unified repository for all IBM Information Server products. Metadata are moved to and from this repository by a metadata delivery service; however this is completely transparent to the DataStage developer. The design canvas and Director work almost exactly as before (the differences are the added new stuff, and a new appearance - especially at the top of the screen).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.