Bottom Line On Top
It happens often that we want to upgrade Polyspace for some projects and still continue with the same release for old and current projects. Since R2016b and using MDCS with a Mathworks Job Scheduler it is possible to apply it to Polyspace. "*Since R2016b*" is important and if you have other releases, please contact Technical Support.
For instance, To be able to use Polyspace R2016a (included) and R2017b through same MDCS server, it is quite easy. You need to stop R2016a service, start a R2017b service after having update mdce_def R2017b file to point on release available since R2016a.
Steps to follow
- login with administration rights on the server.
- Install on the server MDCS and Polyspace R2017b. At end, you have one folder for R2016a and one folder for R2017b on the server.
- Then you need to clean the queue. I mean all jobs remained on MJS will be lost. So please download on a PC any Polyspace jobs that are remaining on the MJS (may be it has already been made). It can be done through one of the desktop side which can access to the R2016a MJS using Polyspace UI and the Menu>Open Job Monitor.
- You need then to stop the R2016a MJS. For that, please login on the server and stop mdce service using -clean option (same kind of command on Linux). <MATLAB R2016a>\toolbox\distcomp\bin\mdce.bat stop -clean.
Then uninstall service: <MATLAB R2016a>\toolbox\distcomp\bin\mdce.bat uninstall
- You need then to open mdce_def on <MATLAB R2017b>\toolbox\distcomp\bin and update field MDCS_ADDITIONAL_MATLABROOTS adding path to R2016a like it is written in the comments above the field (field is located at near end of the file). Note that if you want to also add other MATLABROOTS paths, it is possible as soon as release is also installed on the server. Field supports more than one path.
For instance, you can also have R2017a installed on the server, and then, cluster R2017b will manage R2017a jobs as well.
- Install and start you mdce R2017b service: <MATLAB R2017b>\toolbox\distcomp\bin\mdce.bat install.
Then Start it <MATLAB R2017b>\toolbox\distcomp\bin\mdce.bat start -clean.
You should have a message on the output displaying all the release available in the field.
Then you have to create one MJS and N workers for Polyspace (where N corresponds to the number of Polyspace Code prover licenses you have on your server). To do so you can use the admincenter UI.
Start <MATLAB R2017b>\toolbox\distcomp\bin\admincenter.bat like you did to manage MJS and workers using MJS R2016a (please refer to MDCS documentation to create MJS and workers - https://www.mathworks.com/help/mdce/index.html).
At the end, Polyspace MJS R2017b is available and accepts at least R2016a and R2017b jobs (and any other versions that have been set in MDCS_ADDITIONAL_MATLABROOTS field).
