DSXchange

I suspect that the W token will override the F tokens and cause NameType to be O. For example HENRY JONES INC.

The other possible part of the answer to your question is to observe that what you posted is pattern action language. There is a pattern preceding each COPY action, which specifies the condition under which each constant will be assigned to the variable. The =T= operator forces the comparison to be ...

Why do you believe you want to do this? Using overrides on an existing rule set might be an easier, and easier to mainain, approach.

The answer to your question is non-trivial, would take hours to prepare and even longer to absorb. So I'd like to avoid that, if possible.

Try using escaped single-quote characters.

Inner will be fine. There won't be duplicate values out of the aggregator (because this was the grouping column) but there will be duplicates in the stream data. That's OK, that's what a join does. As to your Filter question, that may cause an issue if you're doing an inner join - depends really on ...

Set up a stage variable to report whether you've already seen the opening PROD_CD tag - if you have, transfer the value to the second field; if you haven't, transfer the value to the first field.

User_option is being assigned by the COPY actions directly.

There is an interactive debugger for parallel jobs in the future, but it's not in the product right now. The closest you can get now is to compile in trace mode (which effectively puts a Peek stage onto every link, so you can inspect the Peek outputs to see what data are being processed). In trace m...

Unless you have a strategy that allows a dynamic ALTER TABLE ADD COLUMN you have no solution. You could, perhaps, pack all the remaining extra pieces into a deliberately oversized final column as a delimited string, or choose a "friendly" database such as UniVerse or UniData that allow the...

There is a converter. Someone will post the name of it. Or you can track it down on IBM web site (probably Fix Central).

You won't lose any data. Only pass the columns to be grouped or summed to the Aggregator stage - pass all the others along the other link to the Join stage. All will be well, and you should not need an outer join - after all, the grouping keys came from the same data source!

Describe your table. That is, what are its column names?

Metadata.

All sorts of metadata, produced and consumed by the various products in the IBM InfoSphere Information Suite.

Technically there is no metadata server *in* DataStage. DataStage is one of many products in the IBM InfoSphere Information Server suite. All of these products use a common metadata model, stored in a common metadata repository, and accessed through services such as the metadata delivery service and...

What is the correct forum in which to post this question?

Not the one you've chosen, which is for suggesting topics to go into the FAQ forum.