1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
.TH pvm_spawn 1 "January 1998" "Scilab // Group" "Scilab function"
.so ../sci.an
.SH NAME
pvm_spawn - Starts new Scilab processes.
.SH CALLING SEQUENCE
.nf
[tids, numt] = pvm_spawn(task, ntask, [nw], [where])
.fi
.SH PARAMETERS
.TP 5
task : string, which is the file name of the scilab script (see exec) to be
started. The Scilab script must already reside on the host on which it
is to be started. The name must an absolute path.
.TP 4
ntask
: integer, specifying the number of copies of the scilab script to start.
.TP 4
win
: string (optional). If win is equal to ``nw'' the Scilab process
will be spawned in background with out any window coming up.
.TP 4
where
: string (optional), can be a host name such as ``tequila.ens-lyon.fr'' or a PVM architecture class such as ``SUN4''.
.TP 5
numt
: integer, the actual number of tasks started.
Values less than zero indicate a system error.
.TP4
tids
: row of integers, array of the tids of the PVM processes started
by this pvm_spawn call.
.SH DESCRIPTION
\fVpvm_spawn\fR
starts
.I ntask
copies of the scilab script
.I task.
On systems that support environment,
spawn passes selected variables from parent environment to children tasks.
If set, the envar \fIPVM_EXPORT\fR is passed.
If PVM_EXPORT contains other names (separated by ':') they will
be passed too. This is useful for e.g.:
.nf
setenv DISPLAY myworkstation:0.0
setenv MYSTERYVAR 13
setenv PVM_EXPORT DISPLAY:MYSTERYVAR
.fi
.PP
The hosts on which
the PVM processes are started are determined by
the
.I where
arguments. On return the array
.I tids
contains the PVM task identifiers for each process started.
.PP
If pvm_spawn starts one or more tasks,
.I numt
will be the actual number of tasks started.
If a system error occurs then
.I numt
will be < 0.
If
.I numt
is less than
.I ntask
then some executables
have failed to start and the user should check the last
.I ntask -
.I numt
locations in the
.I tids
array which will contain error codes
(see below for meaning).
The first
.I numt
tids in the array are always valid.
.PP
When
the argument
.I where
is omitted a heuristic (round-robin assignment) is used to distribute the
.I ntask
processes across the virtual machine.
.PP
In the special case where a multiprocessor is specified by
.I where,
pvm_spawn will start all
.I ntask
copies on this
single machine using the vendor's underlying routines.
.SH EXAMPLE
.nf
// create an exec file (script)
write(TMPDIR+'/foo.sce',['a=1';'plot2d()'])
// start a new Scilab on the same host to execute the script
[tids, numt] = pvm_spawn(TMPDIR+'/foo.sce',1)
pvm_kill(tids) //terminate the new scilab
.fi
.SH SEE ALSO
pvm, pvm_spawn_independent
|
