UV Script to release Job Locks from Unix

nirav.parikh · Post by **nirav.parikh** » Thu May 26, 2011 4:28 pm

Can someone share a Job Unlock UV script which has automated the process of releasing job locks. That is a script which accepts just the project and job name and release all the locks associated with that job, the list.readu and "unlock user <userno> all " commands in a interactive script to make the lock administration and housekeeping tasks simpler.

I tried searching the forum a lot for this kind of script but could not locate one. It would be great if someone has already done this.

Regards,
Nirav

chulett · Post by **chulett** » Thu May 26, 2011 7:00 pm

I don't believe that method of releasing job locks is still valid in the 8.x release. Could be wrong, someone will know for certain.

PaulVL · Post by **PaulVL** » Thu May 26, 2011 8:08 pm

Mr Daignault knows how to do that. I bet you could corner him at the Vegas IOD and pry it out of him.

He's a UV wizard. Much like Sauron the first orchadmin.

ray.wurlod · Post by **ray.wurlod** » Thu May 26, 2011 9:07 pm

The unlock scripts for UV locks are already in place, in the DS.TOOLS menu. However, job locks are not necessarily held in the "UniVerse" (DataStage) database any more. The correct mechanism is to disconnect the owning session, which automatically releases the job locks.

Don't forget that having the DataStage deadlock daemon running will automatically release locks not held by valid processes periodically.

nirav.parikh · Post by **nirav.parikh** » Tue May 31, 2011 9:14 am

Thanks for all your responses gentlemen. Ray I am aware of the DS.TOOLS menu, it is just that I was trying to create a script which would abstract the UV commands, I do not want lot of people fiddling with UV commands as that can mess up things. So I wanted to create a script which would take the job name and project name as input and will release universe locks if any held by that particular job.

We have had issues with jobs hanging intermittently, where they do not process anything after the jobs are started and then we need to stop it and release all the UV locks along with the fifo files in order to rerun it, on rerun that same job completes successfully. We have a admin team who handle this cases and this team is a multi product admin team and we the datastage guys do not want to expose all the UV commands, so that someone does not mess up things by mistake. Meanwhile we are trying to find out the cause of the locks with the service provider.