Not NUll Comparision
Moderators: chulett, rschirm, roy
Not NUll Comparision
I do have a look up in Job which has 5 keys. I need to compare 4 keys in hash file with that of 4 fields in source. The 5th field in hash file should be not be Null. How can I give Not Null in the derivation field for that 5th Filed inside Transformer. If we want to cpmpare it with Null , we can use @NULL. I need to make sure that the field in Hash file is not null.
Aim high
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
NONE of the key columns in a hashed file can be null.
If the reference key expression is null, the lookup is not attempted. You can prove this using the Debugger.
If the reference key expression is null, the lookup is not attempted. You can prove this using the Debugger.
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.
Ray,
My aim is actually not to make sure the 5th field is NOT NULL.My aim is to compare only 4 fields of Hash file with source. I dont want to compare 5th filed with source.Since 5th filed is also a key in hash file, it has to be compared with some value, but for my requiremnet I dont want.
Even I cannot create that hash file with only 4 keys, because that file is used by other jobs.
So, is there any solution to compare only 4 fields and making 5th field as dummy.
My aim is actually not to make sure the 5th field is NOT NULL.My aim is to compare only 4 fields of Hash file with source. I dont want to compare 5th filed with source.Since 5th filed is also a key in hash file, it has to be compared with some value, but for my requiremnet I dont want.
Even I cannot create that hash file with only 4 keys, because that file is used by other jobs.
So, is there any solution to compare only 4 fields and making 5th field as dummy.
Aim high
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Just for this job purpose, you can create another hashed file with 4 keys instead of modifying the original file, and the fith key from source can be checked for null value in the transformer.nkln@you wrote:Ray,
My aim is actually not to make sure the 5th field is NOT NULL.My aim is to compare only 4 fields of Hash file with source. I dont want to compare 5th filed with source.Since 5th filed is also a key in hash file, it has to be compared with some value, but for my requiremnet I dont want.
Even I cannot create that hash file with only 4 keys, because that file is used by other jobs.
So, is there any solution to compare only 4 fields and making 5th field as dummy.