How can I unlock a job after it has been killed?

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
DWH-M
Premium Member
Premium Member
Posts: 46
Joined: Thu Sep 06, 2007 5:26 am

How can I unlock a job after it has been killed?

Post by DWH-M »

HI

my job got locked, I tried using datastage admin command to kill the process id,
after killing the process id also job is still showing , job is still accessed by another.
I tried in Datastage director also to clean up the resource.
can anybody help out in this

Thanks in advance

**Note: subject / content edited to be more descriptive - Content Editor **
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Tell the DS Admin that you NEVER kill processes associated with DataStage jobs. There are proper ways to stop jobs and remove their processes; kill -9 is not among them.

So, the job is locked, and the lock is owned by a process that no longer exists (a "defunct" process). Your DS Admin is going to need to identify the particular lock, using LIST.READU or similar command, identify the process associated with that lock, and issue an appropriate UNLOCK command. Or this can also be done from the DS.TOOLS menu.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
uegodawa
Participant
Posts: 71
Joined: Thu Apr 27, 2006 12:46 pm

Post by uegodawa »

DS Admin can unlock jobs using following commands.
#cd $DSHOME

#/app/ascential/Ascential/DataStage/DSEngine>bin/uv

>LIST.READU

this will display all the locks, check for that particular job and clear the lock as follows

>UNLOCK USER <USER_NO> ALL

e.g
Device.... Inode.... Netnode Userno Lmode Pid Login Id Item-ID.............
75551473 154909 0 50647 12 RU 14889 dsadm SeqFXAllsitesales

in this case Userno is 50647

so command would be:
>UNLOCK USER 50467 ALL

once it clears the lock issue Q to quit.
>Q

Then you should be able to open the job.
Thanks,
Upul
Post Reply