DSXchange

They are fairly frequent requirements. However, Convert() would not be the correct function to use, as it effects character-by-character replacement. The actual solution will depend on the data type of the input column and the output column, but will involve some combination of DateToString() and St...

Because the Data Set is stored on four nodes it can only be read from those four nodes, typically with the same configuration file as the one with which the data were written. You can bring the data together by forcing your Oracle Enterprise stage to execute in sequential mode, and using Sort/Merge ...

Because the location of dsenv is recorded in $DSHOME and/or /.dshome.
The location does not matter; being able to find it does matter.

It's just a file. Provided it is readable by all, its location should not present an issue.

My guess is that the computed fields of an Aggregator stage are always nullable despite what the metadata prescribe, and that this is the source of the alert message.

Your string pad character is set to 0x00 (its default value) but your DB2 is objecting to a fixed-length string (that is, a Char data type) being padded with this character. Explicitly pad the string with space or some other valid character, or change APT_STRING_PADCHAR.

My thought was the CurrentTimestamp() loading into a Date field will effect an implicit conversion.

Download ETLstats from Kim Duke's web site. All that you request is already in that suite.

There is a chapter on each of these stage types in the Parallel Job Developer's Guide that includes explanations and examples. Please read those then post any specific questions here. DSXchange does not purport to replace either manuals or education.

Vertical pivoting (rows to columns) can be performed in DataStage using a number of techniques. Search DSXchange for "vertical pivot".

This looks like an ideal task for an Aggregator stage. You could also do it in SQL using MAX and COUNT set functions.

Difficult if you're using a Data Set to store the intermediate result; you'd have to use an orchadmin command via an Execute Command activity to retrieve the result. Since it's only a single row, I'd advocate using a server job and posting the count into that job's user status area, whence it can be...

Use different jobs.

Difficult if you're using a Data Set to store the intermediate result; you'd have to use an orchadmin command via an Execute Command activity to retrieve the result. Since it's only a single row, I'd advocate using a server job and posting the count into that job's user status area, whence it can be...

Can you please post the exact and entire error message? In particular I am interested in knowing which operator generated it. Can you also advise the setting of the "allow nulls" option in the Aggregator stage? My guess is that the computed fields of an Aggregator stage are always nullable despite w...