Team,
we are using a SoundexName function in datastage 7.5 server on windows. for a given string it is generating a value.
what is the equivalent of the SoundexName in datastage parallel 8.7?
Tried with Soundex function which is giving a another value for the same string in 8.7 Parallel.
Please let me know the equivalent value for the function SoundexName in 8.7 parallel edition on linux.
Soundex function in 7.5 server vs 8.7 Parallel
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 47
- Joined: Tue Sep 13, 2005 4:28 am
Soundex function in 7.5 server vs 8.7 Parallel
Kiran Kumar
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
SoundexName is/was NOT a built-in function. In any version.
A number of sites created similar routines. For example, I once created a Soundex algorithm for Pacific Island names (in which the rules around vowel handling, leading "NG", etc., are different than in US English). I called this SoundexPI. I suspect something similar has happened in your SoundexName function - whose source code you should be able to examine.
The Soundex algorithm is documented in many places on the web.
If you're going to create your own function you may prefer something like NYSIIS algorithm, which is more accurate.
A number of sites created similar routines. For example, I once created a Soundex algorithm for Pacific Island names (in which the rules around vowel handling, leading "NG", etc., are different than in US English). I called this SoundexPI. I suspect something similar has happened in your SoundexName function - whose source code you should be able to examine.
The Soundex algorithm is documented in many places on the web.
If you're going to create your own function you may prefer something like NYSIIS algorithm, which is more accurate.
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.