When I used the -wait option it complained about a clash with the -nojvm
option. When I got rid of -nojvm it said it didn't recognise -wait although it still seemed to work. Anyway I've stuck with start /wait to be on the safe side. Pleasingly there are no error messages or warnings returned now.
+Also, you may need to copy the pathdef.m file to the Condor execute folder
+for the toolboxes to work (if you use them) e.g.
+
+ copy c:\matlab2012\toolbox\local\pathdef.m .
+
+This is useful in building standalone executables using the Matlab Compiler
+Toolbox (the mcc command) actually on a pool PC.
+
+The upshot is that the temporary Condor execute account(s) don't have a proper
+profile so you need to set up an artificial one for Matlab to work (thanks
+to MathWorks for pointing this out).
+
+If you don't include a "quit" command at the end of the M-file, the
+Matlab interpreter will hang around for ever waiting for the next command
+and the jobs will never complete. Hindsight - always 20/20.
+
{section: Additional Resources}
Many other sites are using MATLAB under HTCondor. Here are links to the documentation from just a few.
