DSJS.RUNFAILED not working in custom trigger
Moderators: chulett, rschirm, roy
DSJS.RUNFAILED not working in custom trigger
Hi All,
I have job (J1) which will fail and next job J2 should be triggered which is present in seqeunce. I have custom trigger as below
Activity name.$JobStatus = DSJS.RUNFAILED OR Activity name.$JobStatus = DSJS.RUNWARN,
But Job 2 is not triggered and it is not saying any error. Please help
I have job (J1) which will fail and next job J2 should be triggered which is present in seqeunce. I have custom trigger as below
Activity name.$JobStatus = DSJS.RUNFAILED OR Activity name.$JobStatus = DSJS.RUNWARN,
But Job 2 is not triggered and it is not saying any error. Please help
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
What is the actual exit status (e.g. from Director) of Job1 ?
In your scenario, if Job1 finishes with any status other than the two explicitly mentioned, Job2 will not be triggered. This includes not only DSJS.RUNOK (which is your intention) but also any other status such as DSJS.CRASHED.
In your scenario, if Job1 finishes with any status other than the two explicitly mentioned, Job2 will not be triggered. This includes not only DSJS.RUNOK (which is your intention) but also any other status such as DSJS.CRASHED.
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.
Since new status codes are occasionally added (such as at version 11 to account for queued jobs), it might be better and safer to use in this check. There might be another error status being set by the activity - in that case do as Ray suggested and print out the actual numeric value of the return code.
Code: Select all
Activity name.$JobStatus <> DSJS.RUNOK
Thanks for response.
Below are the details present in Director with exit status
JOB1 has finished, status = 3 (Aborted)
JOB1 did not finish OK, status = 'Aborted'
Controller problem: Unhandled abort encountered in job
Seq S1 JobControl (@Coordinator): Summary of sequence run
Sequence started (checkpointing on)
JOB 1 started
JOB 1 finished, status=3 [Aborted]
Exception raised: @JOB, Unhandled abort encountered in job JOB1
Sequence failed (restartable)
Controller problem: Unhandled abort encountered in job
and i tried with $JobStatus <> DSJS.RUNOK this is also not working, I am using custom trigger. Once the Job1 is abroted next trigger is not working or next job is not kicked. If i use Failed expression type it is working
Below are the details present in Director with exit status
JOB1 has finished, status = 3 (Aborted)
JOB1 did not finish OK, status = 'Aborted'
Controller problem: Unhandled abort encountered in job
Seq S1 JobControl (@Coordinator): Summary of sequence run
Sequence started (checkpointing on)
JOB 1 started
JOB 1 finished, status=3 [Aborted]
Exception raised: @JOB, Unhandled abort encountered in job JOB1
Sequence failed (restartable)
Controller problem: Unhandled abort encountered in job
and i tried with $JobStatus <> DSJS.RUNOK this is also not working, I am using custom trigger. Once the Job1 is abroted next trigger is not working or next job is not kicked. If i use Failed expression type it is working
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: