Hi All,
I have a problem with the below constraint in one of my jobs
IsNULL(Lkp.Column1) AND IsNULL(Lkp.Column2)
both Column1 and Column2 in the hashed file are key fields.How to validate the above constraint. I have checked my hashed file,none of the columns are null.Please let me know your thoughts on this issue.
Thanks,
Satheesh
IsNULL function in Lookup Columns
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 182
- Joined: Thu Jun 16, 2005 2:05 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
What is the problem that you are having?
The expression is syntactically correct. The key columns will not be null unless the lookup fails (a lookup is functionally a left outer join).
The expression is syntactically correct. The key columns will not be null unless the lookup fails (a lookup is functionally a left outer join).
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.
-
- Participant
- Posts: 182
- Joined: Thu Jun 16, 2005 2:05 am
So we're not resolved? You are correct that you populate the key columns with non-null data from the input stream so they "should not be null". However, when the lookup fails all columns return null (including the keys) so they can be checked for null post-lookup to determine failure.
The NOTFOUND Link Variable replaces that technique with a status you can check directly.
The NOTFOUND Link Variable replaces that technique with a status you can check directly.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers