Lookup Filesets
Im trying to use Lookupfile sets with a Lookup Stage. There seems to be a problem somewhere that I can't understand.
Lets assume we have a table - EMP with the fields :
EMPNO
DEPTNO
ENAME
SAL
MGR
We have a Lookupfileset DEPT with the fields :
DEPTNO
DEPT
Say, the Lookupfile Set was created with the Lookup key = DEPTNO.
We have a target sequential file Employee_details.DAT with all the
fields :
EMPNO
DEPTNO
ENAME
SAL
MGR
DEPTNO
DEPT
In the Lookup Stage. Do we have to map anything for the above scenario?
In the Input fields and Output fields? If we do, mapping between the input sources the lookupfileset(DEPT) and the Table (EMP) cannot be done. So how do we pass the data to the Output file? May be Im not understanding the Lookupfileset properly.
Thanks,
MH
Lookup file sets
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard! :D
Refer to Chapter 20 of the Parallel Job Developer's Guide for full information on using the Lookup stage.
You're on the right track, you identify the lookup keys (and whether case sensitivity is required and whether you want to allow multiple return rows) in the Input link properties page.
Leave the partitioning to its default value unless you have some strong reason for changing it.
It helps if the lookup file set is sorted, but this is not essential.
Refer to Chapter 20 of the Parallel Job Developer's Guide for full information on using the Lookup stage.
You're on the right track, you identify the lookup keys (and whether case sensitivity is required and whether you want to allow multiple return rows) in the Input link properties page.
Leave the partitioning to its default value unless you have some strong reason for changing it.
It helps if the lookup file set is sorted, but this is not essential.
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.