DSXchange

I have seen something similar to this in the past, where DataStage (UniVerse) was running out of file units in the rotating file pool, and data destined for one file unit was misdirected to another. Were there very many files open at the time? Does the problem occur reliably? If not, is it only at b...

Probably, but nothing is guaranteed.

This might seem a bleedingly obvious question at this point, but why can't you use the Remove Duplicates stage?

None exists.

Welcome aboard. Unable to allocate... messages usually mean that some resource was not able to be obtained. In this case, for a handler pool, the resource is probably memory. Alternatively, there is a bug in the process for attaching your stage to a Connector - ask your support provider whether ther...

The only reason it could be taking the other field is because the developer told it to. Check the output column and/or stage variable derivations carefully.

With admittedly very standard jobs (only Investigate, Select, Standardize, one-file Match and Survive stages) the migration was transparent.

Your data are not partitioned on the join key. You must partition (using hash - or modulus for integer keys) so that the same value always appears in the same node.

Ask for proof. In the meantime, open the stage properties of any of your Transformer stages. If there are tabs there called Trigger and Build, these are for C++, not for DataStage BASIC, so you have a parallel Transformer stage. Another thing you might try is finding the BASIC Transformer stage in t...

Ask your UNIX administrator about partitions, particularly logical partitions (LPARs).

Parameter sets , however, are stored in the common repository of IBM Information Server. To achieve what you want the easiest thing to do is to set up the parameters in the parameter set as environment variables with default value $PROJDEF. That way, the running job will pick up the value from whate...

The Sort stage is very useful for preventing unnecessary sorting, using Sort Mode "Don't Sort (Previously Sorted)".

Julian is an abused term roughly meaning "counted from a particular day zero".

The Join stage uses hardly any memory at all. It takes in one row from its left input, and only those rows from the right input for which the join keys match. Your error actually came from an (inserted?) tsort operator that precedes the join operator. Dump the score to see how this is connected. So ...

It is not possible by any means. A Lookup File Set is architected purely to answer "Get By Key" functionality - that is, to feed a reference link to a Lookup stage. It does not support a "Get Next Row" function, and therefore can not deliver a row count. You have to rely on the row count when popula...