Overview of the different schedulers (or ‘run modes’) in murex
There are a few distinct schedulers (or run modes) in murex which are invoked by builtin commands. This means you can alter the way commands are executed dynamically within murex shell scripts.
This is a traditional shell where anything in a pipeline (eg cmd1 -> cmd2 -> cmd3) is executed in parallel. The scheduler only pauses launching new commands when the last command in any pipeline is still executing. A pipeline could be multiple commands (like above) or a single command (eg top).
This is similar to normal where commands in a pipeline are run in parallel except murex validates the stderr and exit status of the last command in any pipeline.
If stderr is greater than stdout (per bytes written) OR the exit status is non-zero then the scheduler exits that entire block.
This runs the commands sequentially because the stderr and the exit status of each command is checked irrespective of whether that command is at the start of the pipeline (eg start -> middle -> end), or anywhere else.
Like with try, if stderr is greater than stdout (per bytes written) OR the exit status is non-zero then the scheduler exits that entire block. Unlike with try, this check happens on every command rather than the last command in the pipeline.
->) Token: Pipes STDOUT from the left hand command to STDIN of the right hand command=>) Token: Pipes a reformatted STDOUT stream from the left hand command to STDIN of the right hand command|) Token: Pipes STDOUT from the left hand command to STDIN of the right hand command?) Token: Pipes STDERR from the left hand command to STDIN of the right hand commandrunmode: Alter the scheduler’s behaviour at higher scoping leveltry: Handles errors inside a block of codetrypipe: Checks state of each function in a pipeline and exits block on errorThis site's content is rebuilt automatically from murex's source code after each merge to the master branch. Downloadable murex binaries are also built with the website.
Last built on Mon Feb 13 09:18:06 UTC 2023 against commit f339958f33995895c1d997efcdbb8408d2c8d45f8b5f934.
Current version is which has been verified against 13950 tests cases.