Tell if MatLab is idle or not

The company I'm working for has a few hundred MatLab licenses but we're running out so they implemented a time out call that revokes your MatLab licenses if your computer is inactive for a few hours. When we run Design Verifier, Code Inspector and Model Coverage sometimes it takes 24+ hours to finish, and we lose our work when the licenses get revoked. So I was wondering if there was a way that you could tell if MatLab is idle and not doing anything or is it’s running simulations in the background when the computer idle.

Answer 1

[Andreas Goser]

There is a FLEXnet "timeout feature" that returns MATLAB after being inactive. The way this is set up, you should NOT loose work. I suggest that your license administrator gets in touch with MathWorks installation support to figure out details.

[Andreas Goser]

Documentation is here

[Duke]

I think this is how we have everything set up now. When I run over night and come back I see the following message:

Your MATLAB session has timed out.  All license keys have been 
returned.

But thats if there we're still licenses there, if my license gets returned and someone takes it them design verifier will have stopped or will continue to run forever. I've lost work because of this when MatLab was running and not sitting idle even if my computer was. So I only have an issue when my licenses are returned and then taken.

[Andreas Goser]

Let me see if I understand it correctly: When you return to work and see this message and then do something in MATLAB, then I'd say it should pull the key(s) from the relevant product(s). And you say that when your concurrent license is out of keys for Simulink Design Verifier, then your work is lost? But when such a key is available, then the work is not lost?

[Andreas Goser]

I am not too familiar with Simulink Design Verifier, but there should be results stored in a certain directory, a log file and a detailed analysis report. So I'd say the results are not lost.

In addition, a colleague mention some issues in earlier releases where the product seem to run for a very long time, but was actually done.

[Duke]

We run into the issue where it'll run for a very long time when it's done here, but I think I might have mistated what I meant. When the licenses get pulled and someone else takes them, I dont "lose" my work since all the files get saved off before hand, I just lose the time I had it running and since it was stopped early I have to rerun my tests.

[Andreas Goser]

Got it. So my fundamental statement is: As I understand it it should not stop and please contact installation support.