DSXchange

Agreed that's generated code, and it should never have inserted that Abort, because it makes it look as if that's the way the job gets stopped. Don't know why it got left in - the subsequent (also generated) call to DSLogFatal in the first post makes it clearer. Still need to emphasize that one shou...

Just as an aside, don't use the ABORT statement in job control. Use: Call DSLogFatal("Some meaningful reason for stopping", "Some context") instead. That way the controlling job will stop gracefully, and log a message saying why it stopped. A Call to DSLogFatal never returns. So ...

It's possible the stage GUI is opening up off-screen, so that you can't see it - and that's why the Designer appears to hang, as it's waiting for you to do something on the modal dialog you can't access. If that's the case, you can prove it by pressing the ESC key, and see if that makes the Designer...

Sounds like this might be related to the following bug reported against 8.1: "Clientside import fails to import server routines if server-only licence is applied. This affects the Designer and the clientside commandline inport tools, but not serverside import." There is a client-side patch...

Setting sort options on the link is really only a GUI cosmetic difference, compared to having a Sort stage on the canvas. The compiled Parallel job will still have the same sort operator in it. And as Ray said, having a Sort stage clearly visible is better practice, really.

"dsjob -run" simply starts the job, and the command exits as soon as the job has succesfully started up. "dsjob -run -wait" will wait until the job has finished. "dsjob -run -wait -jobstatus" will wait, and also return the final status of the job (Ok, Aborted, etc.) In ...