DSXchange

Numeric data are actually stored in binary form, so that the visual representation of them is irrelevant.

DataStage uses non-significant leading and trailing zeroes to demonstrate that precision and scale are being correctly handled.

As I stated, the data type on the output side is insufficient in precision or scale.

ArndW wrote:There should also be a file at .../InformationServer/Version.xml

... if you are on version 8.x of DataStage.

Welcome aboard. Check out your search paths (for example PATH and LIB environment variables) to see whether they refer to the parent directory.

Theoretically the answer is yes, but it might depend on just how you are trying to invoke it. Can you please provide more detail?

The old ORABULK stage never gave you the option - it prepared the CTL and DAT files and that's all. You had to invoke sqlldr yourself.

"There aren't any best practices, only practical practices."
(Stewart Hanna, world-wide product head for QualityStage)

What's best for me might not be best for you.

"They" won't make a buck from it.

Most everything in parallel jobs has, in the past, been created as server routines - links to many of them exist here. Why would "they" bother?

There is no limit of which I am aware. Is the 98th column null?

Please Search the forum for how to deal with NLS_LANG which is actually nothing at all to do with DataStage; it is an environment variable used by Oracle. Nonetheless it has to be set (correctly) for DataStage to interact successfully with Oracle.

Decimal(25) is the same as Decimal(25,0). Therefore DataStage does not know what to do with the fractional part. You have to tell it explicitly.

All patches are obtained through your official support provider, who should also have on record which patches they have already supplied to you. In the DataStage engine directory you may find a file called patchlist that will report the patches that have been applied. (However this is not guaranteed...

System variable @DATE does not require conversion, as it is already in internal format. The same is true of the Date() function. Therefore you are looking for an expression something like

Since there is no exit from SQLConnect, it is this that is failing. You need to investigate further using the test utilities in branded_odbc, which are fully documented in the various README files there.

Welcome aboard.

You are using a version of DataStage that is not supported for compiling and running jobs on Windows.

There is only one version earlier than 8.0 that is supported on Windows, and that is 7.5x2. Note that 7.5x2 is NOT the same as 7.5.2.