jasoncordell

Let me take a stab at this and see if I am on the same sheet here. You want to have a common job that is used by multiple jobs. This common job could change from time to time and you only want to make the change in one central place rather that many "copies" of this job.

The problem with DS jobs is that once you chain to another job, you are forced to follow the exit/chaining rules of that job (if exit 0 jump to job 4, etc). If this were the last step in the various chained jobs, then this would reduce the risk, but would still probably cause you some grief at some point.

If this common job wasn't the last step in a chain of jobs, then you have to figure a way to get back out of the chain that you just joined so you can get back to your original chain. This can be accomplished with various dummy files created in the preceeding job and specific exit codes in the common job to get you back where you want to be, but this could easily grow to something that you would need to flowchart to keep track of. You also run the risk of losing your true exit code for the task completion by using non-standard exit codes to jump you to other jobs.

If you are trying to save a few minutes of time, then this approach is definitely not worth it. If this is going to save you a lot of time, and if you have time to design it, this is potentially doable.

Let me know if I am way off track, or if I lost you somewhere.


Thanks,
Jason