HP-MPI Version 1.1 for Windows Release Note
HP-MPI V1.1 for Windows Release Note
What’s in This Version
11
flag is rarely necessary as the client (mpirun) and the server (HP-MPI
Remote Launch service) will negotiate the security package to be used for
authentication.
-token <token-name>
-tg <token-name>
Authenticates to this token with the HP-MPI Remote Launch service. Some
authentication packages require a token name. The default is no token.
-pass Prompts the user for his domain account password. Used to authenticate
and create remote processes. A password is required to allow the remote
process to access network resources (such as file shares). The password
provided is encrypted using SSPI for authentication. The password is not
cached when using this option.
-cache Prompts the user for his domain account password. Used to authenticate
and create remote processes. A password is required to allow the remote
process to access network resources (such as file shares). The password
provided is encrypted using SSPI for authentication. The password will be
cached so that future mpirun commands will use the cached password.
Passwords are cached in encrypted form, using Windows Encryption APIs.
-nopass Executes the mpirun command with no password. If a password is cached, it
is not accessed and no password is used to create the remote processes.
Using no password will result in the remote processes not having access to
network resources. This option will also suppress the 'no password cached'
warning. This is useful when no password is desired for SMP jobs.
-iscached Indicates if a password is stored in the user password cache and stops
execution. The MPI application will not launch if this option is included on
the command line.
-clearcache Clears the password cache and stops. The MPI application will not launch if
this option is included on the command line.
Appfile, hostlist, and hostfile support for Windows 2003/XP and Windows CCS
This release contains a variety of new launch options for the mpirun.exe command. The
-hostfile and -hostlist options allow the user to launch the same executable across a
collection of hosts. The use of the -f option and an appfile allow applications to launch that
consist of multiple programs or that run on multiple hosts. Detailed examples of these options
are given in the “Building and running applications” section on page 34 of this release note.