The start.ss command starts the spooler and the phantom scheduler.
start.ss {(options}
| options | f | Phantoms only |
| l | Phantom processes are started using the monitor located on the current (local) directory. | |
| z | Abs and monitor are not the same |
For UNIX: The start.ss command starts the UNIX processes, which supports the D3 phantom processes, if they are not connected to the virtual machine already. The monitor the phantoms use is controlled by the UNIX environment $path and the UNIX file /usr/lib/pick/pickname, created by the installation procedure.
On a configuration where more than one virtual machine is running, it is important to ensure that all processes on a given virtual machine run the same version of the monitor. Normally, when the virtual machine is booted, the start.ss command creates processes running the same monitor, found on /usr/bin, as the one currently executed by the line 0. This is ensured by executing a which command, which shows the monitor version such as:
7.3.0.LINUX
Monitors are deemed compatible if the first two digits are similar. If not, then the UNIX variable $path is scanned, and a compatible monitor is looked for on the given directories. If it fails, then start.ss complains and does not start the spooler nor the phantom scheduler.
The l option instructs start.ss to use the monitor on the current directory. For this option to work properly, the system-coldstart macro should be modified as follows:
cd /usr/mydir start.ss (l
When the l option is in effect, the $path UNIX variable is not used to find the correct monitor.
For Windows: The start.ss command starts the Windows processes. The monitor the phantoms use is controlled by the Windows environment.