DataStage Error: Job xxx is being accessed by another user

DataStage Error:  Job xxx is being accessed by another user  

Take below steps to get rid of locks in datastage --

• In web console check active sessions and if job is listed disconnect session.
  
  To view all active sessions:
  
  In the Web console, click the Administration tab.
  In the Navigation pane, select Session Management > Active Sessions
  
  The Active Sessions pane shows the users that are currently connected to the server.
  
  
  
•  Check for and clear any Universe locks:

From the DataStage (DS) Administrator:

1. Launch DS Director
2. Select Job > Cleanup Resources (if Cleanup Resources is disabled, go to step 10 below)
3. In the Processes pane, click Show All
4. In the Locks pane, click Show All
5. In the Locks pane, scroll to the job name in the Item ID field
6. Note the PID/User # associated with the job
7. Click on the PID # in the upper pane (Processes)
8. Click Show by process (Locks pane)
9. Click Release All (Locks pane)
10. Launch DS Administrator
11. In the Projects tab, highlight the job
12. Click Properties
13. Check Enable job administration in Director
14. Click OK
15. Click Close
16. Exit DS Director and relaunch
17. Perform steps 3 - 9 above.

From Unix/Linux:

1. Log into the server using the dsadm user.
2. cd to the DSEngine directory
3. Enter . ./dsenv to source the dsenv file
4. Enter ./bin/uvsh to get into DataStage prompt
5. At ">" DataStage engine prompt, enter LOGTO project name
6. Run LIST.READU EVERY to list all the locks
7. Check active record locks under "Item Id" column for job name or RT_CONFIG# or RT_LOG# (# matches the job description number
8. Write down the Inode numbers and user numbers associated with these locks.
9. Enter LOGTO UV
   
   If the LOGTO command is disabled, enter this command
   
   "CHDIR <path_to_the_DSEngine_folder>"
   
   (with <path_to_the_DSEngine_folder>=cat /.dshome under a telnet session on the DataStage server).
   
   The UNLOCK command lives in UV account.
10. Enter UNLOCK INODE inode# USER user# ALL
11. You can use Q to get out of DataStage engine

• Use cleanup_abandoned_locks utility to clear any abandoned locks. The cleanup_abandoned_locks utility deletes session locks from the Information Server repository that were left over from some usage of an Information Server suite application (e.g. DataStage).
  
  Login to domain layer using either root or Administrator user (for Windows)
  
  cd /opt/IBM/InformationServer/ASBServer/bin
  
  ./cleanup_abandoned_locks.sh (on Unix/Linux)
  ./cleanup_abandoned_locks.bat (on Windows)
  
  usage: cleanup_abandoned_locks
  -P,--password Password
  -U,--user User name
  -h,--help Print this message.