DSXchange

I can think of 2 things:
a) filtering Director entries
b) Automatic purging - this will remove the instance name when the log is purged.

dspxlearn wrote:...

Code: Select all

Convert(lk_AccInfo.AI_HomePhone,'-','')

...

should read

Yes, the syntax is different; like the Server stage syntax. It is available in the PDFs or online help.

TRIM In.String '0' 'F' in a modify stage would do the trick

I explained in the original reply that because of proprietary sorting method you cannot guarantee identical output. So either specify all columns needed in your sort criteria or explicitly sort using CoSort in DataStage. Also, because of partitioning in DataStage you are going to get separate stream...

Either use CoSort in DataStage or ensure that there are no unsorted duplicate columns in both CoSort and DataStage. This is the only way you will get guaranteed identical behaviour.

DataStage. Particularly if you have a partitioned table.

Hello Joe, there are so many complex mathematical approaches that are data dependant that the output order of sorted records will always be undefined unless they are part of the sort criteria. Since the sort algorithms and methods in CoSort as well as DataStage are not published you can never guaran...

Could you cut-and-paste your concatenation derivation to this thread? Most likely that is not working as you expect. Also, what datatype and length have you declared your stage variables as?

Could you be more specific about what didn't work? RCP, when enabled, lets columns get propagated without having them explicitly declared in all stages.

The DataStage subroutine calls to get this information have not changed at Version 8 so you can continue to use DSGetJobInfo() and the other DSGet...() routines to retrieve this information.

It is a bug, since I'm fairly certain I didn't try to do anything illegal.

The instance name isn't too important, it just has to be a unique string. Where do you want to generate this? If from inside DataStage I'd use @DATE:@TIME, assuming you won't be starting several instances within the same second.

It seems to be the way that DataStage calls up the ksh at version 8. If, from my shell, I execute the following two commands I see that the second one doesn't work as expected. I have no idea why the two commands run differently. echo "\000" | tr '\000' '?' | wc ksh -c echo "\000"...

Actually, replacing your joins with sparse lookups would show memory usage a lot better if you could try that - with a sparse lookup the reference data is not loaded to memory at all.