pvm_spawn — Starts new Scilab processes.
[tids, numt] = pvm_spawn(task, ntask, [nw], [where])
started. The Scilab script must already reside on the host on which it is to be started. The name must an absolute path.
integer, specifying the number of copies of the scilab script to start.
string (optional). If win is equal to ``nw'' the Scilab process will be spawned in background with out any window coming up.
string (optional), can be a host name such as ``machine.domain.country'' or a PVM architecture class such as ``SUN4''. If you want to use localhost as host, set
where value to
integer, the actual number of tasks started. Values less than zero indicate a system error.
row of integers, array of the tids of the PVM processes started by this pvm_spawn call.
copies of the scilab script
On systems that support environment,
pvm_spawn passes selected variables from parent
environment to children tasks.
If set, the envar
PVM_EXPORT is passed.
PVM_EXPORT contains other names (separated by
':') they will
be passed too. This is useful for e.g.:
setenv DISPLAY myworkstation:0.0 setenv MYSTERYVAR 13 setenv PVM_EXPORT DISPLAY:MYSTERYVAR
The hosts on which
the PVM processes are started are determined by
where arguments. On return the array
tids contains the PVM task identifiers for each
pvm_spawn starts one or more tasks,
numt will be the actual number of tasks started.
If a system error occurs then
numt will be < 0.
numt is less than
then some executables have failed to start and the user should check the last
locations in the
tids array which will contain error codes
(see below for meaning). The first
tids in the array are always valid.
When the argument
is omitted an heuristic (round-robin assignment) is used to distribute the
ntask processes across the virtual machine.
In the special case where a multiprocessor is specified by
pvm_spawn will start all
copies on this single machine using the vendor's underlying routines.