Job not aborting

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
SHARAD123
Premium Member
Premium Member
Posts: 54
Joined: Wed Jan 09, 2008 12:05 am

Job not aborting

Post by SHARAD123 »

Hi All,
I have a job control which attaches a job sequence, the job sequence calls two more sequences.
All the triggers are set to OK Condn.
But still if a job inside the sequence aborts, the next job within that sequence aborts: but the calling sequence executes till the last job and gives a finished status not an aborted status.

The flow is like:
1 Master Job Control
1.1 Sequence1
1.1.1 Sequence_1
1.1.1.1 Some job1
1.1.2 Sequence_2
1.1.2.1 Some Job2
1.2 Sequence2
1.2.1 Some Job
The case is if 1.1.1.1 aborts the 1.1.2 gets aborted but then the 1.2 sequece starts executing tilll the end.

Is there any way to make it abort if any job inside 1.1 aborts?
222102
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Yes. Propagate the warnings upwards by checking "Log warnings after activities that finish with status other than OK" and/or "Automatically handle activities that fail" and/or direct all failures to a Routine that executes UtilityWarningToLog. Detect these warnings in the job sequence at each level and act appropriately.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
SHARAD123
Premium Member
Premium Member
Posts: 54
Joined: Wed Jan 09, 2008 12:05 am

Post by SHARAD123 »

"Log warnings after activities that finish with status other than OK" and/or "Automatically handle activities that fail" "




But then where to find these options? Am using datastage 7.0.
222102
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You find them in 7.5. :(

Without that you're pretty much limited to explicitly handling failures through Failure triggers and routine activities that log warnings.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
SHARAD123
Premium Member
Premium Member
Posts: 54
Joined: Wed Jan 09, 2008 12:05 am

Post by SHARAD123 »

Thanks
222102
Post Reply