HI All
I have a job which hangs when using Hash file as a lookup.
My job design is like this
!-------------HASHFILE1
! !
! !
! !
! !
! !
DRS-----------TRANS1------------TRNAS2-----------SEQFILE
! !
! !
! !
! !
AGG------------HASHFILE2
The First HASHFILE1 is looked up with TRANS! and Second HASHFILE2 is looked up with HASHFILE2.The job is working fine as long as i dont use HASHFILE2 as lookup,there is no error message thrown ,upon running the job turns in waiting state. i.e hangs
Please advice
Job Hangs when using hash file as a Lookup
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 14
- Joined: Tue Dec 20, 2005 2:29 am
-
- Participant
- Posts: 14
- Joined: Tue Dec 20, 2005 2:29 am
-
- Participant
- Posts: 14
- Joined: Tue Dec 20, 2005 2:29 am
![Idea :idea:](./images/smilies/icon_idea.gif)
That being said, I have no idea what you mean by this:
The First HASHFILE1 is looked up with TRANS! and Second HASHFILE2 is looked up with HASHFILE2.The job is working fine as long as i dont use HASHFILE2 as lookup,there is no error message thrown ,upon running the job turns in waiting state. i.e hangs
So, HASHFILE2 is 'looked up' by TRANS2 I assume. And I don't think that's a valid job design and somewhat surprised it will actually compile. HASH2 has to be completely populated before it can be used as a lookup by TRANS2 and the job isn't just going to stop there and wait for the Aggregator to do its work.
Build HASH2 from a separate source.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers