HeNCE 1.4 now includes support for pvm 3.x. No new functionality is available -- HeNCE doesn't make use of any of the new features of pvm3. For example: although HeNCE should be able to run node programs on various nodes of a MPP if pvm 3.x supports doing that, it will still only fire up one node program at a time. Likewise, HeNCE doesn't use the fault-tolerance facilities of pvm3. Yet. There are no new features in HeNCE 1.4 other than support for PVM 3.x. CAVEAT Both PVM 3.x and the HeNCE 1.4 code that is built on PVM 3.x are still somewhat fragile. INSTALLATION By default, HeNCE 1.4 is built to use pvm version 2.4.x. Here's how to compile and install it with pvm 3.x: 1) If you've already built HeNCE with pvm 2.4.x, do a "make clean" from the top-level HeNCE source directory. 2) edit "imake.defs" and uncomment out the line that defines PVM3. 3) do "make; make install" to build and install things. OPERATION 1) When built with PVM support, the HeNCE 1.4 executioner will automatically attempt to "add" any host named in the cost matrix to the PVM. If any attempt to add a host fails, the executioner will abort with an error. However, there is currently no support for a pvm "hosts" file if you start pvm from within htool. If you need a hosts file to specify pvm options, you must start pvmd3 "by hand" before running any HeNCE program. You can still start up the pvm console by pressing the "Start PVM" button in htool, since the console and pvmd are separate processes in pvm3. 2) Be very careful that you don't try to run HeNCE node programs that were linked with pvm2.x, under htool linked with pvm3.x. X RESOURCES To avoid conflicts, some resource names are changed: 1) HeNCE node programs are installed and run from the directory defined by the htool.binDir resource. For the pvm3 version, the default value of this resource is "$(HOME)/pvm3/bin/$(ARCH)". 2) The location of the pvm console is defined by the htool.pvmd3 resource. Normally this should be "$(HOME)/pvm3/lib/$(ARCH)/pvm". By default, this will be set to that directory, using the architecture that htool was compiled with. (You don't have to set an environment variable.) 3) The pvm 3 host file has a slightly different syntax than the pvm 2.x host file. So you specify the location of a pvm 3 host file with the htool.pvm3HostFile resource. By default, it is /dev/null. 4) Htool has to know where the libpvm3.a file is. The resource that sets this is htool.pvm3Lib. By default the resource is set to $(HOME)/pvm3/lib/$(ARCH)/libpvm3.a If you install pvm3 as suggested, you shouldn't need to change htool's defaults. Just make sure that $(HOME)/pvm3 is equivalent to the top-level pvm3 directory. If necessary, install a symlink from $(HOME)/pvm3 to wherever.