DSXchange

Get your shared library search path correct, probably by sourcing the dsenv script before you launch into dsjob commands. Spend some time learning how operating system command parsers and search lists work.

You might try looking at this thread

wfis wrote:Need more insight on why not to go for Stable sort.

It requires more resources than not using it.

Which part of that is unclear?

That's one "solution". Another would be to execute stage(s) in sequential mode. Another would be to execute stage(s) in a single-node node pool within a multi-node configuration. My personal preference for processing a single row is a server job, where the startup and execution overheads are far low...

Where is the parameter coming from? You can not use parameters in the Command field in the Execute Command stage. You can only use them in the Parameters field. Therefore the solution that you require for this particular problem (assuming that there exists a job sequence parameter called "path" and ...

Get rid of stable sort unless you have reason to keep it. It requires more resources than not using it. Unless your other configuration file has more nodes than eight, it can not give better sort performance than eight nodes. You're only processing on average 27 million rows per node - this is not a...

I believe that their organization will contract to do that work using their own intellectual property (if asked nicely, with a purchase order).

It's a known bug, but yes that's how it is at the moment.

Let me clarify. You fixed something and suddenly everything is broken. Is that how it is?

If so may I strongly suggest that you back out that "fix" (you DO keep old versions of jobs, right?).

It's VarChar according to your original post in this thread. How you get it is irrelevant.

Message handler.

Four years is fairly easy. DateFromDaysSince() with an offset of (365 * 4 + 1). Only a problem if years like 2000 and 2400 (divisible by 400) are in the range.

Did someone create a local message handler in development? (There will be an entry in the log showing near the beginning that a message handler was attached, and another near the end if one was used.)

What does "parallel" mean to you? Are you running this job on two nodes?

There is a long-running discussion on DSXchange about this, for which you could Search. Parallel jobs do not handle "quoted quotes" properly.