Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 7282
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Schematics are getting locked

tawsaras
I have recently started using a new PDK for one of my projects.
In this PDK, they have provided us with a work folder, we have to source the cshrc file there.
All of the work, related to this PDK is saved there, not in the home folder.
Now because of this above restriction, Whenever I save a schematic in the work folder and log off. That schematic gets locked and I am not able to unlock it using the clsAdminTool command.
Parents

  • That doesn't sound like the way most PDKs would be set up - I'm not sure who "they" is in this case, but it sounds as if somebody has configured things so that you all work in a shared area. If that is the case, if somebody has a schematic open for edit, nobody else can edit it at the same time (that's the whole point of locking, to prevent data loss).

    Saving the schematic and then quitting Virtuoso should not cause it to be locked still - the lock should be cleared when Virtuoso exits. Even if Virtuoso exited abnormally (e.g. a crash), the lock recovery mechanism should handle this - in essence, any other session which tries to open the schematic for edit will check if there's a lock, and if so it will use the CLS boolean daemon (clsbd) to determine if that process is still running - if it isn't the lock can be reclaimed automatically.

    You should only need to use clsAdminTool in rare cases - typically only if a machine which was previously locking the machine is no longer on the network.

    I suggest you contact customer support - trying to understand your setup and what exactly is going on will be rather hard via the community forums.

    Andrew

Reply

  • That doesn't sound like the way most PDKs would be set up - I'm not sure who "they" is in this case, but it sounds as if somebody has configured things so that you all work in a shared area. If that is the case, if somebody has a schematic open for edit, nobody else can edit it at the same time (that's the whole point of locking, to prevent data loss).

    Saving the schematic and then quitting Virtuoso should not cause it to be locked still - the lock should be cleared when Virtuoso exits. Even if Virtuoso exited abnormally (e.g. a crash), the lock recovery mechanism should handle this - in essence, any other session which tries to open the schematic for edit will check if there's a lock, and if so it will use the CLS boolean daemon (clsbd) to determine if that process is still running - if it isn't the lock can be reclaimed automatically.

    You should only need to use clsAdminTool in rare cases - typically only if a machine which was previously locking the machine is no longer on the network.

    I suggest you contact customer support - trying to understand your setup and what exactly is going on will be rather hard via the community forums.

    Andrew

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.