DSXchange

If you publish the data rules you can either open in Information Analyzer or create a report of the rules, and copy from there to paste into DataStage.

The problem is whoever created data in this format.

The first argument does NOT include the sign. The definition ("digits") is correct.

"It" is converting nothing. It is finding these {c2 ac} sequences in the data.

Maybe, since you are on Windows, the record_delimiter_string property value should be '\r\n' (DOS style).

For example, these two would match using Reverse Soundex, even without any other standardisation.

Confuted indeed.

Parallel jobs use the transform operator - the parallel Transformer stage is merely a convenient (= GUI) way of setting it up.

The server Oconv() function with "MD"-style conversion can also specify the number of decimal places. In your example.

Also define "last 5". Do you mean "last 5 for this particular job", "last 5 runs in this particular project" or even "last 5 jobs run on this server"?

Microsoft does not believe that any other dates than those mentioned in the referenced article exist!

Glad we could help.

You're in France, using a French locale, which specifies space as the thousands delimiter and comma as the decimal placeholder (which is correct for France). You can change this easily by changing the NLS locale used by that job.

The job will automatically split the data over the four nodes for processing. If you use Round Robin partitioning, which is the default in most cases, then they will be distributed evenly. Whether or not your scratch space is consumed depends on whether your job performs operations that require scra...

Or is it that you wish to match against the final digit of the first ID?
Your requirement is not clearly stated.

I'd be using a Standardize stage (QualityStage component) with an appropriate address rule set (e.g. USADDR).