DSXchange

Error message handler applies only to parallel jobs and provides a mechanism for intercepting specified types of message and suppressing them from the log, demoting from warning to informational, or promoting from informational to warning. An error message handler can be attached to (and have scope ...

When you convert to Decimal specify as much scale as you need. But there is a limit to the accuracy to which floating point numbers can be stored.

If you used a link to the container in your job you should not need to do so. If you used a copy of the container in your job you will need to.

OK, an explicit configuration file will do it. Create a job that uses an External Source stage to execute hostname ; ulimit -a and capture all the lines of output into wherever makes sense. This operator should execute on each compute node.

When you create configuration files for grid execution you don't specify the exact nodes, only the number that you require (at two levels). The grid management software actually allocates machines to nodes. This is fully documented in the manuals.

No, because each segment file of a Data Set is a sequential file (same argument as before) and each parallel job has every segment file in the Data Set in use.

You can use looping in the Transformer.

Prefer Phil Hibbs' most recent version of pxEreplace() function. Or upgrade to version 9.1.2 and get an inbuilt Ereplace() function in the parallel Transformer.

It is a given that computers cannot accurately store floating point numbers above a certain size. The IEEE published standards that are used widely and which offer the best compromise.

If that is true with rowid round robin partitioning then you have duplicate rows in source.

Keep dfloat (Double) throughout.

Any time you try to shoehorn a dfloat into an sfloat you will get data loss.

Please note that "-123.67" contains seven characters.

VarChar(5) is not big enough. NOR is VarChar(6).

Are you trying to monitor multiple machines in the one console, and perhaps using conflicting settings?

Where is the specification of what has to be loaded into each target column from each source (the "source to target mapping" document)?

If there is no common column Join would appear to be out of the question unless some kind of common column can be generated.

If you want to do anything differently from the default, create triggers that will implement your logic to your needs. Use Sequencers within the sequence to combine triggers.

How much later is "later"? Might the passwords have expired?