Open MPI logo

prterun(1) man page (version 5.0.0rc2)

  |   Home   |   Support   |   FAQ   |  

« Return to documentation listing

Table of Contents


prterun - Execute serial and parallel jobs with the PMIx Reference Runtime (PRTE).


C]prterunR] does B]notR] require a running C]prteR] Distributed Virtual Machine (DVM). It will start the C]prteR] DVM, run a single job, and shutdown the DVM.

Single Process Multiple Data (SPMD) Model:

C]prterun [ options ] <program> [ <args> ]R]Multiple Instruction Multiple Data (MIMD) Model:

C]prterun [ global_options ] [rs] [ local_options1 ] <program1> [ <args1> ] : [rs] [ local_options2 ] <program2> [ <args2> ] : [rs] ... : [rs] [ local_optionsN ] <programN> [ <argsN> ]R]Note that in both models, invoking C]prterunR] via an absolute
path name is equivalent to specifying the C]--prefixR] option with a C]<dir>R] value equivalent to the directory where C]prterunR] resides, minus its last subdirectory. For example:

C]$ /usr/local/bin/prterun ...R]is equivalent to

C]$ prterun --prefix /usr/localR]Quick Summary

If you are simply looking for how to run an application,

you probably
want to use a command line of the following form:

C]$ prterun [ -np X ] [ --hostfile <filename> ] <program>R]This will run C]XR] copies of C]<program>R] in your current
run-time environment over the set of hosts specified by C]<filename>R], scheduling (by default) in a round-robin fashion by CPU slot. If running under a supported resource manager a hostfile is usually not required unless the caller wishes to further restrict the set of resources used for that job.


This section includes many commonly used options. There may be other options listed with C]prterun --helpR].

C]prterunR] will send the name of the directory where it was invoked on the local node to each of the remote nodes, and attempt to change to that directory. See the [lq]Current Working Directory[rq] section below for further details.

The program executable. This is identified as the first non-recognized argument to C]prterunR].
Pass these run-time arguments to every new process. These must always be the last arguments to C]prterunR] after the C]<program>R]. If an app context file is used, C]<args>R] will be ignored.
B]CB]-h, --helpB]R]
Display help for this command
B]CB]-V, --versionB]R]
Print version number. If no other arguments are given, this will also cause C]prterunR] to exit.

Since C]prterunR] combines both C]prteR] and C]prunR] it accepts all of the command line arguments from both of these tools. See prte(1) and prun(1) for details on the command line options. See prte-map(1) for more details on mapping, ranking, and binding options.


One invocation of C]prterunR] starts the PRTE DVM (i.e., C]prteR]), runs a single job (similar to C]prunR]), then terminates the DVM (similar to C]ptermR]). If the application is single process multiple data (SPMD), the application can be specified on the C]prterunR] command line.

If the application is multiple instruction multiple data (MIMD), comprising of multiple programs, the set of programs and argument can be specified in one of two ways: Extended Command Line Arguments, and Application Context.

An application context describes the MIMD program set including all arguments in a separate file. This file essentially contains multiple C]prterunR] command lines, less the command name itself. The ability to specify different options for different instantiations of a program is another reason to use an application context.

Extended command line arguments allow for the description of the application layout on the command line using colons (C]:R]) to separate the specification of programs and arguments. Some options are globally set across all specified programs (e.g. C]--hostfileR]), while others are specific to a single program (e.g. C]--npR]).

Return Value

See prun(1) for details.

Table of Contents

« Return to documentation listing