Using DS.TOOLS

nilotpalr · Post by **nilotpalr** » Tue Dec 10, 2002 5:37 am

Hi All,
I am using DS.TOOLS to clear the status file. The Datastage director shows the status as COMPILED. But when i view the log, new log messages are logged indicating that the job is still running. Also I am unable to compile the jobe from designer and the message given is that this job is still monitored.
Can any one tell me what is happenning.
Thanks in advance.
Nilotpal.

ray.wurlod · Post by **ray.wurlod** » Fri Dec 13, 2002 1:32 pm

This symptom usually means that there is a lock on the job, possibly held by a redundant process (particularly if the job has been stopped). Or maybe a previous run of the job IS still being monitored by another DataStage client (in which case shut down the monitor).
If the job is locked you need to identify which process is holding the lock and release it. You can do this via DS.TOOLS or via the Cleanup Resources option in Director.
Bouncing the DataStage Engine will also clear all locks.

srinivasb · Post by **srinivasb** » Mon Mar 10, 2003 11:06 pm

Hi Ray,

Thanks for the response ... by the way whats bouncing the DataStage engine?
Regards
Srinivas.B

vmcburney · Post by **vmcburney** » Tue Mar 11, 2003 6:20 pm

By bouncing he means stopping and restarting the DataStage services on the server.

ds -admin -stop
- Will shut it down.
ds -admin -start
- will hopefully bring it back up.

Obviously more drastic than cleaning up locks manually as it ends all connections such as logged in users and running jobs.

srinivasb · Post by **srinivasb** » Tue Mar 11, 2003 9:33 pm

Hi VMCBURNEY,

Thats very kind of you. I didn't know that jargon.

Thanks and Regards
Srini

mihai · Post by **mihai** » Thu Mar 27, 2003 6:11 am

If you don't want to/can't bounce the server, telnetting to the engine and issuing the command
UNLOCK ALL
should do the trick.

This should be done carefully, as locks will be dropped by everything (including scheduled jobs that are running at the time, your colleagues, etc).

Kind regards,
Mihai

ray.wurlod · Post by **ray.wurlod** » Thu Mar 27, 2003 5:45 pm

The "trick" UNLOCK ALL should do, if the system is set up sensibly, is to emit the message "insufficient privileges to execute command".

This is because unlocking every lock on the system without thought and due care may solve one problem, but will definitely create lots of others. For example, each connected client signals the fact by using a shared lock in the lock table. NEVER blow them all away.

Find out the process IDs (from files in the &PH& directory if necessary), or the user numbers (they will be the same on Windows, different on UNIX), and use a more targeted syntax of UNLOCK to clear just the locks for this process (exactly what DS.TOOLS does).

And you will still need Administrator rights.

If one learns from others but does not think, one will be bewildered.
If one thinks but does not learn, one will be in peril.
(Confucious)

Teej · Post by **Teej** » Fri Aug 08, 2003 10:39 am

nilotpalr wrote:Hi All,
I am using DS.TOOLS to clear the status file. The Datastage director shows the status as COMPILED. But when i view the log, new log messages are logged indicating that the job is still running. Also I am unable to compile the jobe from designer and the message given is that this job is still monitored.
Can any one tell me what is happenning.

It means a bug had reared its head.

Recompile the job and the "running" job will reset.

-T.J.

DSXchange

Using DS.TOOLS

Using DS.TOOLS

Thanks for the explanantion !!

Alternative to bouncing

Re: Using DS.TOOLS