I know at times there are jobs that simply misbehave and will not stop properly. Of course the first step to stopping a job is to select the job in Director and click the stop button. And, most of the time this works just fine. However, there are times when this does not work.
When it does not work, and your job is running on a grid, what are the proper steps to ending a DataStage job as cleanly as possible. I suspect the final step after trying all else would be to issue a kill command from the Unix command line; possibly from each compute node that it is/was running on. But what other steps should be taken to cleanly end a job that does not stop after issuing the stop command within DS Director.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2013-01-20T15:58:31Z by SystemAdmin
Pinned topic How to Stop a stubborn grid enabled job?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-01-20T15:58:31Z at 2013-01-20T15:58:31Z by SystemAdmin
SystemAdmin 110000D4XK7754 PostsACCEPTED ANSWER
Re: How to Stop a stubborn grid enabled job?2013-01-20T15:58:31Z in response to SystemAdminWell try clean up resources option in Director and logout the processes. I use the same when stop button doesn't help and it works fine (no job locking/corruption encountered so far).