DSXchange

"" is not the same as NULL. "" is legal for a key value. NULL is not legal for a key value, because a primary key column is necessarily declared to be NOT NULL. DataStage does not have Ab Initio's {} construct, or anything like it. Usual approaches are to use a transformation to change any NULL to a...

Someone also need to make the point that 800 rows/sec and 25 rows/sec can represent exactly the same performance in terms of volume/time. 800 25-byte rows and 25 800-byte rows contain exactly the same volume of data. Please don't rely on rows/sec as a measure between jobs unless you are totally cert...

It means you've hijacked this thread with an unrelated question.
Please post a new thread if, after searching for 30107 on the forum (it IS there) you can't find an answer.

we want to stop a running job at once No you don't, at least not by killing "the" process. The job consists of more than one process. There's a conductor process on the node where the job was started. There's a section leader process on each processing node. There's a player process associated with...

It's not easy. The status of each job is in its own RT_STATUSnn table. So a "UniVerse" approach would need to query every one of these tables, or at least the one in which you're interested. To get some feel for the amount of work involved, open Director in Status view and disable the viewing of Cat...

Who said you have to?

What's better depends on exactly what you're trying to accomplish. For example, if your source is a database, chances are that a join to a small table can be performed very efficiently during extraction, meaning that much less work for DataStage to do.

DRS can natively talk to Oracle, DB2, Sybase and Informix as well as using ODBC protocols.

ODBC is limited to using ODBC protocols, as documented in the ODBC API (manual from Microsoft Press).

What did you feel that the limitations were? You claim to have been able to feel them? There is, with any such model, a very tiny probability that two different values will generate the same result using algorithms like CRC32. The probability is low enough for us to feel comfortable even processing ...

Why not ask whomever told you, and enlighten us with their wisdom?

Input1 ----> T1 ----> HF | V Input2 ----------------> T2 ------> Target A passive stage (in this case the Hashed File stage) can not open its outputs until its inputs are closed. Therefore the lower Transformer stage (T2) cannot process the first row from Input2 until Input1 is completely processed...

And sometimes it's just a glitch in OLE Automation. These are nearly impossible to diagnose without lots of stuff from MSDN and deep knowledge of how Windows works. Sometimes you will get a "failed to write to/at address 0xnnnnnnnnn" message, sometimes not.

You will need to post the exact derivations you used in the Modify stage. Without these there's not really enough information for accurate diagnosis.

Only if its data type is string. If its data type is date, you must first convert to string (string_from_date in Modify stage would do). Only string data types (including ustring) support substring operations.

Yes, but why would you want to run a job if the job's already running and calling a function exposed in the DLL?

The business rule is documented in the Transform or the Routine that it invokes. (It's in the Code of the Routine, to explain why the particular algorithm used was chosen.)
This is one of the advantages of documentation.