resetting aborted jobs

tgoehring · Post by **tgoehring** » Tue Jan 25, 2005 11:02 am

We have DataStage 7.x. We have batches that submit a whole host of jobs simultaneously. Sometimes they all fail. To rerun this we have to reset all of the jobs in Director individually from their "abort" status. Is there a way to reset all the jobs at once from an "abort" status in Director or Designer or some other DataStage app?

Thank you for all your help

kcbland · Post by **kcbland** » Tue Jan 25, 2005 11:11 am

Mass-compile the jobs. Or, use better job control that resets a job after it fails or prior to running.

scottr · Post by **scottr** » Tue Jan 25, 2005 11:51 am

kcbland wrote:use better job control that resets a job after it fails or prior to running.

Bland can u expalin how can we achive this-

thanks in advance

kcbland · Post by **kcbland** » Tue Jan 25, 2005 12:00 pm

If you use Sequencer jobs, then use the option to reset and then run. If you are using Batch jobs, add logic to get the job status and if necessary run with a reset mode, wait for it to finish, then run as normal. All of the APIs are documented in your DS BASIC manual.

scottr · Post by **scottr** » Tue Jan 25, 2005 12:17 pm

what if 1)some jobs are scheduled through DataStage Schedular
2)some jobs are scheduled through CRONTAB

chulett · Post by **chulett** » Tue Jan 25, 2005 1:10 pm

The scheduler isn't part of this equation. What matters is how the jobs are run - via a Sequencer, via hand-coding / Job Control or directly via a script and 'dsjob' from the command line.

Each have different mechanisms and APIs for controlling resetting of aborted jobs.

kcbland · Post by **kcbland** » Tue Jan 25, 2005 2:53 pm

scottr wrote:what if 1)some jobs are scheduled through DataStage Schedular
2)some jobs are scheduled through CRONTAB

Directly putting a job into DataStage Scheduler is the same as use Windoze AT or Unix cron. You are not using job control. Job control means controlling jobs.

If you want to use DataStage Scheduler, you will not have the flexibility you require.

ray.wurlod · Post by **ray.wurlod** » Tue Jan 25, 2005 5:28 pm

DataStage scheduling on UNIX also uses at, rather than cron, if at is available.

You could, in this case, schedule two runs of the job. One in reset mode (whether it needs it or not) five minutes or so before scheduled exection time of the normal run.

This still offers no protection against future failure, if the conditions that caused the job to abort previously have not been remedied.

You should, however, prefer to wrap the job in a job sequence, where you can choose "reset if required, then run", and schedule the job sequence. It's a cleaner approach.