Why dont we have look-up stage in Datastage Server jobs
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 20
- Joined: Sun Jan 28, 2007 10:06 pm
- Location: Gurgaon
Why dont we have look-up stage in Datastage Server jobs
Hello alll,
I have a basic question for which i could not find an answer.
Why in datastage we dont have Look=up stage ina server job ?
I tried to figuer out but could'nt find an answer to it .
Can someone throw some light on it ??
I have a basic question for which i could not find an answer.
Why in datastage we dont have Look=up stage ina server job ?
I tried to figuer out but could'nt find an answer to it .
Can someone throw some light on it ??
In DataStage server jobs, the lookup is done via a reference link in a transform stage.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Ultimately the answer is that the vendor elected to have server jobs perform lookups one way (Transformer stage) and to have parallel jobs do it a different way (Lookup stage). The parallel Transformer stage does not support reference inputs.
As to why, only the vendor could answer that definitively.
As to why, only the vendor could answer that definitively.
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: 20
- Joined: Sun Jan 28, 2007 10:06 pm
- Location: Gurgaon
yes I'm aware of the fact that lookup is done via a transformer stage .
Also to add to this we can always perform look up in a transformer using datasets too.
but My question is that why at all datastage makers decided to provide this functionality in a transformer stage and did not allow look up stage in a server job.
Is this got something to do with the performance of a server job.
Also to add to this we can always perform look up in a transformer using datasets too.
but My question is that why at all datastage makers decided to provide this functionality in a transformer stage and did not allow look up stage in a server job.
Is this got something to do with the performance of a server job.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Because they are different products and different paradigms. Ascential built the Server product from the ground up, and later acquired the PX technology and folded it into the product line.RohanSharma wrote:but My question is that why at all datastage makers decided to provide this functionality in a transformer stage and did not allow look up stage in a server job.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 20
- Joined: Sun Jan 28, 2007 10:06 pm
- Location: Gurgaon
ray.wurlod wrote:It is NOT possible to perform a lookup in a Transformer stage using Data Sets. The parallel Transformer stage does not support reference inputs. At all. ...
I know that I was not clear in stating my earlier comments,but i was referring to server jobs only .
I know that a transformer doesnot support referrence links in a parallel job .
But in a parallel stage we can perform a lookup using the look up stage and datasets always.
And thats how the px engine was designed to perform. Server jobs dont have lookup stage and datasets, period.RohanSharma wrote: But in a parallel stage we can perform a lookup using the look up stage and datasets always.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.