HP-MPI Version 1.1 for Windows Release Note

HP-MPI V1.1 for Windows Release Note

Building and running applications

-h n01 -np 2 \\node01\share\path\to\hello_world.exe

-h n02 -np 2 \\node01\share\path\to\hello_world.exe

Step 2. For the first run of the hello_world executable, use -cache to cache your password:

> "%MPI_ROOT%\bin\mpirun" -cache -f appfile

Password for MPI runs:

When typing, the password is not echoed to the screen.

The HP-MPI Remote Launch service must be registered and started on the remote

nodes. mpirun will authenticated with the service and create processes using your

encrypted password to obtain network resources.

If you do not provide a password, the password is incorrect, or you use -nopass,

remote processes will be created but will not have access to network shares. (i.e. in

this example it will not be able to read the hello_world.exe file.)

Step 3. Analyze hello_world output.

HP-MPI prints the output from running the hello_world executable in

non-deterministic order. The following is an example of the output:

Hello world! I'm 1 of 4 on n01

Hello world! I'm 3 of 4 on n02

Hello world! I'm 0 of 4 on n01

Hello world! I'm 2 of 4 on n02

Running with an appfile using CCS

Using an appfile with CCS has been greatly simplified in this release of HP-MPI. The

previous method of writing a submission script that uses mpi_nodes.exe to dynamically

generate an appfile based on the CCS allocation is still supported. However, the preferred

method is to allow mpirun.exe to determine which nodes are required for the job (by reading

the user-supplied appfile), request those nodes from the CCS scheduler, then submit the job to

CCS when the requested nodes have been allocated. The user writes a brief appfile calling out

the exact nodes and rank counts needed for the job. For example:

Perform Steps 1 and 2 from “Building and running on a single host” on page 34.

Step 1. Create an appfile for running on nodes n01 and n02 as:

-h n01 -np 2 hello_world.exe

-h n02 -np 2 hello_world.exe

Step 2. Submit the job to CCS with the following command: