• 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 Design
  3. License file format

Stats

  • Replies 4
  • Subscribers 129
  • Views 349
  • Members are here 0

License file format

threshold
threshold 8 days ago

Hi Community,

I recently came across a license format that contains only FEATURE lines, with no SERVER or DAEMON definitions. In this setup, the $CDS_LIC_FILE variable points directly to this license.dat file.

This is quite different from the standard configuration I have studied. Can anyone clarify if it is possible for the SERVER and DAEMON lines to be defined elsewhere, while the targeted file contains only the FEATURE lines?

  • Cancel
  • Sign in to reply
  • Andrew Beckett
    Andrew Beckett 8 days ago

    A colleague and I were discussing this today, and we've not seen this with Cadence tools (and can't really see how it would work). I have seen with other (non-Cadence) tools which use FlexLM that this is supported and works for single-user applications where there's no need for a license server, but never with our tools. There is (apparently) support for CDS_LIC_FILE to point to a directory of files and then these are concatenated, with the server/daemon being in one of the files - but I'm not aware of that being used in practice.

    Is $LM_LICENSE_FILE being set too? Maybe that is being set to a complete license file with the server/daemon lines or to the port@hostname format and that's being used instead and the (malformed) CDS_LIC_FILE is being ignored? That certainly works (it's much slower though, because it has to parse through the file looking for the server information, because we need that there and the USE_SERVER line too).

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • threshold
    threshold 8 days ago in reply to Andrew Beckett

    Hi Mr. Andrew, thanks for keeping the community alive.

    Both $CDS_LIC_FILE and $LM_LICENSE_FILE variables are pointing to the same license.dat file. I don’t find any HOSTID, EXPIRE DATE and NO OF SEATS in the license file, which makes me a little suspicious about the genuineness of the tools.
    Can I conclude that the tools are not genuine?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 7 days ago in reply to threshold

    There is one other mechanism that might be in use here, but I don't see it widely used (I used to set this up myself in the past before I worked for Cadence, but that was in the era of a single common release stream which incorporated all Cadence tools; it makes less sense nowadays). Anyway, assuming that it's Virtuoso you are using (you didn't say which tools), you'd locate the installation (in the UNIX terminal, type "cds_root virtuoso") and then under that path there is a <ICinstDir>/share/license directory. You can set up a clients file in that directory which tells the software where to find the licenses. More information is in <ICinstDir>/doc/license/license.pdf

    If it's not this, you should contact customer support (use the Case menu to submit a case after logging in). Something is clearly wrong in your setup anyway. At the very least you should speak with whoever is responsible for your software installation.

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • threshold
    threshold 7 days ago in reply to Andrew Beckett

    The Cadence tool is Virtuoso (IC618). I checked the share/license folder and I can see only the default sample files, not an actual license file. Since this is one of the client logins I happened to get access to, I tried to explore the setup. Usually I understand how the licensing is configured, but this one is very different from what I have learned.
    I will inform the client about this.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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