• 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. Digital Implementation
  3. command description needed

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 91
  • Views 13162
  • 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

command description needed

svcadence
svcadence over 16 years ago

Hi,

Can anyone explain me about the following commands in SOC encounter

unlogcommand selectinst

logcommand selectinst

Thanks,

sv

 

 

  • Cancel
  • BobD
    BobD over 16 years ago

    They're non-productized commands (meaning you're free to use them but they're not officially supported) that give you a way to influence which commands are logged (in your .cmd file and in your .log file with the <cmd> notation).

    One situation where they can be useful is if you're written a custom proc and you want that to appear in the log file with a <cmd> notation and in your .cmd file, you can use the logCommand command to achieve this behavior.

    Another is if you've found that a certain command is being logged thousands of times and you want to suppress that logging.

    Note that this doesn't influence whether the output of the commands is logged- just whether the command itself is logged.

    Let me know if that doesn't explain it.

    Thanks,
    Bob

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • svcadence
    svcadence over 16 years ago

    Thank you Bob,

    Iam clear with your explanation..

    Thanks,

    sv

    • 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