DSXchange

How have you proven that it's the sort time?

I always prefer an explicit Sort stage, because it allows me to allocate more memory to the tsort operator. This can result in quicker finishing. It also allows sort mode of "don't sort (previously sorted)" where applicable.

That's what you'd expect, since the month is 12 in each date.

You can use Director to set different defaults. Under the Job menu choose the Set Defaults option.

What else is happening? On the machine, in the job? Rows/sec can be a very misleading metric. What is the elapsed time for the Transformer stage?

The file you opened is the dictionary. It is (was) a hashed file. By overwriting it with text you have irretrievably damaged the hashed file structure, and therefore the file dictionary. What you needed to do was to open a file in the BASICCODE1 directory, not in D_BASICCODE1. You need to undo your ...

Did you check the error log (C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\.convert.4472)?

I'm guessing here, but I suspect that the "v" in "vsh" stems from Vality, the name of the company which was acquired by Ascential. Their product was called INTEGRITY, which Ascential renamed QualityStage.

Trim() function.

It appears to be a deficiency in the dsjob -import command. Report it to your support provider. Meanwhile, use Manager to import your shared containers.

You can not invoke a server routine from a parallel job. You can, however, invoke one from a Routine activity in a job sequence. Review the online help and/or manuals for the DataStage API functions. There is one family of functions with names beginning DSGet... that allow you to interrogate the sys...

Where and in what context did you encounter the terminology?

When the job is not able to push the data into SAP BW, what error messages are logged? Also check on the SAP BW side for any error messages.

Your computer seems to be deficient in some vowels.

I would design the DataStage job to do the detection - to perform the other "gathering" tasks whenever sending an update to XYZ. Then you don't need to worry about triggers anywhere.

Did you remove the User DSN when you created the system DSN?

Also try creating an entry in the uvodbc.config file in your project directory, in which you declare the DSN to be DBMSTYPE = ODBC (the spaces either side of the "=" character are required).

And anything else that's operating system specific, for example any calls to ExecDOS will need to be replaced with calls to ExecSH, BAT files will need to be re-written as shell scripts, the first (Shell) argument to DSExecute calls will need to be changed, and so on.

Someone is going to need to hack to discover how this works. It's clearly not a simple checkpoint mechanism when a loop is involved.