Methods of Releasing LOCKS in DataStage

3 methods for releasing locks in Datastage.

     1.via  Director client using cleanup resources.

     2.via UNIX box using DS commands

     3.Via DataStage Admin clients using DS commands

If a job is hanging or failing and not releasing locks, the first thing you  should do is Cleanup resources in Director.

If you  cannot remove the locks in Director's Cleanup resource then you can do it via uv command line. This can be done either via Administrator GUI command line or uvsh on Unix, they both do the same thing, it is just a different interface but there is no difference in the functionality.

Also, when it is a lock related to opening a job in Designer and then Designer crashing, the way to release it is from command line not in Director's cleanup resources.

Cleanup Resources is just for lock associated with running jobs.

---------------------------------------------------------------------------------------------------------
The job is not in running status? If it isn't then you would just need to manually remove the locks.

Please follow this techtip and let us know your results.http://www-304.ibm.com/support/docview.wss?uid=swg21390366
From Unix/Linux server:

    Log into the server using the dsadm user
    cd to the DSEngine directory
    Enter . ./dsenv to source the dsenv file
    Enter ./bin/uvsh to get into DataStage prompt
    At ">" DataStage engine prompt, enter LOGTO <project name>
    Run LIST.READU EVERY to list all the locks
    Check active record locks under "Item Id" column for job name or RT_CONFIG# or RT_LOG# (# matches the job description number)
    Write down the Inode numbers and user numbers associated with these locks
    Enter LOGTO UV
    Enter UNLOCK INODE inode# USER user# ALL
    You can use Q to get out of DataStage engine