DSXchange

I was accessing a datastage job from my clients DS Server, while working on it my connection with DS server lost giving me an Error Message "Error calling Subroutine........". After that I closed and Opened DataStage Designer again, when I tried to access the Same job again, It now gave me a message saying "The Job is being currently accessed by another user". But no else is working on DS. I also tried to Release this Job from DataStage Manager and Director but in vain.
Please can any body help me in unlocking/releasing my DS jobs.
Thanks in Advance

Amit_111,

It's been said before but you can really help yourself alot by using <a href="search.php">search</a>. Searching for "Job Locked" gives 38 matches.

<a href="viewtopic.php?t=99125">Here</a>'s a good one that will help you.

John.

Amit_111 wrote:I also tried to Release this Job from DataStage Manager and Director but in vain.

Releasing a job is something completely different from what you think it means. Don't. As noted, search instead.

i guess you can always try to clear the status file. that should do the job most of the times. or the best turn around would be to rename that job, make a copy and rename the copy to its original name...this saves time when you are actually waiting for the job to be developed to proceed ahead on that day.

Do you have the DataStage deadlock daemon running? This will periodically clear the locks held by redundant processes.

Actually the Deadlock Daemon works well in certain Unix environments but I have found it is very negative with run-away process in HP-UX and SUN....IBM IIS (Ascential) Support recommends not using since its unpredictable and unsupported.....

I use to use all the time and have backed-off due to bad experiences....Just an opinion....

ray.wurlod wrote:Do you have the DataStage deadlock daemon running? This will periodically clear the locks held by redundant processes. ...

I have no idea of this "DataStage deadlock daemon " How to keep it running so that it will clear the locks periodically...It would be of a great help.

Also I didn't understood the diffrence between releasing a job and Unlocking? Is it really different or the same?

Also the Jobs were locked by my own userid i.e while i was working the connection lost....but still I am not able to Unlock/ release them through the manager or Director? Why is it so?....Please help..

Set the auto-start property in the dsdlockd.config file to 1. Restart DataStage - the deadlock daemon will start and remain logged in. It wakes every 15 minutes, or such other interval as is specified in the dsdlockd.config file.

Releasing a job is the old-fashioned way of creating a versioned, read-only copy of the job for deployment into production. It has nothing whatever to do with locking or unlocking.

The client tools can only see current processes, not defunct processes. You will need to learn about LIST.READU and UNLOCK commands on the server.

A series of video tutorials on just this topic will shortly be available (for premium members) on DSXchange.

Hi,

Go to DataStage Director Job Log. From the Lower pane note down your respective job's process number. Now go to Unix, fire the below mention command from command prompt for each job rather process number.

kill < process number >

I think this will work.

Thanks-
Pranab Das

Not if the lock is owned by an abnormally disconnected process. That's when you need the UNLOCK command on the server.

Hi,

Please find the steps below to unlock the job which has been locked. Please be aware that no one else is using the job.

1. Log on to DataStage Telnet Server (e.g. TELNET <ServerIP> )
2. Logon to Server using Username and password.
3. Type LIST.READU EVERY. Check for the job which has been locked and note down its inode number and user number.
3. Log on to UV Account. (LOGTO UV)
4. Type "UNLOCK INODE inode# USER user# ALL" to unlock all the file locks,
group locks, and record locks

Now open the job in DataStage Designer.

Not if the lock is owned by an abnormally disconnected process. That's when you need the UNLOCK command on the server.

Just wondering if having dsdlockd running can resolve locks left over by such disconnected
processes? Any idea/experience with this one?





Thanks
Ramesh

Yes it does, but does not provide instant gratification. The dsdlockd process by default only wakes every 15 minutes, and it can take two or three cycles to clean up after a defunct process - the first cycle detects the potential for a lock problem, the second cycle checks that the problem is still extant.