• 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. Mixed-Signal Design
  3. LSF batch jobs are killed on closing ADEXL window

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 64
  • Views 16906
  • 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

LSF batch jobs are killed on closing ADEXL window

Casp
Casp over 8 years ago

Hi,

I am using IC6.1.6 and launching LSF jobs from ADEXL. I am using LBS --> batchq. 

I am facing a problem that when I close ADEXL window then it cancel my jobs as well. I read on this forum that it should not be the case.

Can you please help me in finding why it kills the running jobs?

Regards,

Kamran 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    My previous reply might have been slightly ambiguous. Regardless of how the simulation jobs (the "ICRP") get launched (either local, remote or via a queueing system like LSF), the default behaviour is for the simulations to end when you exit virtuoso or exit ADE. This is because there is a communication channel between virtuoso and these remote processes, and one end would no longer be available. It has to do something special to deal with that channel no longer being there.

    That's what the envSetVal is for - it tells it to use a different strategy. This means that if virtuoso exits - either abnormally (i.e. a crash) or manually - then the background jobs continue (well, for a manual exit, you get a popup asking you whether you want the simulations to continue). That doesn't happen if you close the ADE XL window though - the assumption then is that because you've chosen to exit the ADE XL window, you are stopping using the tool.

    The reason why it works for exiting virtuoso is to deal with the situation where there is planned maintenance for the machine where you've launched virtuoso, and you are being asked to log out - but don't want the sims which have been submitted on the farm to die.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    My previous reply might have been slightly ambiguous. Regardless of how the simulation jobs (the "ICRP") get launched (either local, remote or via a queueing system like LSF), the default behaviour is for the simulations to end when you exit virtuoso or exit ADE. This is because there is a communication channel between virtuoso and these remote processes, and one end would no longer be available. It has to do something special to deal with that channel no longer being there.

    That's what the envSetVal is for - it tells it to use a different strategy. This means that if virtuoso exits - either abnormally (i.e. a crash) or manually - then the background jobs continue (well, for a manual exit, you get a popup asking you whether you want the simulations to continue). That doesn't happen if you close the ADE XL window though - the assumption then is that because you've chosen to exit the ADE XL window, you are stopping using the tool.

    The reason why it works for exiting virtuoso is to deal with the situation where there is planned maintenance for the machine where you've launched virtuoso, and you are being asked to log out - but don't want the sims which have been submitted on the farm to die.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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