DSXchange

There might be occasions when the date constraint fails to limit the return to a single row. For example, a patient can be admitted to hospital, or visit a doctor, more than once on the same day. If you're collecting "health service provisions" for that particular patient, constraining to a single d...

Did you list locks for ALL jobs? You will see locks held by defunct processes if you choose this option, rather than extant jobs (which have current processes associated with them). The job name will be in the report.

I vaguely recall that FTP will not permit redirection of the password. The way that DSExecute works (and, I assume, the way that the Execute Command activity works), is to fork a child process. Therefore you have redirection. You might like to try a Routine Activity, in which your routine uses PERFO...

Check out the readme file for version 7.5, where it talks about the job's exit status being available on stderr.

The dummy job that you configure contains the union of all job parameters in the project. When you change job names in the Job Activity, that Job Activity magically causes non-relevant job parameters to disappear. I keep the "master" job activity in a Job Sequence of its own, and copy from there to ...

Ascential have cunningly hidden job control documentation in the Server Job Developers Guide
That's because a job sequence is just a special case of a server job. :D

That's a stack trace that lets an engineer see how you got the error. The error was in transfer_rep.C and in a structured data type (the fixRunAnchor_f element of destConcField). Presumably this occurred in a (parallel) Transformer stage. There's nothing in that error message that helps to diagnose ...

Isn't it the same as in server jobs? For example

There's no good reason to edit the generated OSH. The correct solution is to get your job design right, so that it generates correct OSH.

Even if you did, recompiling the job will regenerate whatever OSH it will, rendering your editing efforts futile.

The most difficult situation I ever faced was an incompetent junior developer. The amount of time spent coaching and mentoring was about five times what I would have needed to do the job. The solution was to fire the incompetent person (a contractor who had claimed to be competent), with the recomme...

The user ID in the DataStage job used to authenticate to DB2 is the one that requires the privileges to system tables that I mentioned before. You are right in your assumption, but did not address the question of whether the DB2 user has sufficient privilege to system tables to import table definiti...

Lose the code. It's horribly inefficient, re-creating the output file for each row processed! Do it all in a job, with an Aggregator stage as Craig suggests. Is this really a parallel job, in which you're trying to use DataStage BASIC code? What kind of a routine is it (transform function, before/af...

MetaStage is a product of huge complexity. You simply can not use it sensibly out of the box. You MUST get some training first. Seriously.

Check with your support provider.

Does this happen with every Merge stage you use? If so, it could be that you lack write permission in the temporary directory (which you specify in the stage properties).

Or it could be a problem within one of those temporary files.

Create one Job Activity that runs a job with all possible parameters, and set these. Copy this Job Activity and paste it as much as you like.