Tuesday, April 19, 2011

Removing cadence locks

First I found the clsAdminTool using the locate command but it should typically be in the technology folder. I then ran clsAdminTool to see if there were any locks on the project I was working on. I got some output along the following lines:

clsAdminTool exiting with status 0
tunis(stelescu): ~ $./CMC/tools/cadence/ASSURA-5141.3.20.022/tools.lnx86/bin/clsAdminTool -ale ostelesc/cadence
bash: ./CMC/tools/cadence/ASSURA-5141.3.20.022/tools.lnx86/bin/clsAdminTool: No such file or directory
tunis(stelescu): ~ $
tunis(stelescu): ~ $/CMC/tools/cadence/ASSURA-5141.3.20.022/tools.lnx86/bin/clsAdminTool -ale ostelesc/cadence
BEGIN: Edit Locks List
ostelesc/cadence/libManager.log.21300 bigshot.omic.carleton.ca 21300 1298070979
ostelesc/cadence/libManager.log.12926 bigshot.omic.carleton.ca 12926 1278702057
ostelesc/cadence/ass/superass/schematic/sch.cdb bigshot.omic.carleton.ca 29149 1275521699
ostelesc/cadence/libManager.log.32320 tunis.doe.carleton.ca 32320 1302741992
ostelesc/cadence/libManager.log.22129 bigshot.omic.carleton.ca 22129 1279648545
….
END: Edit Locks List

SUMMARY: A total of 131 Edit Locks were found in the directory hierarchy: ostelesc/cadence

To remove the locks simply use:

clsAdminTool -are FOLDER

END: Release Edit Locks.
SUMMARY: A total of 131 Edit Locks were released in the directory hierarchy: ostelesc/cadence
tunis(stelescu): ~ $

No comments:

Post a Comment