DSXchange

how to kill pid of other users,if any one locked the job with there ids.
i need unix command to kill process ids of other users

su root
<<enter root password here>>
kill -15 the_pid

Killing the PID is not the FIRST thing you want to do. Also, killing the PID of another user is only possible if you're root or have root privs. Even if you kill the PID, it won't unlock the job.

First, try unlocking via Director.
Second (I just go here first), determine the lock that is in place on the job. Go to DS Administrator, Projects, highlight project, Command, issue "LIST.READU EVERY". Record the "Userno" for the process that has the job locked.
Third, issue command "UNLOCK USER Userno ALL"
Fourth, if third step fails, issue command "INSERT INTO VOC (F0, F1, F2, F3, F4, F5) VALUES ('UNLOCK','V','list_readu','E','BV','unlock');" This adds the UNLOCK verb to the specific project.
Then do third step again.

This will unlock the job. It will not kill the unix user's DS session that had the job locked.

Use with care and only as a last measure once you've determined the original user can't unlock the job on their own.

I prefer to use list_readu from the operating system, because I can pipe its output through filters like grep to narrow my focus. I also like to capture the header line:

I like that, Ray.

Is "unlock" available from the command line also?

to get unlock to work, create a symbolic link called unlock which points to list_readu. It's a magic trick - if list_readu is executing under the name unlock then it gains the functionality to unlock locks.

eh?

You're scaring me...

I tried it under my account (not dsadm). Like shooting into the ground so as not to hurt anyone.

So I get "Insufficient privileges to perform lock maintenance." Good.

So if I do it as dsadm.... just what will get unlocked?

-Craig

If you type in "unlock ALL", the answer is EVERYTHING. If you type in "unlock USER 12345 ALL" then only the locks held by USER 12345. It works exactly the same as UNLOCK from the UV account inside dssh/uvsh, because it is the same. Most commands for the engine are executable from the unix command line (clear.file, mkdbfile, etc) with synonyms in the VOC pointing to them, sometimes as other names though. UNLOCK and LIST.READU point to the same unix executable list.readu.

The need to have admin privileges doesn't go away just because you're executing from the operating system. The same restriction would occur if you used UNLOCK as a non-admin user at the TCL prompt.