HP-MPI Version 2.2.5 for HP-UX Release Note

HP-MPI V2.2.5 for HP-UX Release Note
Known Problems and Workarounds
15
Known Problems and Workarounds
Problem with CPU binding and appfiles that launch scripts on HP-UX
HP-UX shells do not get bound because they are chatr'd to ignore LD_LIBRARY_PATH. This
causes problems with binding when a shell is involved in the MPI program that is started
first.
In order to get proper CPU binding on HP-UX, insert a wrapper (mpipreexec) before the
program in the appfile or command line. For example, instead of
-np 128 /path/to/some/script arg1 arg2 arg3
use
-np 128 /path/to/mpipreexec /path/to/some/script arg1 arg2 arg3
mpipreexec executes the program along with the arguments it is passed and propagates
the environment. It is not chatr'd to ignore LD_LIBRARY_PATH.
The source for mpipreexec.c:
#include <errno.h>
#include <unistd.h>
#include <stdio.h>
int main(int argc,char *argv[])
{
if(argc <2)
return 1;
execvp(argv[1],&(argv[1]));
fprintf(stderr,"Error, unable to exec cmdline (%s),error=%d.\n",argv[1],errno);
return 0;
}
InfiniBand driver B.11.23.06 has a known issue that can lead to data corruption if
HP-MPI is used with the -srq option. The bug does not occur if -srq is not used, and older
versions of the InfiniBand driver do not have this problem. Newer versions of the
InfiniBand driver will also contain the fix.
If your system contains multiple versions of system utilites such as 'ar', be sure that
/usr/bin comes earlier in your PATH so the HP-UX version of the utility will be used. If
'which ar' gives some other version of 'ar' such as the 'ar' from a GNU tools package, then
the Makefile which is used to build your own copy of libmpiCC.a may produce an invalid
link command.