Job handlers allow mpsh to send a command to some external program to handle instead of executing it directly. For example: sending jobs to batch queues, execution on remote nodes, delayed execution via /bin/at, running a command in a new x-term window, etc. All job handlers are user configured. The handler is specified by a single letter, which is then the argument after "&". It is configured by setting an environment variable handler-x where x is the letter for the handler you want to configure. The handler can be given arguments as well. Some examples:

Configure job handler "q" to submit job to a batch queue, via the command "batch-submit". When a command is run with the "&q" option, batch-submit will be executed, with the text of that command as stdin. batch-submit can also be given arguments, for example "40" (presumably a batch queue priority level) in this example:

mpsh$ setenv handler-q="batch-submit"
mpsh$ command blah blah &q 40

Submit a job to "at" to run at a later time:

mpsh$ setenv handler-t="at"
mpsh$ command blah blah &t 6:00 pm

(See more examples in mpshrc_all)

Handing the command off to the job handler is not done in the background (unless the job handler has a '&' at the end of the line), and once it's accomplished, it is not listed as a running job.

Configured job handlers can be displayed with setenv:

mpsh$ setenv -sh
mpsh$ setenv -qh

And cleared:

mpsh$ setenv -ch