Reading through the posts and trying to create indexes on a sample hash file.
1. when i set try to enter a VOC entry it gives me a warning. that the 'DICT file path ' physical path name' does not exist, though it does create a link after it
2. when i try to create index on a hash file by CREATE.INDEX HASH_FILE_DEMO COL A , it says unable to open hash file or not a valid hash file.
any tips ... cause i have tried everythin which is already been said in the previous posts pertaining to this.
thanks
Problem creating indexes!
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Any reason not to post a question that is obviously about a server job in the forum for server jobs?
There's no such thing as a hash file (other than a tool for shaping a block of hash). How did you attempt to create one?
Assuming the thing that you attempted to create was a hashed file, how did you create that? The answer to that question will affect the proper answer to the questions you posted in this thread.
There's no such thing as a hash file (other than a tool for shaping a block of hash). How did you attempt to create one?
Assuming the thing that you attempted to create was a hashed file, how did you create that? The answer to that question will affect the proper answer to the questions you posted in this thread.
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.
If you edit your VOC entry for this hashed file then there should 3 lines.
ED VOC DS_AUDIT
3 lines long.
----: P
0001: F Ardent DataStage Repository file
0002: DS_AUDIT
0003: D_DS_AUDIT
Bottom at line 3.
----: EX
Line 1 says it is a F-pointer or file pointer.
Line 2 is the DATA side of this hashed file.
Line 3 is the DICT side of this hashed file. DICT is the dictionary or the column for this hased file or if you will this table.
The DATA side and the DICT side need to exist at the OS level.
ED VOC DS_AUDIT
3 lines long.
----: P
0001: F Ardent DataStage Repository file
0002: DS_AUDIT
0003: D_DS_AUDIT
Bottom at line 3.
----: EX
Line 1 says it is a F-pointer or file pointer.
Line 2 is the DATA side of this hashed file.
Line 3 is the DICT side of this hashed file. DICT is the dictionary or the column for this hased file or if you will this table.
The DATA side and the DICT side need to exist at the OS level.
Mamu Kim