Stats

  • Locked Locked
  • Replies 22
  • Subscribers 130
  • Views 30883
  • 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

License check sequence in IC6.1.3

Aramsh

 Hi All,

Does anybody know how to set sequence of checking license features in IC6.1? I always need to use GXL

but it always goes to L, XL, then finds GXL. It takes a while as we have license in remote server.

Is there a way to force always look for GXL?

Thanks in Advance!

Aram 

  • Aramsh

     Hi Andrew/Sunil,

    Thannks for the answers! I have already registered in COS with host ID

    Best Wishes!

    Aram

  • Aramsh

    Hello again!

    I set the following in .cdsenv file in my home dir

    designEditor.license    appsWhichNeverTryHigherTieredLicense    string    "Layout L,Layout XL,"
    designEditor.license    appsWhichAlwaysTryHigherTieredLicense    string    "Layout GXL,"

     but still I see thatIC tries to get L and XL first

    *WARNING* (icLic-3) Could not get license Virtuoso_Layout_Suite_L
    *WARNING* (icLic-3) Could not get license Virtuoso_Layout_Suite_XL

    Can you please advice what's wrong?

    Thanks,

    Aram

  • Andrew Beckett
    Hi Aram,

    Without trying it, I think you have them back to front. I think you'd want the Layout L and XL to "Always" try the higher tier? (Not sure, I'd need to re-read the solution and I'm replying from a handheld devices so can't easily do that right now).

    To be honest, the reason we changed this in ISR15 to the new cdsenv vars was to improve the flexibility. Before that, you still got some warnings...

    Andrew
  • Aramsh

    Hi Andrew,

    I have tried this as well, but it does not work either....

    designEditor.license    appsWhichNeverTryHigherTieredLicense    string    "Layout GXL,"
    designEditor.license    appsWhichAlwaysTryHigherTieredLicense    string    "Layout L,Layout XL,"

     

    Regards,

    Aram

  • Andrew Beckett
    I think the purpose of them was just to stop it asking you; the warning remains. You need the new cdsenv vars to stop it even looking for the lower tier licenses, and hence preventing the warnings.

    There is a workaround using $CDS_LICFLTR (I think there are solutions about this) which allows you to specify a script to deny access to licenses on the client side, but that's really overkill just to remove a few warnings. Better to move to the later ISR.

    Andrew
  • Aramsh

     Hi Andrew,

    Corect, I need to stop preventing even looking into license. And actually I don't care about warnings in 

    CIW window, so if $CDS_LICFLTR just helps to skip warning messages, that does not help at this point....

    Aram

     

  • Andrew Beckett

    If you have slow license access (due to a remote license server) then $CDS_LICFLTR could help, because it means that you can allow or deny the license locally, before it even tries to talk to the license server. Better is the ISR15 onwards feature.

    Regards,

    Andrew.

     

     

  • Aramsh

     Hi Andrew,

    Yes, we have remote license server. I have read the manual for CSD_LICFLTR, but it's not pretty obvious how to use it.

    What's the values for that variable, if I want to filter e.g L and XL features?

    Thanks,

    Aram

  • Andrew Beckett

    Hi Aram,

    Create a script, say called "licfilter.ksh" something like the following:

    #!/bin/ksh
#echo "Request to checkout $@"
case $1 in
    Virtuoso_Layout_Suite_L) exit 1;;
    Virtuoso_Layout_Suite_XL) exit 1;;
  esac;
exit 0

    Make the script executable, and then do:

    setenv CDS_LICFLTR /path/to/licfilter.ksh

    Then start virtuoso.

    Regards,

    Andrew.

  • Aramsh

     Hi Andrew,

    Thanks for the script. Actually we use tcsh, but I will try to modify it!

     Best Regards,

    Aram

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.