General problems:
PVM-specific problems:If all of the missing symbols are interface routines, then you probably have an interface problem. If they are all internal routines, then you probably have a internal problem. If the missing symbols include internal and interface routines, you are probably pointing at an invalid library.
Invalid libraries are usually fairly straight-forward.
You may be pointing at a BLACS library that does not exist. If you are
maintaining BLACS for several different systems, you may be pointing at
the wrong system's libraries. For instance, you may want the HP version
of the PVM BLACS, but you are pointing at the SUN4 version.
There are a couple of things which commonly cause interface
problems. The most likely is that the a particular interface was not installed.
The BLACS may be installed for Fortran and/or C: the installer may choose
to install only one.
If the missing symbols all begin with C, then you need to build
the C interface library. This can be done from the top-level makefile by
typing make
Another possibility is that the BLACS library was compiled with an
incorrect Bmake.inc file. The BLACS are written in C, but made
to be callable from Fortran77. The method for calling a C routine from Fortran
is system specific. Therefore, Bmake.inc allows the user to
vary the BLACS naming scheme, so that the routines may be called from Fortran.
Bmake.inc contains a macro called INTFACE, which
performs this function. Some systems (e.g. SUN4, CM-5, and Intel) require
an underscore to be postfixed to a C routine name for it to be callable from
Fortran.
This type of interface should be indicated by defining
INTFACE = -DAdd_.
Others (e.g. HP, RS6000) let Fortran and C share the same name space,
so that no change is required to call a C routine from Fortran.
This type of interface should be indicated by defining
INTFACE = -DNoChange.
Finally, some systems (primarily CRAY) require the the C routine name be
in upper case for it to be callable from Fortran.
This type of interface should be indicated by defining
INTFACE = -DUpCase.
Having on the internal routines missing happens most often to PVM users
where a previous platform's internals have been compiled into this library
(i.e., the internals for HP are compiled into a SUN4 library) .
If this is the case, remove the library, do a make clean
and rebuild.
Spawned processes do not check in
This usually indicates that there is insufficient memory to spawn the
required number of processes. The pvm_spawn succeeds, but when the system
attempts to allocate the process's memory, it fails, and thus the process
never truly gets started. The usual fix for this is to add more hosts,
or to reduce the size of your executable.
Strange behavior while using blacs_setup.dat
Old blacs_setup.dat files often remain around after their use, and when you
run your next program, the old file is accessed, causing the wrong executable
to be spawned. The BLACS do not
require you to use blacs_setup.dat, and it is recommended that you do not.
If you require the extra power blacs_setup.dat gives (e.g., you need to spawn
with debug), then of course it should be used.
Got message like "pvm error #XXX"
The BLACS may encounter a PVM error that they are not designed to handle.
In that case, they simply abort after reporting the error. The number printed
is a PVM error number. The meaning of these error number can be found in
the PVM manual or quick reference guide.