DSXchange

Here are three possibilities:
1. Use a Build stage (BuildOp).
2. Create a parallel routine (in which there can be a loop) and invoke that from Transformer.
3. Use a BASIC Transformer stage and Fmt() and Field() functions.

Are there any warnings in the log, particularly about changes to structure of Data Set, or "node not found", either if which might indicate use of an incompatible configuration file than that used when the Data Set was created.

Have you tried the "Microsoft solution" (re-booting your client)?

Projected population of India in 2012 ?

Search the forum, on-line help or the manuals for APT_STRING_PADCHAR environment variable.

Only the Sort Merge collector makes this assumption. If it's not true it doesn't really matter, but warnings about rows out of order may be generated.

Either you don't have permission to SDKSequences or someone has deleted one or both of SDKSequences and D_SDKSequences using operating system commands. The key management routine, because it can't open SDKSequences hashed file, attempts to create it. It is up to you to determine which of the above s...

I don't have a problem with sequencers - you can use them legally (in job sequences) anywhere.

You also need an entry in the uvodbc.config file for your DSN.

A Sort Merge collector is preferable to (Auto) collector followed by a Sort stage operating in sequential mode. Don't re-sort unnecessarily.

There's no difference in how you do it. There's a significant difference in how it happens. In an SMP ("share everything") environment the repartitioning can take place through shared memory. In an MPP ("share nothing") environment the repartitioning occurs using TCP sockets (at network speeds rathe...

To clarify. There's no number in the exponent? Is this "incorrect value" only in View Data, or is it in the output file as well? If in View Data, did you make the column wider, in case part of the value was hidden by inadequate column width?

One BLOB column. One row.

In DataStage BASIC (which is used for before/after job subroutines in parallel jobs) you need the STATUS statement - not the Status() function.

No it isn't. It's saying that there are too many digits in the value.