Test Routine, infinite loop

PhilHibbs · Post by **PhilHibbs** » Thu Apr 21, 2011 4:56 am

I think my DataStage routine has an infinite loop in it - is there any way of interrupting the Test Routine dialog other than killing the Designer task?

ray.wurlod · Post by **ray.wurlod** » Thu Apr 21, 2011 5:59 am

chulett · Post by **chulett** » Thu Apr 21, 2011 6:43 am

Pull the plug?

kduke · Post by **kduke** » Thu Apr 21, 2011 3:50 pm

Reboot. Hard to kill a sleep command too.

MrBlack · Post by **MrBlack** » Wed Oct 24, 2012 12:04 pm

I was victim of this same situation and this is how I was able to solve it. I thought it was worth posting in case anyone else comes stumbling across this thread. I hope in the future DataStage will build in functionality into killing processes for when this happens because in enterprise applications, pulling the plug is often not an option.

I'm on the linux version, I don't know how it looks on windows. There should be processes called dsapi_slave This is the connection between your computer (client) and the server. Look for the dsapi_slave process that started at the time you ran your routine and kill it. Usually there will be 2-3 other parent processes related to the process you kill that should clean themselves up automatically.

References
http://www-01.ibm.com/support/docview.w ... wg21596423

PhilHibbs · Post by **PhilHibbs** » Thu Oct 25, 2012 2:09 am

That's pretty much the same as killing the Designer task, since Designer will have to be closed after you do that, and I think it's also necessary (under v7 anyway) to clean up the dsapi_slave process after killing Designer anyway.

saiwelcomes · Post by **saiwelcomes** » Thu Oct 25, 2012 6:15 am

Go to /tmp/ folder in your unix server box. Try searching for a file starting with Capture*.

Code: Select all

ls -l Capture*

It will list some file whose names starting with Capture*
Try the same command again and again for multiple times. If any of the file size is getting increased, forcibly delete the file. Otherwise your server memory will run out of the limits.

This has to be done in case any routine gets hung due to infinite loop or so.