SKILL code to lock a layout in the library.

Marben,

This could either be done typically with a design management tool or maybe just changing the permissions of the view in the library. However, I did (25 years ago!) write an example of using dd triggers to implement access control lists for a library. This is discussed in this post: https://community.cadence.com/cadence_technology_forums/f/custom-ic-skill/41763/ddregtrigger-trigger-a-function-when-a-cell-is-opened-for-edit plus the code is shared in https://community.cadence.com/cadence_technology_forums/f/custom-ic-skill/29819/libmanager-edit-trigger-callback/1335387#1335387

Andrew

Hi Andrew,

Thank you very much for your reply.

How about a SKILL code to make a lock file just like,

layout.oa.cdslck?, if lck file exist,, it can't be editted.

How to make a SKILL code to make a lck file for

the layout?

Please help.

Best regards,

Marben

The presence of a lock file isn’t enough. The lock file contains information about the process id and host name of the process which locked the file. This is so that the stranded lock recovery mechanism can check first whether the process which locked the file has now exited (maybe it crashed without freeing the lock, or was killed). If it can check and the process is no longer running then the lock can be safely reclaimed. So unless you leave a virtuoso open keeping the file open for edit (say), it will be possible to open the file for edit.

You could abuse the lock system by intentionally producing a malformed lock stake file (eg an empty cdslck) file. This can happen sometimes when disk fills up or quota is exceeded. Anyway, attempts to open in this case give a message about the lock stake file being malformed, and then the natural reaction of any user would be to clear that lock either using clsAdminTool or even just deleting the file. I wouldn’t advise relying on a malformed lock stake file. 

As you can see, I’m not convinced this is a good approach!

Regards,

Andrew