More about file locking in cadence

Hi,

after having read the postings regarding the file locking mechanism in
newer versions of cadence I decided to do a little research.

I have versions ic446 ic500 ic5032 ic5033 ic5033usr1 ic5033usr1
installed. We do not use versions of cadence older than ic446 so the
clsbd cdsd problem is not present. (or should not be, at least).

The problem that I have is when I want to edit the cds.lib in
ic5033isr1 I get a message that the file is not edit locked and that
the file is read only. So far I have solved this by using the save as
function and overwritten the cds.lib. I started to do a backtrace to
find what version started giving me these problems, and I found that
between ic5032 and ic5033 things started to change, not only the
splash screen showing up when icms starts, but also this message about
failing edit lock on cds.lib.

I have set the DD_DEBUG_NEWLOCK to 3 and find that the two versions
use same functions to set and free the locks. (ddLockSetEx and
ddsNewLockFree) From the logs I cannot really find a difference.

I also do
CLS_CDSD_COMPATIBILITY_LOCKING=NO
DD_DONT_DO_OS_LOCKS=set

I have used clsAdminTool to do an are . on my work directory, and
there were no locks to release.

I have also checked the ownership of the directory where I am working,
but as ic446 and ic500 can edit the cds.lib without the message, I
guess that is not the cause. I have also stopped clsbd and restarted
it, it is the one from ic5033 running. I have even stopped the ic5033
and started the ic5032 clsbd and ic5032 is working fine and ic5033
still shows the problem.

It is not a critical problem, but it is very anoying. I would be happy
to get some feedback from other ic5033 (and newer) users that have
solved this problem.

 

Hi Svenn,

A change was made a little while back (IC5032/IC5033 timeframe, as you note)
so that the library path editor did not lock the cds.lib by default. The reason
for this is that potentially the library path editor could be left open, keeping
a lock for a long time. Then other things that want to add libraries (e.g.
File->New->Library in DFII) wouldn't be able to, because the lib path editor has
an exclusive lock.

If you want to obtain a lock on the file, you can then do Edit->Exclusive Lock.
Having done that you can quite happily save as normal, and then
do Edit->Exclusive Lock to free the lock (or exit the library path editor). No
need to do File->Save As in this case.

In IC5141, and the upcoming IC5033 USR3, two new cdsenv settings were added:

cdsLibEditor.main autoExclEdit boolean nil
cdsLibEditor.main warnExclLock boolean t

(this shows the defaults). The first controls whether it will automatically get
a lock when the library path editor is started - the default is not. The second
controls whether the popup warning appears or not.

So the issue is specifically to do with the library path editor behaviour and
not a general locking system issue.
Regards,

Andrew.