Background/Phantom process commands

The :background-start command starts the background processor. The background command will not run unless the background processor has been started with this command. This command is automatically run by the coldstart procedure.

The :background-stop command stops the background processor. The background scheduler will no longer be able to run. Jobs can still be queued for execution when the scheduler is not running, but they will not start. This command has no effect on backgrounds that are already running. To stop those jobs, they must be logged off.

The background command starts a phantom job with rerun and delay facilities.

The backgrounds-disable-missed command disables running any scheduled background processor jobs that were missed due to the background processor being stopped (either manually or because of a service disruption).

The end command terminates a process on another port, or the current port if a port number is not specified.

The list-backgrounds-missed command lists any scheduled background processor jobs that were missed due to the background processor being stopped (either manually or because of a service disruption).

The startsched command starts the phantom scheduler, which itself is a phantom process. The scheduler is normally started on the last phantom port of the system.

The stopsched command halts the phantom scheduler process. No phantom processing can occur if the phantom scheduler is deactivated.

The z command starts a phantom job. Phantom jobs run in the background, meaning that they do not necessarily need a terminal present.