HP-MPI User's Guide (11th Edition)

Understanding HP-MPI
Running applications on Windows
Chapter 3108
Hello world! I'm 2 of 4 on n02
Hello world! I'm 1 of 4 on n01
Hello world! I'm 0 of 4 on n01
Hello world! I'm 3 of 4 on n02
Running on CCS with an appfile - advanced usage
Another method for running with an appfile using CCS is to write a
submission script that uses mpi_nodes.exe to dynamically generate an
appfile based on the CCS allocation. The -ccp flag will generate an
appfile that uses the allocated CCP job resources as the machines and
rank counts in the appfile, and then launch the mpirun job using this
appfile.
If the user wishes to provide their own appfile, the tools described below
have been provided.
The executable mpi_nodes.exe (located in "%MPI_ROOT%\bin") has been
provided which will return the job resources, in the same format as the
CCP_NODES environment variable. Alternately, the user could write an
appfile, then select the exact resources needed from the Submit jobs
window, then the Advanced tab as needed. But this defeats the purpose
of the job scheduler because the CCP_NODES environment variable only
lists the resources allocated to the task, not the job.
<Node-Count> [<Node> <Processors-on-node>] ...
The script submission_script.vbs (found in "%MPI_ROOT%\help") is an
example of using mpi_nodes.exe to generate an appfile, and submit the
mpirun command.
There are many other ways to accomplish the same thing. Other
scripting languages can be used to convert the output of mpi_nodes.exe
into the appropriate appfile.
Or a script using all the job resources and the CCP_NODES environment
variable can construct the appropriate appfile, then submit a single
processor mpirun task to CCP_JOBID and exit. Here the mpirun task will
be queued up with no available processors until the script (using all job
processors) finishes, then start executing.
Again, there are many different ways to generate your own appfile for
use by mpirun. In all cases, the mpirun command will use the -ccp flag,
and the -f <appfile> flag using the generated file as the appfile name.