Job is being accessed by another user

andet14 · Post by **andet14** » Wed May 12, 2004 9:20 pm

My desktop crashed while I was editing a job, after I logged back in I got the 'Job is being accessed by another user' message. I know the message is caused by the PC crash but I don't know how to unlock the job.

Does anyone know how to unlock a job that isn't being edited by anyone?

Thanks
ta

vmcburney · Post by **vmcburney** » Wed May 12, 2004 9:54 pm

It's been covered many times before, just do an archive search on unlock job for lots of threads such as this one:
viewtopic.php?t=85560

andet14 · Post by **andet14** » Wed May 12, 2004 10:20 pm

Thanks, I thought this would be common but I couldn't find a search tool.

richdhan · Post by **richdhan** » Thu May 13, 2004 1:40 am

Hi All,

I searched the archives on the LOGTO topic and this is what I found

Code: Select all

Go to $dshome (which should be .../DSEngine) 

bin/uvsh 

LOGTO [project name where the job is] 

DS.TOOLS 

Select 5. 

Select 4. Identify the job listed. 

Select 1. (4 only shows the last 5 digits of the PID, use this option to 
show the entire PID. This is a known bug with at least 6.0.1, but this, 
again, is an undocumented feature.) 

Select 7. 

Enter the PID identified. 

Press enter/return key a few times to return to '>' 

Type QUIT

Since Iam working on PX I used PXEngine instead of DSEngine and I gave the command bin/osh instead of bin/uvsh. Am I correct upto this point. Pls clarify?

When I gave the command Iam getting the following error

exec(): 0509-036 Cannot load program bin/osh because of the following errors:
0509-150 Dependent module liborchoslaix3.a(libtemp.o) could not be loaded.
0509-022 Cannot load module liborchoslaix3.a(libtemp.o).
0509-026 System error: A file or directory in the path name does not exist.

Is this because I dont have the right access or priveleges.Pls clarify?

Thanks
--Rich

For andet14: A search tool is provided.Pls follow the Search link provided above to use the search tool.

sekarshah · Post by **sekarshah** » Fri May 14, 2004 2:00 am

Please use Datastage Director and clean up the resource. then try to open your job it will open with out problem.

Thanks
Shah

ray.wurlod · Post by **ray.wurlod** » Fri May 14, 2004 5:50 am

Since Iam working on PX I used PXEngine instead of DSEngine and I gave the command bin/osh instead of bin/uvsh. Am I correct upto this point. Pls clarify?

You are not correct. Locking of design time objects is performed in the DataStage engine.

You should execute neither osh nor uvsh. You should execute uv. Its pathname is $DSHOME/bin/uv (if you are on release 7.x) or `cat /.dshome`/bin/uv (if you are on releases 5.x or 6.x) or `cat /.uvhome`/bin/uv (if you are on earlier releases). In all cases, if you are on UNIX, you need first to have executed the dsenv shell script in the DataStage engine directory.