I have a job that works correctly with a hash file. When I view data in the input tab... all data seems ok... all data seems ok in the output tab too.
I have another job that's not working with a hash file. All data seems ok in the input tab... but when I look into the output tab... column definitions are ok but I have garbage data... ie @KEY @ID @
Any suggestions?
Thanks
Hash File Seems Corrupted
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
@KEY, @ID and @ are entries from the file dictionary, they ought not to appear in the data portion of the hashed file. My guess is that someone has somehow copied the dictionary entries into the data part. These will have "D", "I", "PH" or "X" in field #1, so should be easily detected.
To see themTo delete them, use the same FROM and WHERE clauses in a DELETE statement.
To see them
Code: Select all
SELECT F0, F1 FROM hashedfilename USING DICT VOC WHERE F1 IN ('D', 'I', 'PH', 'X');
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.
-
- Premium Member
- Posts: 892
- Joined: Thu Oct 16, 2003 5:18 am