DSXchange

Given what you're trying to do, you don't need to create a data dictionary. All of the repository tables have dictionaries, containing all the metadata that the vendor is prepared to reveal. What you are trying to do is to hack the Repository tables, which would involve creating additional column de...

For a few cents a day - all of which goes to paying for this site - you CAN read premium posts.

TJX Companies wrote:This kind of concatenation worked with numeric fields in another job.

Just noticed this in the original post. Which suggests to me that the other job was a server job.

You don't understand me. It affects the size of the column in the data file used by TPUMP, not the column size in Teradata.

You have not specified the logic. There appears to be no way to solve the problem as posed, as there is no relationship between the two tables. Even if I can select a row - or several rows - in the date range from table B, how does that tell me which row(s) to select from table A?

All design objects are stored in DS_JOBOBJECTS which is a table in the DataStage Repository. When the job is compiled, information about the runtime configuration is stored in the RT_CONFIGnnn table apposite to the job. UniVerse database is not involved at all. DataStage ceased to be a UniVerse appl...

UniVerse is not DataStage.

Do you have UniVerse?

This As to your original questions, what's wrong with sufficient Execute Command activities in the job sequence? The values can be passed to the shell scripts either as command line arguments (retrieved from $1, $2 and so on) or as environment variable values. is a solution. If you have chosen not t...

How are you asking for the length to be reported? Create more output columns - define their derivations to use the Len() function.

Is the output file fixed-width format? If so, the fields will always be padded to length.

It may do, because display width governs the width of the column when writing to a fixed-width format file (such as the data file for TPUMP).

1(b) - actually they could be DS provided, they just aren't. There is example code provided elsewhere in the product. The reason is that you have to create, compile and link the C++ routine externally to DataStage; what goes in the Repository is only a description of the routine, not the routine its...

If you MUST use DataStage, use a Funnel stage and a Sort stage.

Wrong! Substring and concatenate does not produce a date, it produces a string.

Stop thinking like a server job developer!

Perhaps a better caption would have been "do not skip this activity"

How is the subset obtained?