DSXchange

There are two solutions already in this thread.

It's new in 8.1, it's improved in the next version (currently in beta). It's used in DataStage Designer, to suggest opportunities for shifting some of the processing into the database, depending on a cost-based optimizing algorithm. It can then re-design the job to take account of the processing shi...

You need to configure .odbc.ini in the engine directory.

You also need to configure the DSNs correctly.

Any hash or checksum algorithm will have its limitations. For example CRC32 is necessarily limited by its 32-bit result to be accurate only to about one in four million. The greater the number of potentially unique values, the "bigger" the algorithm you need. There are variations on MD5 - ...

laknar wrote:is there any possibility using Modify stage.

No.

You still need to report what's different (about the system, databases, DataStage, ... anything) between when the job runs fast and when the job runs slowly.

Dump the data into a text file and inspect that text file with a hex editor (such as od -cx command) to determine exactly what these characters are. This will assist in diagnosing where they are coming from.

I like Arnd's answer. If you have a third party sort utility, such as CoSort or SyncSort, then there's also scope for invoking that. If you have a UNIX emulator, such as MKS Toolkit, you could use a UNIX sort command as a filter command in the Sequential File stage itself. You could stick the data i...

You could do worse than understanding what it is that needs to be done, in this case a "vertical pivot". Were you to Search DSXchange for that term, you might even get answers!

Let's begin with "what's 'special' about them?"

Most operating systems impose a smaller limit than the theoretical limit, typically 1TB or 9TB.

DataStage 8.1 on AIX 6.1 is a 64-bit application. The issue here seems to be that DataStage is destroying the PATH environment variable, and with it reference to all the DB2 executables.

Shades of Mythbusters: "I reject your PATH and substitute my own."

There's no problem.

Windows operating system does not support the system calls that the parallel engine makes to determine virtual memory. So you get a warning that it is safe to ignore. Since this is the only warning, your configuration file is good on that server.

Not a question at all.

There is no RunJob command.

You're probably intending to use a DSRunJob() function.