DSXchange

Since you don't like using the forum and want an immediate answer, your problem is something to do with IPC stages, row buffering, inter-process, etc. You are either stalling in an active stage somewhere waiting on rows, probably from bad job design from what you initially stated. The easy answer is...

Hmmm, sounds like you're using defaults in jobs rather than feeding at runtime with job control. Maybe you should consider changing your standard?

Unless it's an acronym for World Class Solution, which of course could be about anything.

I have never heard of WCS in relation to a data warehouse. Did you try Googling? I did.

A CLEAR.FILE removes the PURGE.SETTINGS record in the job log, which means your auto-purge never works again. Bad idea.

I searched for mutex and got 72 matches. You've got some reading to do.

Please search the forum. This has been covered enough times.

I forgot to mention, but not to rub things in, but when I architect ETL solutions I push for an externalized audit repository of tables. I use custom job control that pushes process metadata into those audit tables so that jobs status, start time, end time, comments, parameter values, link values, a...

Well let's see if I can't take a fair shot at this. 1. Jobs can't be correlated to a project from the unix command line. The same job name in two projects can't be distinguished using a "ps -ef|grep phantom |grep DSD.RUN" statement. But, you can get a list of jobs executing. 2. Using dsjob, you can ...

Skip using ExecSH, use

It's always been an issue that DS Server threads get zombied when you Stop a job. It's your responsibility to do a "ps -ef|grep phantom" after stopping jobs to make sure there aren't zombies out there. You can kill them or ask that a DBA kill the Oracle session which will let the zombie die.

It's unfortunate that new members never realize that they're in the wrong forum, or don't care. They post a few messages, then go away and become lurkers. There's no punishment suitable...

It must be possible, however, as RTI jobs do this. Yep, Ray shows how it is how it's done. That's why whenever we have a billion row log file it's better to just do a Clear Log from Director, because it appears to read the purge settings, issue a CLEAR.FILE, and then rewrite the PURGE.SETTINGS reco...

What Ray missed today was a new poster going thru and replying to 8 month old topics. It made it appear that posters were posting again in the FAQ forum, but it was replies to posts.

How??? A CLEAR.FILE hashedfile is like a TRUNCATE command. It blows away everything in the file. Since all instances write to the same file, I don't know how you accomplish what you need. By the way, what are you trying to do?