Job abort communication in Sequence calling Sequence
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 158
- Joined: Tue Mar 15, 2005 3:16 am
Job abort communication in Sequence calling Sequence
Hi
We have the project design as follows: (This is been designed to have generic format)
Main sequence -> calls ->Sub sequence -> calls ->Underlying jobs, depending on condition
In main sequence, We are passing a parameter, for the specific job to run from the sub sequence.
In the main sequence, we are updating the log whether particular job finished or aborted.
Currently what is happening is, when the underlying job aborts, then it is not recording as aborted by main sequence, because of not passing that information by sub sequence.
Is there any way to pass the underlying job status information to the calling main sequence from sub sequence?
Thanks
Sai
We have the project design as follows: (This is been designed to have generic format)
Main sequence -> calls ->Sub sequence -> calls ->Underlying jobs, depending on condition
In main sequence, We are passing a parameter, for the specific job to run from the sub sequence.
In the main sequence, we are updating the log whether particular job finished or aborted.
Currently what is happening is, when the underlying job aborts, then it is not recording as aborted by main sequence, because of not passing that information by sub sequence.
Is there any way to pass the underlying job status information to the calling main sequence from sub sequence?
Thanks
Sai
-
- Participant
- Posts: 158
- Joined: Tue Mar 15, 2005 3:16 am
Why not use a Routine in your main sequence to get the status of each job after all of them have finished? You could use the following to read the status of each job -
where hJob is the Job Handle.
Code: Select all
DSGetJobInfo(hJob, DSJ.JOBSTATUS)
gateleys
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
Re: Job abort communication in Sequence calling Sequence
Why not update the log from the sub sequence? Update the log as and where the job gets calledsaikrishna wrote: In the main sequence, we are updating the log whether particular job finished or aborted.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You can prevent the sub-sequence from aborting by explicitly handling failure of its activities.
You can set the compile options automatically to log a warning if an activity fails to finish successfully.
You can create a routine that writes an informational or warning entry into the controller's log using the DSLogEvent() function, and invoke that via a Routine activity in a control path that handles errors.
You can set the compile options automatically to log a warning if an activity fails to finish successfully.
You can create a routine that writes an informational or warning entry into the controller's log using the DSLogEvent() function, and invoke that via a Routine activity in a control path that handles errors.
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.
-
- Premium Member
- Posts: 24
- Joined: Thu Jun 21, 2007 1:20 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 158
- Joined: Tue Mar 15, 2005 3:16 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Log warnings for any activity that fails to complete successfully. That will alert the parent sequence that there is something for which to search. It can use a routine that invokes DataStage API functions to examine the log. If you use Exception Handler or explicit failure handling, you can also write directly to the log of the controller (again from a routine).
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.