Start the ORNL PVM daemon process before you start TotalView. See the ORNL PVM documentation for information about the PVM daemon process and console program. The procedure for starting an ORNL PVM application is as follows:
1 Use the pvm command to start a PVM console session—this command starts the PVM daemon.If PVM isn’t running when you start TotalView (with PVM support enabled), TotalView exits with the following message:
2 If your application uses groups, start the pvmgs process before starting TotalView.PVM groups are unrelated to TotalView process groups. For information about TotalView process groups, see “Examining Groups”.
3 You can use the –pvm command-line option to the totalview command. As an alternative, you can set the TV::pvm variable in a startup file.The command-line options override the CLI variable. For more information, see “TotalView Command Syntax” in the TotalView Reference Guide.This directory list must include those needed to find both executable and source files. The directories you use can vary, but should always contain the current directory and your home directory.You can set the directory search path using either the EXECUTABLE_PATH variable or the File > Search Path command. See “Setting Search Paths” for more information.For example, to debug the PVM examples, you can place the following directories in your search path:
5 Verify that the action taken by TotalView for the SIGTERM signal is appropriate. (You can examine the current action by using the Process Window File > Signals command. See “Handling Signals” for more information.)PVM uses the SIGTERM signal to terminate processes. Because TotalView stops a process when the process receives a SIGTERM, the process is not terminated. If you want the PVM process to terminate, set the action for the SIGTERM signal to Resend.
Rogue Wave Software, Inc. |
Voice: (303) 473-9118 |
rwonlinedocs@roguewave.com |