1prterun(1) PRRTE prterun(1)
2
6 prterun - Execute serial and parallel jobs with the PMIx Reference Run‐
7 time (PRTE).
8
10 prterun does not require a running prte Distributed Virtual Machine
11 (DVM). It will start the prte DVM, run a single job, and shutdown the
12 DVM.
13 Single Process Multiple Data (SPMD) Model:
15 prterun [ options ] <program> [ <args> ]
17 Multiple Instruction Multiple Data (MIMD) Model:
19 prterun [ global_options ] \
21 [ local_options1 ] <program1> [ <args1> ] : \
22 [ local_options2 ] <program2> [ <args2> ] : \
23 ... : \
24 [ local_optionsN ] <programN> [ <argsN> ]
25 Note that in both models, invoking prterun via an absolute path name is
27 equivalent to specifying the --prefix option with a <dir> value equiva‐
28 lent to the directory where prterun resides, minus its last subdirecto‐
29 ry. For example:
30 $ /usr/local/bin/prterun ...
32 is equivalent to
34 $ prterun --prefix /usr/local
36
38 If you are simply looking for how to run an application, you probably
39 want to use a command line of the following form:
40 $ prterun [ -np X ] [ --hostfile <filename> ] <program>
42 This will run X copies of <program> in your current run-time environ‐
44 ment over the set of hosts specified by <filename>, scheduling (by de‐
45 fault) in a round-robin fashion by CPU slot. If running under a sup‐
46 ported resource manager a hostfile is usually not required unless the
47 caller wishes to further restrict the set of resources used for that
48 job.
49
51 This section includes many commonly used options. There may be other
52 options listed with prterun --help.
53 prterun will send the name of the directory where it was invoked on the
55 local node to each of the remote nodes, and attempt to change to that
56 directory. See the “Current Working Directory” section below for fur‐
57 ther details.
58 <program>
60 The program executable. This is identified as the first non-
61 recognized argument to prterun.
62 <args> Pass these run-time arguments to every new process. These must
64 always be the last arguments to prterun after the <program>. If
65 an app context file is used, <args> will be ignored.
66 -h, --help
68 Display help for this command
69 -V, --version
71 Print version number. If no other arguments are given, this
72 will also cause prterun to exit.
73 Since prterun combines both prte and prun it accepts all of the command
75 line arguments from both of these tools. See prte(1) and prun(1) for
76 details on the command line options. See prte-map(1) for more details
77 on mapping, ranking, and binding options.
78
80 One invocation of prterun starts the PRTE DVM (i.e., prte), runs a sin‐
81 gle job (similar to prun), then terminates the DVM (similar to pterm).
82 If the application is single process multiple data (SPMD), the applica‐
83 tion can be specified on the prterun command line.
84 If the application is multiple instruction multiple data (MIMD), com‐
86 prising of multiple programs, the set of programs and argument can be
87 specified in one of two ways: Extended Command Line Arguments, and Ap‐
88 plication Context.
89 An application context describes the MIMD program set including all ar‐
91 guments in a separate file. This file essentially contains multiple
92 prterun command lines, less the command name itself. The ability to
93 specify different options for different instantiations of a program is
94 another reason to use an application context.
95 Extended command line arguments allow for the description of the appli‐
97 cation layout on the command line using colons (:) to separate the
98 specification of programs and arguments. Some options are globally set
99 across all specified programs (e.g. --hostfile), while others are spe‐
100 cific to a single program (e.g. --np).
101
103 See prun(1) for details.
1042021-08-23 prterun(1)