• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. Cancel checkout of data.dm file

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 6458
  • 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

Cancel checkout of data.dm file

jaapvds
jaapvds over 1 year ago

the data.dm file of a library is checkout and temporarily changed. I would like to cancel this checkout and using the following command:

ddCheckin(ddGetObj(Lib"" nil "data.dm") "" "c")

However I get the following Error message:

om: Error 135: Can't overwrite local changes.  Use force switch.

How can I add the force switch to this ddCheckin command?

thanks

Jaap

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago

    Jaap,

    I think the message is coming from DesignSync (a Dassault MatrixOne product), so best to ask them. There appears to be some unofficial way of adding extra arguments, using something like "cx-f" (assuming the force switch needed is "-f") but it's not that clear to me whether this actually works. I think you need to find the underlying problem first - the "x" option for ddCheckin is not documented and no guarantees that it will work.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jaapvds
    jaapvds over 1 year ago in reply to Andrew Beckett

    thanks a lot Andrew,  this works.

    To give you a little bit more background on this. What I try to achieve:

    In order to run some OA db checks, I need to re-reference temporarily to another Tech File. After running the checks set the Technology reference back to its original one. 

    So what I did:

    1. change temporarily design-sync preferences: ddAutoCtlSetVars( 0 0 2 0 )

    2. change technology reference to another techfile using skill function: techSetTechLibName. The data.dm will be automatically checked-out

    3. run the OA db checks

    4. Cancel the data.dm check-out in order to have the original technology data back. For this I was using the SKILL command: ddCheckin(ddGetObj(Lib "" nil "data.dm") "" "c")

    5. Set the design-sync preferences back to it's original settings.

    As indicated earlier, the checkin command was showing following error message. What of course is understandable since I indeed made changes to the data.dm in Step2.:

    \o Info (gdm): Beginning Cancel Checkout operation...
    \o
    \o Info (gdm): lib/data.dm : som: Error 135: Can't overwrite local changes. Use force switch.

    To me, it looks like safe to use your suggested ddCheckin option

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information