DSXchange

Can anyone decipher this message, generated by a Lookup stage BlackBox.CS101_LookupCId: When checking operator: The view adapter has a binding for the non-existent destination field "SOURCE_CRNC_CODE". I am getting a currency code from a reference table by a lookup keyed on a Currency Id. ...

Cunning.

Mind you if everyone were to sue IBM for all the errors and omissions in Datatage documentation, the would probably be on course for the biggest corporate loss in US History.

Again.

If you do include a WHERE clause you effectively overwrite whatever the sparse join was going to generate That's basically the conclusion I have come to, further proof that whoever designed datastage does not inhabit the same planet as the rest of us. Seems that if you want to constrain a sparse db...

Make sure Customer Id is named identically in both the input and reference links and is set to be the only key field in both and your lookup should work. I can confirm that all columns are named consistently and the lookup 'works', in fact it works too well, returning more rows than we want. (How d...

What did you put in your WHERE clause ... do you include the WHERE statement or just the condition itself

eg do you enter "WHERE HIST_DT > '2005-01-01'"

or just "HIST_DT > '2005-01-01'"

I am using a Sparse lookup to return some values from a Customer History table in DB2. The key is a Customer Id, and there is one row on the table per Customer Id, per month. I use Customer Id as my lookup key, set read type to TABLE and constrain the month using a WHERE clause .... Instead of retur...

Emabarrassingly swift reply.

Note to self RTFM before posting

Thanks,

So I've been developing in PX for 8 weeks or so now so still a bit of a novice, and having got the application working I am now looking at optimising its performance. One situation that crops up repeatedly is where I want to send rows that meet conditions A or B down one stream and all other rows do...

Nothing like writing a problem down for enabling you to see the bleedin' obvious solution staring you in the face. The answer is indeed to use Runtime Column Propagation, and I will write up the steps I went through to get it working when the time pressure eases off again. Thanks, DSXchange - someti...

I am trying to write a simple buildop and find myself disappearing in ever decreasing circles ... Basically I have to apply some business rules to an input row to determine its Classification and write this value to a CLAS column. Every other column should be propagated straight through untransforme...

Thanks for the fast response: OK I substituted @IM and the warnings went away. However only the first element of the array - before the first @IM - was returned I ideally want to return an array that I can then reference using the <> notation eg result1 = dynarray<1> result2 = dynarray<2> etc ... I ...

I want to pass a small series of values from one job to the next and I thought that a solution would be to build a dynamic array by concatenating the values delimited by @FM, and pass it to DSSETJOBSTATUS to be picked up and passed to the next job. This works well except for one thing, the Director ...