How to clean up the particular job

venkat n · Post by **venkat n** » Thu Jul 21, 2005 4:56 am

How to clean up the particular job in the project

ArndW · Post by **ArndW** » Thu Jul 21, 2005 4:58 am

"Clean up"? Is that a reset or a delete or something else that you wish to do?

venkat n · Post by **venkat n** » Thu Jul 21, 2005 5:06 am

I mean job has been locked thatsy first i want to unlock and clear status file and all those things
please let me know how to do those things
first which one I have to do?
from client(director/Administrato) or unix server I have to cleanup?
which is the better method to unlock?

ArndW · Post by **ArndW** » Thu Jul 21, 2005 5:16 am

First of all, it is best to use the dsdlockd to clear up locks. When started, it defaults to checking for deadlocks every 15 minutes; this is better than trying to do it manually.

Manually go to the Director, and use the "Cleanup Resources" tab to find the locks and process and clean them up.

Amos.Rosmarin · Post by **Amos.Rosmarin** » Thu Jul 21, 2005 5:53 am

Hi Arnd

Can you please give some explenation on dsdlockd.
How to use it
Is it documented ?

I tried to execute it (using dsadm) and got

Must be Superuser to start Deadlock Daemon

thanks,
Amos

ArndW · Post by **ArndW** » Thu Jul 21, 2005 5:58 am

You can't (or shouldn't) start this daemon; if you run it as supervisor you will just sit there for 15 minutes until it wakes up. Edit the file dsdlockd.config and turn it on (start=1) and it will automatically get started the next time you start DataStage. The config file also lets you change the default interval from the factory settings of 900 seconds.

Amos.Rosmarin · Post by **Amos.Rosmarin** » Thu Jul 21, 2005 7:50 am

Thanks,

After posting the message I searched the dsexchange and saw there are many posts on this issue.

Do you recommand setting start=1 ?
If I set it on, is it good to work with the defaults (timer=900, res=0) ?

Thanks,
Amos

ArndW · Post by **ArndW** » Thu Jul 21, 2005 8:00 am

Amos,

yes & yes. If you have frequent cases where jobs are locked even though they shouldn't be then you might bring the time down to 10 minutes (600). I don't know why the installation default is to have this turned off, it is useful and saves people (inadvertantly) doing "kill -9"s in the hopes of getting jobs running again -- this way you can take a coffee break and have the system clear it up for you.