I've searched the docs and the forums, but can't find much to go on for this problem:
I have a sequence job that is scheduled to start in the morning, runs all day waiting for input files, processes them through a few server jobs, then loops back and waits for more input until a certain time of day passes. At that point, I route to a Terminator stage to nicely ask the jobs to stop and then exit.
This all works fine, but when the Terminator executes, it logs an Abort in the job log. But I don't want an Abort -- this is not an unexpected failure, but normal successful completion at the end of the run window. We send emails to Admins on abort, and we run reports every morning looking for aborted jobs, because we take them to mean something bad happened that we need to fix. I don't want to pollute those logs with bogus 'failures', or send unnecessary problem emails.
It doesn't look like there's any way to make the Terminator log a different status. Is there any other technique I can use to cause the sequence job to exit cleanly? I'm OK with logging a warning, but don't want an abort.
Is there anything in DataStage Basic, the built-in routines, a shell script, etc. that I can use to stop the job without Abort?
Thanks!
- Val
Exit cleanly from a Sequence job?
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I prefer to use a Routine activity as a sink, so as to log an entry reporting that the job sequence reached that point.
You could use UtilityMessageToLog as the routine. I don't, because it returns 1 - I use a clone of it that always returns 0.
You could use UtilityMessageToLog as the routine. I don't, because it returns 1 - I use a clone of it that always returns 0.
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.