Hi,
I have placed a job in a sequence. Under the 'Job Activity' options there is a Trigger tab.
Under 'Expression', I have 4 options:
Unconditional
Otherwise
OK (Conditional)
Failed (Conditional)
Warning (Conditional)
UserStatus (Conditional)
Custom (Conditional)
My query is as follows:
I have two jobs in a sequence. If the first job aborts it has to write the same to log. Hence, if it aborts, 'Execution Failed' will be written in log.
But I need to run the second job regardless of whether the first job is successful or not. Hence, under the 'properties' for the first job activity, shouldn't I put the expression as 'Unconditional' and not Otherwise?
Can someone please confirm the same for me? Thanks in advance.
Trigger options in Job Activity in a Sequence
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 73
- Joined: Thu Mar 08, 2007 9:50 pm
- Location: Bangalore
Re: Trigger options in Job Activity in a Sequence
UNCONDITIONAL should be the trigger the next job irrespective of the status of the first job completion as per your requirement.Rea_Antony wrote:Hi,
I have placed a job in a sequence. Under the 'Job Activity' options there is a Trigger tab.
Under 'Expression', I have 4 options:
Unconditional
Otherwise
OK (Conditional)
Failed (Conditional)
Warning (Conditional)
UserStatus (Conditional)
Custom (Conditional)
My query is as follows:
I have two jobs in a sequence. If the first job aborts it has to write the same to log. Hence, if it aborts, 'Execution Failed' will be written in log.
But I need to run the second job regardless of whether the first job is successful or not. Hence, under the 'properties' for the first job activity, shouldn't I put the expression as 'Unconditional' and not Otherwise?
Can someone please confirm the same for me? Thanks in advance.
![Razz :P](./images/smilies/icon_razz.gif)
Baig
Nothing is Impossible in this world. TRY ..try till you Succeed.
Re: Trigger options in Job Activity in a Sequence
UNCONDITIONAL should be the trigger the next job irrespective of the status of the first job completion as per your requirement.Rea_Antony wrote:Hi,
I have placed a job in a sequence. Under the 'Job Activity' options there is a Trigger tab.
Under 'Expression', I have 4 options:
Unconditional
Otherwise
OK (Conditional)
Failed (Conditional)
Warning (Conditional)
UserStatus (Conditional)
Custom (Conditional)
My query is as follows:
I have two jobs in a sequence. If the first job aborts it has to write the same to log. Hence, if it aborts, 'Execution Failed' will be written in log.
But I need to run the second job regardless of whether the first job is successful or not. Hence, under the 'properties' for the first job activity, shouldn't I put the expression as 'Unconditional' and not Otherwise?
Can someone please confirm the same for me? Thanks in advance.
![Razz :P](./images/smilies/icon_razz.gif)
Baig
Nothing is Impossible in this world. TRY ..try till you Succeed.
Re: Trigger options in Job Activity in a Sequence
UNCONDITIONAL should be the trigger the next job irrespective of the status of the first job completion as per your requirement.Rea_Antony wrote:Hi,
I have placed a job in a sequence. Under the 'Job Activity' options there is a Trigger tab.
Under 'Expression', I have 4 options:
Unconditional
Otherwise
OK (Conditional)
Failed (Conditional)
Warning (Conditional)
UserStatus (Conditional)
Custom (Conditional)
My query is as follows:
I have two jobs in a sequence. If the first job aborts it has to write the same to log. Hence, if it aborts, 'Execution Failed' will be written in log.
But I need to run the second job regardless of whether the first job is successful or not. Hence, under the 'properties' for the first job activity, shouldn't I put the expression as 'Unconditional' and not Otherwise?
Can someone please confirm the same for me? Thanks in advance.
![Razz :P](./images/smilies/icon_razz.gif)
Baig
Nothing is Impossible in this world. TRY ..try till you Succeed.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I agree about Unconditional trigger.
You might create a second link with a Failure trigger, if you want to handle the Abort result specifically, for example by sending email.
You might create a second link with a Failure trigger, if you want to handle the Abort result specifically, for example by sending email.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 73
- Joined: Thu Mar 08, 2007 9:50 pm
- Location: Bangalore