Job Status = 3 (Abort)

Raftsman · Post by **Raftsman** » Wed Jan 16, 2008 12:33 pm

I have a sequence job with two jobs, ie.

Job1 ====> Job2

Exception =====> Termination (Stop Sequence)

I wanted to test the exception abort routine and entered an incorrect File name in Job 1 so that it would abort. It did. The problem I face is, Job2 started and finished and the sequence ended normally.

Does someone know why the sequence didn't stop before starting Job 2. I think it's because the sequence did react quick enough to catch the abort.

I also tried to enter a condition in the trigger which worked and Job 2 did not execute but still the sequence did not end abnormally.

Has anyone else encountered this.

Thanks,

kumar_s · Post by **kumar_s** » Wed Jan 16, 2008 12:37 pm

What was the trigger to Job2??
Is it Otherwise?? And you want to act Exception handler parallely?

Raftsman · Post by **Raftsman** » Wed Jan 16, 2008 12:41 pm

There is no trigger in Job 2. Last Job in the sequence.

Not sure what you mean about the Exception Handler parallel, Could you please clarify

kumar_s · Post by **kumar_s** » Wed Jan 16, 2008 12:46 pm

I was asking Trigger from Job1 to Job2. And the other one that I was mentioning is the Exception Activity. How do you expect it to trigger.

Raftsman · Post by **Raftsman** » Wed Jan 16, 2008 12:53 pm

First, the trigger in Job 1 is unconditional.

Second, normally when an abort occurs in any job, the exception handling module get initiated which in turn initiates the termination module.

We didn't want to attach error handling in all Jobs of a sequence. From the documentation, we were able to make a generic error routine.

Is this the case???

kumar_s · Post by **kumar_s** » Wed Jan 16, 2008 1:22 pm

Does log shows that Exception Handler been executed? What is the settings in Terminator stage? Like, "Send stop signal to All running jobs / Abort without sending Stop signal"?

Raftsman · Post by **Raftsman** » Wed Jan 16, 2008 1:42 pm

The exception handler is not getting initiated and my colleagues and I figure that the the subsequent job is getting fired off before the exception handler is hit. The subsequent job finished normally and takes over the initial exception.

One solution is to put a Terminator stage on all jobs. This ensures that the job reports the abort.

Any thoughts??

ray.wurlod · Post by **ray.wurlod** » Wed Jan 16, 2008 2:09 pm

Job1 needs an OK trigger or a Custom trigger, one that does not handle Failure (an Unconditional trigger does "handle" failure). When Job1 aborts, the Exception Handler should fire, provided that the "automatically handle activities that fail" check box in job properties is checked.

Raftsman · Post by **Raftsman** » Wed Jan 16, 2008 2:45 pm

Ray,

I have tried many thing and the exception handler doesn't fire. I tried setting the trigger and still it didn't work. I put Terminate stages to handle the Abort and it works. I still thing the second job causes confusion in the sequence. If I run one job it works.

ray.wurlod · Post by **ray.wurlod** » Wed Jan 16, 2008 5:29 pm

Please verify that "automatically handle activities that fail" is checked and, when it is, re-compile just to make sure. Let us know (I'm sure you will).

Raftsman · Post by **Raftsman** » Thu Jan 17, 2008 12:55 pm

Yes it is checked. I changed my design. There was a flaw in how the calling program received the abort. It did not catch it. It's works now.

I thought the forum was to be informative. Why the wisecrack "I'm sure you will" Like everyone in this forum, we try and learn from others. I respect your input, hopefully I can return the favor.

Sorry if my feedback offend you. It's not meant to be.

ray.wurlod · Post by **ray.wurlod** » Thu Jan 17, 2008 4:45 pm

Sorry you misinterpreted my intention - it was acknowledging that you are diligent in helping us to help you. Not everyone is.