DSXchange

He did - in the other thread.

So... 'Automatic' mode?

That, in and of itself, is not a problem - as long as you delete the accidental post. And you can do that until someone comes along and replies to it. Like us.

Do not post the same question in multiple forums, it disturbs the natives. And there's no need to put "RE:" in your subject line, we already know that is what the question is "regarding".

(see? disturbed before I finished composing)

Describe "Job2" in gory, embarrassing detail.

StageName.$CommandOutput<1>="File Not Found"

It's no different from earlier versions except there's no Manager so you write the Routine in BASIC via the Director. First step would be to lay out your requirements for the routine in "psuedo code", words that explain all of the steps that it needs to perform in the proper order. Then code it. Do ...

Glad you got it sorted out.

Cool. Make sure you include one of the "wait" options with dsjob so that you know if it runs ok or not.

Then it should not be checkpointed and should always run. Are you certain it is being skipped?

Get rid of the spaces around the equal sign in the parameter name/value pairs.

Hmmm... ok. How "dynamic" are we talking about? If the number of different jobs are a small number, consider just branching to multiple Job Activity stages using triggers or the Nested Conditon stage. If you are going to stick with the dsjob solution, make sure you include one of the WAIT options, p...

Why not mark that stage as "Do Not Checkpoint"?

sshettar wrote:I know we would have to declare all the parameters in a file with all its values

No, you don't. It can run pretty much anything that returns a value or set of values.

Why in the heck would you not use a Job Activity stage for this?