DSXchange

You are getting the "correct" value as far as the computer is concerned. What you are seeing is an example of the condition called arithmetic overflow, where the unsigned number is large enough to turn on the most significant bit, causing the signed number to be represented as negative. A ...

I would expect a server job to behave this way. One exception is ODBC, where you have to specify this behaviour by specifying Date as the data element.

Please show us the syntax you used when calling PxEreplace() function.

What is your default date format for Teradata? (You may need to ask your DBA.)

Easily. There's no theoretical limit.

It might help us to help you better if you were to post the exact error message, rather than "an error like..." which is tainted with your own expectations and understanding.

Welcome aboard.

Think about what that means. You're getting into Cartesian product territory here. How long would all those passes take? I guess that's why they don't make multiple passes available for many-to-many.

Do you have SELECT privileges to the system tables in which the metadata are stored?

Try it. You will, of course, have to name the sal column, since you're operating on it.

No software in the world has no bugs (unless, perhaps, I author it ).

Did you notice that you're adding to an eight year old thread?

Connector is the future.

IBM will not be developing the others further (apart from bug fixes).

You stand corrected.

This error arises because Pravenai has not sourced the dsenv script.

Interesting that your link is from Lotus. You'd think that they'd make the same information available in other brands, like WebSphere and InfoSphere.

Apparently there is no UNIX newline characters in the first 100000 bytes (or 300000 bytes) of your file. It may, for example, be a fixed-width format file with no record delimiters at all. DataStage can handle that - but you have to set the Record Delimiter property to None.

Type 1 is a simple update. Maybe your expectations are wrong. The SCD stage does handle Type 1 correctly. How have you identified the BatchId column in the stage? That is, have you marked it to be updated in any particular way (other than as Type 1, obviously)?