Hi Richard,

It is a TSM server that have two instances.

Looking at the installation path we found the files dsmserv.lock and 
adsmserv.lock but the size is 0, and the content is empty when TSM is running.

The same is happening with the second instance.

But one curious thing is that if we try to launch another TSM from the path's 
that other TSM exists previously(and is up), it won't let you because the file 
adsmserv.lock and dsmserv.lock exist -> but the content is empty and filesize 
is 0. 

The FS got enough free space.

In other way, what do you think about killing TSM with kill -9 <pid> script or 
a "dsmadmc -se=<inst> -id=admin -pa=admin halt" script -> with this script 
someone could find the admin password... :-(((

Any comments will be appreciated !!

Thanks !!

Ibán


-----Original Message-----
From: ADSM: Dist Stor Manager on behalf of Richard Sims
Sent: Thu 14/12/2006 13:34
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] dsmserv.lock  and adsmserv.lock empty
 
Your posting doesn't say where you looked for the lock file.  In
Solaris, it is documented as being in /opt/tivoli/tsm/server/bin/, as
dsmserv.lock.

Note that a zero-length file can be a consequence of a full file
system at the time of attempted file creation, so check that.  Also
check the mtime timestamp on your lock files relative to the time
that your server started, to corroborate.

    Richard Sims