eliminate certain records
Moderators: chulett, rschirm, roy
eliminate certain records
Hi all,
I have a data set file which has few key column records only. Now my requirement is process only those records from input in hich key is not matching to the key column in dataset. Lookup can't help. any other idea on how to accomplish it in job design? Input is Oracle table and records ot be rejected are in dataset.
I have a data set file which has few key column records only. Now my requirement is process only those records from input in hich key is not matching to the key column in dataset. Lookup can't help. any other idea on how to accomplish it in job design? Input is Oracle table and records ot be rejected are in dataset.
Re: eliminate certain records
Why is that?BSG1 wrote:Lookup can't help.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Re: eliminate certain records
Not able to fins how lookup would help. Dataset file has key1 which are to be rejected. source has all the key1 columns. Now if I use lookup with lookup from dataset file, what properties and condition to use to get unmatched records get to output?
Re: eliminate certain records
I think it can work. I should capture all unmatched record to reject link and use that reject link for further processing.
Re: eliminate certain records
Yes you got it! It will work.
Consider the volume of the data. If it is huge, you can try some other stage.
Consider the volume of the data. If it is huge, you can try some other stage.
Thanks
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
Re: eliminate certain records
data at reference link is very less like few hundreds so everything is going to go to reject only. What other options i have?
Looks like a job for negative logic, something I try to avoid if at all possible.
A constraint is "open" where lookup key matching is not. I've seen reject links used for scenarios like yours, but a "negative" constraint using not-equal (<>) is more direct, and also let's you use more than one constraint if your data is more complex than just the one key.
A constraint is "open" where lookup key matching is not. I've seen reject links used for scenarios like yours, but a "negative" constraint using not-equal (<>) is more direct, and also let's you use more than one constraint if your data is more complex than just the one key.
Franklin Evans
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
Sorry, I meant my suggestion to be for a stage other than Lookup. Try a transformer.
Franklin Evans
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872