/*
1. Copy all the files from the VMS pvm directory to a directory
on a VMS machine and setup the C programming environment.
a) properly installed C compiler and license
put dxm_link.opt in the home directory sys$login
setup c library logicals with @clinklib
b) UCX product properly installed (vms tcp/ip)
{ multinet may provide similar functionality for vms }
c) properly installed MMS tool and license (vms make)
command procedures can be used to compile the modules too

2) Create the executables
mms/description=descrip.mms/ignore=warning

3) Create a test application
copy example files from original distribution
change the mms file make.com for the test programs
build the executables
mms/description=make.com/ignore=warning

4) Setup and run the pvm daemons
a) set symbols to run the program
@pvmsetup.com
b) must be in home directory to run the daemon
set def sys$login
c) pvmd3 hostfile.
where hostfile specifies the list of daemons to run on remote nodes
recommend intially using the manual startup option i.e.
nodename ms

5) setup and manaully start pvm slave daemons
signon to remote node
copy over the executables to the remote site
(may have problems for cluster machines due to file name conflicts)
@pvmsetup
run the slave daemon
pvmd3 -s

6) manually cut and paste the data between master and slave daemons

7) now the applicatons can be run on either node

Note: there is still more work to be done cleaning up the port to VMS
but this is a good start for people interested on helping port the
PVM code to VMS.
*/
/*
* please be sure to obtain the full pvm release from ornl
* this is an addon only
* Dan L. Clark dclark@cse.ogi.edu
*/
