Schedulers

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.

Normal

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).

Try

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.

Try Pipe

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.

See Also

• Arrow Pipe (->) Token: Pipes STDOUT from the left hand command to STDIN of the right hand command
• Generic Pipe (=>) Token: Pipes a reformatted STDOUT stream from the left hand command to STDIN of the right hand command
• POSIX Pipe (|) Token: Pipes STDOUT from the left hand command to STDIN of the right hand command
• Pipeline: Overview of what a "pipeline" is
• STDERR Pipe (?) Token: Pipes STDERR from the left hand command to STDIN of the right hand command
• runmode: Alter the scheduler's behaviour at higher scoping level
• try: Handles errors inside a block of code
• trypipe: Checks state of each function in a pipeline and exits block on error