Afterwards, you can found the
LMExec.exe file and launch it. It has a simple
interface (see picture) to open a script, execute it and see its progress log.
Openbutton in the top-right corner. You can press then the
Startbutton in the bottom-left corner to execute it. After the execution of the script has finished, you can start it again using the same button.
If an error occurs during execution, you can switch to a text editor, change
script at given position and save changes. You can press once again the
Start button to run the updated version of the script, without a need
to open the script again or even to restart the LM Exec module.
You can cancel a running script by the
Cancel button. Be
aware that this button functionality depends on the actual script code. It
will not work if the script is stalled (eg. in an infite cycle).
You can also pause the execution, instead of outright cancelling the script.
In this case you can export the log history (see later) and then re-start the
script using again the
All the errors and warnings are logged and displayed during the script execution. So are the main Lua-script function calls and selected time-consuming LISp-Miner operations (depending on the log verbosity level).
If an error is encountered during the execution, the script is aborted and a
description of error appears in the log together with the line-number on which
this error had occurred. User-defined debug-messages could be logged using the
log function (or its variants) from
You can copy the whole log into clipboard by pressing the
button. The log is also automatically saved into the
Each parameter has a syntax of
/ScriptParam:<Name>=<Value>. Parameters are accessible from within the script using the lm.ScriptParam table followed by the parameter name.
LMExec.exe /Input:LMExec.Demo.Z.b.ScriptParam.lua /ScriptParam:FirstParam=Alfa /ScriptParam:SecondParam=2
lm.logInfo( "First parameter value is "..lm.ScriptParam.FirstParam);
lm.logInfo( "The second parameter value is "..lm.ScriptParam.SecondParam);