DSXchange

Help us help you - what is "not proper" about it?

OK, just to keep picking at this... that's almost a month. Was he saying that over that course of time your jobs generated 1000 processes or you've had 1000 processes all 'running' since that time?

Also, you didn't answer the aborted question.

I was told it happens often to beginners. Have whomever told you that explains what it means. :? When these jobs "finished running" did they run OK or did they in fact crash / die / abort? The latter can leave orphaned processes running, which may be what your comment maker meant. Oh and ...

You are probably correct but first I would suggest confirming that belief. Can you confirm what kind of processes they were? Post some examples?

For that suggestion, only the first column should be the 'key' in the Sort change in order to generate a proper Key Change column.

You could also look into what I seem to recall a Sequence job will do in a similar situation - use DSWaitForJob() but pass it a list of job handles to wait for. And it does. However, not aware of an equivalent from the command line, you'd need to make use of a routine and DSRunJob() to initiate them...

Then I would wager the suggestions were not properly implemented but there's no way to know that without including details of what you actually attempted. Let's stick with "Suggestion 1" for the moment, can you show us the stage variables, their derivations and the constraint you used? You...

You've gotten specific suggestions right here in this thread. Please be more specific with regards to what "did not work" about them. As Arnd noted, this seems pretty straight-forward to me so I'd be curious what issues you had with his approach in particular. And ps - none of the suggesti...

Not going to work that way, the deletes will be committed and then your inserts will start. They both need to be 'inside' the stage to be in the same transaction and that requires two links. The delete link needs to be ordered to run first and only needs to send 1 row to trigger the deletes. Which O...

Have you asked your DBA about this message?

What stage are you using? Typically you would get everything in a 'transaction' simply by using a single target stage with multiple input links.

You would need to have access to his 'KBA Job Control Utility' code for those to make any sense. I would imagine they could be... ignored.

That seems... fine... if all it is doing is make sure things are ready to go as you have no actual RUN mechanism in there. Have you tested it with a non-existent job? Asking because I looked for 'ERROR' in the jobinfo output rather than any kind of status value. And just a side note if this ends up ...

You can edit / change a job export through whatever mechanism you have skills in and are comfortable with. As to the compile question - yes but only on the client side.

Better answer would be to not be reliant on default values, sounds like a switch to leveraging parameter value files may be in order. There's nothing inherently different about editing a dsx vs. an isx, both are doable and carry the same level of risk. You keep saying 'routine' which has a very spec...