Sablassville
22nd November 2007, 18:06
I have a job that I start using rc.startjob script. After it runs for a long time (which is what I want) I want to stop it.

the job runs one session only. It is a custom session for an interface.

I need to kill the running bshell, have the Baan job stop cleanly and ready to run, and have the application lock released.

Can anybody help me please?

I have played with the bshcmd6.1 command and the "-k" and the "-e" don't leave the job in the free state and remove the application lock.

Thanks
Rick

suhas-mahajan
23rd November 2007, 11:41
Rick,

Hmmm...seems the issue is related to your custom session. Have you tried running it without job?

You can search here "kill", it has been discussed many times. You can kill user from BaaN or Oracle or OS level.

regards,

-Suhas

günther
23rd November 2007, 12:14
I do not agree that you have to kill the bshell!
1. Your Job runs only one session.
2. It's a customized session.

So, why don't you give the session a way to stop itself in a clean way? I have done that by using a timer (e.g. every minute or so) and some condition (a specific file is present, an entry within a table exists, maybe some more).

Günther