DSXchange

What Vincent's flying fingers prevented him from typing accurately was 7.5x2

This is not the same as 7.5.2, which is a UNIX release.

If you have 7.5x2 you would not be getting this message, so I deduce that you have the wrong version.

Hashed files are not supported in parallel jobs. You have posted in the parallel forum and specified a parallel job type.

Post the question in the server forum if it is related to server routine (which the language appears to suggest).

What are the symptoms of "failure"?

How many headers do you want? Does that suggest why sequential mode works and parallel mode does not?

Any "mark" characters in <Key Column Value> ?
Any non-printing characters in <Key Column Value> ?

Send to sequential file and inspect with hex editor.

You are correct to assert that the FTP stage is not equipped to unzip / uncompress compressed files.

My concern would be with "/C=/Program: not found " from which it appears that somewhere (configuration file?) you have specified "C=" rather than "C:" in a Windows pathname. Given that the client software installs by default in C:\Program Files\Ascential\DataStage some reference in the client config...

You can also go to the Tracing tab when submitting a job run request and ask for statistics to be gathered for each active stage in the job. This can yield detailed timing and therefore allow you to further diagnose the "hot spots" within your design.

This is a Windows error, caused in the application software (DataStage client). You must report it as a bug to your support provider.

Derive asto start from -1, or as to start from some particular value like -6.

We have a job which actullay runs at 2500 rows per second....all of a shudden the row count has shuddenly dropped phenominally..now it is running at 9 rows per second which is not acceptable? statistics are updated after every run. What could be the posssible reason? What has changed? "Nothing" is ...

I don't have a problem with 25, or even 75, stage variables, in exactly the same way that I wouldn't have a problem declaring 75 local variables in a function in any programming language, if the need were there.

Right-click in the background area of the Monitor. You also get Show CPU which is almost vital information when tuning parallel jobs.

They've taken the option to check for orphans out of DS.TOOLS in recent releases. However, the command is still there. From memory it is either DS.CHECKER or DSR.CHECKER. Execute from the Administrator client Command window when you have exclusive access to the project.

Read the help on DSGetJobInfo() function. One of the things you can return is a list of invocation IDs.

Monitor is one of the four views available in the Director client.