DSXchange

It's there in Arnd's post (on screen #1), in blue.

Start time, end time and job status are not in DS_JOBOBJECTS table, which only contains design-time metadata. Run-time metadata are stored in a separate table for each job. You need to use the DataStage API (in one of a number of ways, perhaps a routine, perhaps the command line interface) to recove...

Trace level 1 is invoked only under two circumstances.

(a) stage tracing specifies "capture data"

(b) running in the Debugger

Avoid it by using neither of these. The default should be trace level 0.

It is not possible. You will need an additional job parameter containing the six-digit date. You can calculate the one from the other, for example using the Right() function, in the job sequence that invokes your job.

Which part of "remote server required" is unclear?

For some reason your DB2 is returning this string when its version is being requested, and DataStage does not recognize it. Take it up with your support provider.

Create a routine that ends up invoking DSSendMail() function. Invoke your routine from a Routine activity near the end of your job sequence.

It ("Reply to Topic") is at the top, too, and in a larger font than "Reply with quote".

I, on the other hand, adopt the approach of not having too many jobs in the project. Therefore "all jobs" still refreshes in a reasonable amount of time.

What's different about the jobs?

Trace level 1 means that every piece of data, as well as being processed, has to be logged to the stage trace file. That can be an immense overhead.

So you can see whether the merge was successful, assuming that your "update not found" rule is "Continue".

What information precisely do you want to get? Ultimately it will all be stored in DS_JOBOBJECTS table. But why not just use the Job Report tool in the job sequence itself? (This is the tool that looks like the Internet Explorer icon.)

QualityStage

... but there is an ODBC driver for SQL Server that can be (is) installed on a UNIX system on which DataStage is installed. Hence wesd's advice to use an ODBC Enterprise stage.

hey the best way is kill the sessions type ps -ef|grep dscs n see the PID and KILL -9 PID or go to Datastage Admin command n type ds.tools go through the options u can make it out u r done..... :D Aaaaarrrrggggghh! Don't ever work for me. It would be significantly dangerous for you.