DSXchange

Doesn't have to come from a Transformer at all. You can select one row from any reliable source (for example the "VOC" entry from "VOC").

Have you tried Help > About in the QualityStage Designer?

If you don't know that, find someone who understands Windows security - you're likely to do damage with unknowing tampering.

Not if your data type is Decimal. DataStage shows leading and trailing zeroes to confirm that precision and scale have been handled correctly.

You can remove these by changing the data type to VarChar.

Summary of techniques follows. Obviously the actual queries on the source system tables will vary with database type. (1) For a given (job parameter) table name read all the column names (excluding synonyms) with corresponding data type, character max length, precision, scale and nullability and, if...

It's always "Year of the " : Oconv(@DATE, "DYA")

Char(25)

All of the Ctrl-letter characters map to their ordinal position in the English alphabet. So, for example, Crtl-L is Char(12), Ctrl-T is Char(20).

The best delimiter is any character that does not occur in the data. As noted, this might be a non-printing character, such as tab or Ctrl-Y.

IsValid() expects a string argument. What happens when the data are not a valid date format? The StringToDate() function fails, but what result obtains?

(1) Sort and partition data using Sort stage generating key change column then use stage variables to increment/reset counter depending on whether a change has occurred. (2) Fork join. Make a copy of your data (Copy stage) and run it through an Aggregator to count the rows for each group. Downstream...

We have no way to know. We assume, as Craig said, that MCM was switched to 8.1 when you did the uninstall.

Has the password expired for the wasadmin user?

Thanks for the ideas, and the brainwork behind them. The point of parameterized SQL is "one job to do any one column in any one table" executed many times to do all columns in all tables. For reconciliation the same query must be run against source and target tables, and the results compar...

Everything is a valid string. Why not specify "date" as the first argument of the IsValid() function, and set a default date format of "%mm/%dd/%yyyy" in the job properties just for this job?