DSXchange

It would be more efficient not to try to undo the join, but to select the original tables from the original tables. -----> Transformer -----> ODBC2 (original table A) ODBC1 -----> Transformer -----> ODBC3 (original table B) -----> Transformer -----> ODBC4 (join of tables A and B&...

Go to the job properties window of your job sequence. On the General tab there are four check boxes. One of these is to log an event (in the job log of the job sequence) whenever a job is executed. Check that box and recompile the job sequence.

Make use of the fact that the exit status of grep is 0 if the string is found and non-zero (typically 1) otherwise.

Search would have answered that question. In short, the status that Director reports is from the RT_STATUSnnn table associated with the job. If there is a network problem or the job has aborted, the job may not get the chance to update its status table. That's the main reason the "Clear status file...

That's because the DB2 stage (idiosyncratically) wants an internal format date. You achieve this with an Iconv() function.

In your MATCH job, did you specify a different output file name? Did you request that the report be generated (this is a check box, from memory)?

The message says not to use the setOutputFieldAsString() function unless the target data type is string (that is, Char or VarChar).

NLS means National Language Support; it must be selected when DataStage server (engine) is installed. It gives you the ability to map from and to different character sets using a "character map" (or "code page"), and to represent dates/times, currency, numeric data, etc., according to local conventi...

Within the Lookup stage, what is the data type of COLUMN_NM_1 on each link on which it appears? The message suggests that it is Char(2) somewhere.

How closely have you verified that "the only thing changed is the hardware"? Please monitor both systems, running the same jobs, to determine what DataStage processes are running and what resources these are consuming. Also report all other processes, particularly any associated with database server...

1. Request additional file systems (NOT additional directories in the same file system) from your "higher authorities". Ideally, use a separate file system for each processing node, to maximize I/O throughput. Then, on an SMP environment, institute a configuration that "gives all nodes all the disk"...

Post the full error message. This is not the kind of message I would expect to see from a Sort stage. Examine the error message fully to determine which stage generates it.

There are Transforms for extracting the date portion of a Timestamp, or you can use or etc.

It sorts ROWS.
The sort key only serves to specify the basis of how to sort the rows.

This is true of every sorting mechanism, not just DataStage's.

The rules are different in other countries, particularly in the southern hemisphere.

But DataStage still picks up its time from the operating system, even if water and weather do spiral the other way.