DSXchange

You will need to put the Teradata-related environment variables into dsenv but probably don't need to re-start DataStage services.

There shouldn't be, though you might get newer ODBC drivers and therefore need to re-define the DSNs.

I think it's to do with the physical construction of the key (@ID), which in your "two key" example would be Char(128):Char(252):Char(128). The separator character, by default, is a "text mark", which can be represented by @TM or Char(252). Because at least one of these is not @N...

The main error is that DataStage was unable to connect. Is db2inst3 your default database connection? (What values do DB2INSTANCE, APT_DBNAME and APT_DB2INSTANCE_HOME environment variables have?) The error message suggests that the Columns tab contains column names other than those in the STAGING.PR...

Stage variables are exactly what they sound like - variables whose scope is limited to the stage. They can (should) be initialized and may be re-calculated for each row processed. Constraints are "gates" - expressions that determine whether or not the current row is eligible to be passed t...

It is not possible.

Why do you want to?

If you can make a business case (or even if you can't) you're able to submit a product enhancement request to IBM either through your official support provider or through DSXchange's enhancement requests forum.

When a VarChar is stored, it is prefixed with a length. You can see this most easily by displaying the table definition as COBOL. The Prefix designator in a record schema indicates the size in bytes of this number. That information, in turn, is available to any import operator that needs to handle V...

Do you have sufficient permission to the DSParams file in the project?

Using Web Console for Information Server you have to map the Active Directory users to UNIX user IDs in the Domain Management menu, DataStage Credentials area. This automatically assigns Suite User role. Then you have to assign the DataStage User role to the user, still within Web Console for Inform...

This is also available in the BASIC Transformer stage.

First convert to ASCII (using Ascii() function) then use Oconv() which expects ASCII data.

0x00 is not @NULL. It is the ASCII NUL byte and can be represented using the function Char(0).

0x80 is @NULL (unless changed, on Windows platforms, because Microsoft uses 0x80 for the Euro symbol). The change is effected in uvconfig.

While it's not possible through a specific command line interface, it is possible to compile on the server (or "engine tier") using the same mechanism that DataStage itself uses. I don't have the details available right now, but you need to invoke dssh in the project and execute (from memo...

That, of course, is an entirely different message, indicating that the original problem has been solved.

To make life easier for future searchers, please start a new thread for the new problem.

dati.hari wrote:How to Handle Exception in DS with out using Job Sequencer

However you like, if you create the routine that controls it all.

I don't see a vector defined in your osh - just a Char(40). Your metadata needs to specify the size of the vector (which will cause a vector to be defined). Do this on the extended properties of the column - right click on the column definition and choose Edit Row from the menu.