DSXchange

The "skip job #1" piece is an inbuilt capability. Select the "include checkpoints for restart" option in job properties of the sequence and recompile. The one before another is managed simply by having (dependency) links between activities in the sequence.

Does your company have any kind of an "Enterprise" scheduler?

ray.wurlod wrote:The "skip job #1" piece is an inbuilt capability. Select the "include checkpoints for restart" option in job properties of the sequence and recompile. The one before another is managed simply by hav ...

Ray,
thank you for responding to this post. I am looking at the job properties, but don't seen "Include checkpoints for restart" check box as an option. I only see the following check boxes under Compilation options,

1 - Add checkpoints so sequence is restartable on failure
2 - Automatically handle activities that fail
3 - Log warnings after activities that finish with status other than OK
4 - Log report messages after each job run

Thanks again,

Seyed

chulett wrote:Does your company have any kind of an "Enterprise" scheduler? ...

Craig,
Other than DataStage Director, I am not aware of any other Enterprise Scheduler that our organization utilizes.

Thank you for your help,

Seyed

That's too bad... and #1 is the option that Ray was referring to.

Seyed wrote:

chulett wrote:Does your company have any kind of an "Enterprise" scheduler? ...

Craig,
Other than DataStage Director, I am not aware of any other Enterprise Scheduler that our organization utilizes.

Thank you for your help,

Seyed

Using an enterprise scheduler for your dependencies and scheduling would be ideal but in its absence - If you do have shared/NAS directories accessible from all of those environments, maybe you could get creative with Flag files to imply successful completion of one sequence and the next sequence would utilize wait-for-file activities to get started.