Environment Variables and Path

There are several environment variables that must be set before PADE will run. Also, there are some directories to be added to the executables path. This is most easily accomplished by adding a few lines to the non-login shell startup file ( .cshrc, .profile, .bashrc , etc.). The environment variables on the development host are:

• PADE_ROOT -- the directory in which PADE is installed
• PVM_ROOT -- the directory in which PVM is installed
• PVM_ARCH -- the PVM name of your architecture
• XPVM_ROOT -- the directory in which XPVM is installed (optional)
• TCL_LIBRARY -- the directory in which the TCL library resides
• TK_LIBRARY -- the directory in which the TK library resides
• EDITOR -- your favorite editor (optional; PADE will prompt if not set)

The additional directories to be added to the executables path on the development host are:

$HOME/pvm3/bin/$PVM_ARCH
$XPVM_ROOT/src/$PVM_ARCH (optional)
$PADE_ROOT/caml_utils/$PVM_ARCH
$PADE_ROOT/pade
$PVM_ROOT/lib/$PVM_ARCH
$PVM_ROOT/lib

The caml_utils directory is not necessarily installed under $PADE_ROOT . Consult your system administrator for the actual location.

On the remote hosts, the user is only required to have the environment variables PVM_ROOT and PVM_ARCH. None of the path additions are required on the remote hosts.

For further information on these environment variables and directories, see the script pade_setenv (if your shell is csh or tcsh), or pade_export (if your shell is sh, ksh or bash) in the directory $PADE_ROOT/examples . An alternative to entering this information in the shell startup file is to execute one of these scripts before starting PADE.