sequence unable to restart

mab_arif16 · Post by **mab_arif16** » Wed Jul 05, 2006 10:53 am

Hi
I have a sequence A which calls another sequence B(with option reset if required then run ),A is scheduled to run through cron tab,if B fails ,A is not able to restart in the second run .
What are the add check point options to be selected in both sequence A and B so that A can be restartable in the second run.
Thanks
Arif

kris007 · Post by **kris007** » Wed Jul 05, 2006 11:17 am

1.What is the error message you are getting?( Is it Job A has to be reset before it can be run?)
2.When Job Sequence B fails, what is the status of the Job sequence A.Is it in Aborted Status or Finished status.

If a Job is scheduled at particular time, and if that job aborts(finishes with status=3) then you would need to reset that job before you can run it at the scheduled time OR you would have to run it manually. In short, a scheduled Job has to be in Finished or Compiled state to be run at that time and not in aborted/restartable state.
IHTH

mab_arif16 · Post by **mab_arif16** » Wed Jul 05, 2006 11:39 am

kris007 wrote:1.What is the error message you are getting?( Is it Job A has to be reset before it can be run?)
2.When Job Sequence B fails, what is the status of the Job sequence A.Is it in Aborted Status or Finished status.

If a Job is scheduled at particular time, and if that job aborts(finishes with status=3) then you would need to reset that job before you can run it at the scheduled time OR you would have to run it manually. In short, a scheduled Job has to be in Finished or Compiled state to be run at that time and not in aborted/restartable state.
IHTH

The warning is job A needs to be reset ,If sequence B fails the status of A is finished .

kris007 wrote:In short, a scheduled Job has to be in Finished or Compiled state to be run at that time and not in aborted/restartable state.

Doesnt the reset if required then run option takes care of it.If the main sequence aborts then doesnt it reset itself automatically.

Thanks
Arif

kduke · Post by **kduke** » Wed Jul 05, 2006 7:54 pm

No the sequence itself does not reset automatically. If you compile it then it will not restart at the point of failure. The jobs within the sequence will reset themselves if you select that option on the job activity. Most of the time the sequence does not abort. It finishes with a warning.

mab_arif16 · Post by **mab_arif16** » Fri Jul 07, 2006 10:43 am

kduke wrote:No the sequence itself does not reset automatically. If you compile it then it will not restart at the point of failure. The jobs within the sequence will reset themselves if you select that option on the job activity. Most of the time the sequence does not abort. It finishes with a warning.

I sequence is calling another sequence in the job activity ,and if it use the option reset if required then run ,will the inside sequence reset .
Thanks
Abdul

srinivasvemula · Post by **srinivasvemula** » Fri Jul 07, 2006 12:49 pm

Can you be more clear in these terms:

1. When your sequence's B and A fails what is the STATUS that you see?
2. Are you sure that no job in Sequence B is failing?

Thanks

DSguru2B · Post by **DSguru2B** » Fri Jul 07, 2006 1:05 pm

mab_arif16 wrote: I sequence is calling another sequence in the job activity ,and if it use the option reset if required then run ,will the inside sequence reset .

Yes it will.

kumar_s · Post by **kumar_s** » Fri Jul 07, 2006 6:32 pm

The warning is job A needs to be reset ,If sequence B fails the status of A is finished .

Can you justify this statement. Are you sure that, B gives the warning that Job A need to be reset even if it is finished with success?