Totalview® Reference Guide : Appendix A MPI Startup : Customizing Your Parallel Configuration : TotalView
TotalView
If you are using TotalView, set the TV::parallel_configs variable, either local to your TotalView installation or globally:
Globally, in your system's .tvdrc file. If you set this variable here, everyone using this TotalView version will see the definition.
Locally, in your .totalview/tvdrc file. You will be the only person to see this definition when you start TotalView.
You can also directly edit the parallel_support.tvd file, located in the totalview/lib installation directory area, but reinstalling TotalView overwrites this file so this is not recommended.
For TotalView, if you are using a locally-installed MPI implementation, you should add it to your PATH variable. By default, both TotalView and MemoryScape use the information in PATH to find the parallel launcher (for example, mpirun, mpiexec, poe, srun, prun, dmpirun, and so on). Generally, if you can run your parallel job from a command line, TotalView can also run it.
If you have multiple installed MPI systems — for example, multiple versions of MPICH installed on a common file server — only one can be in your path. In this case, specify an absolute path to launch it, which means you will need to customize the TV::parallel_configs list variable or the parallel_support.tvd file contained within your installation directory so that it does not rely on your PATH variable.
The easiest way to create your own startup configuration for TotalView is to copy a similar configuration from the TV::private::parallel_configs_base variable (found in the parallel_support.tvd file, located in your installation directory at totalview/lib) to the TV::parallel_configs variable, and then edit it. Save the TV::parallel_configs variable in the tvdrc file located in the .totalview subdirectory in your home directory. For standalone -MemoryScape, please see Standalone MemoryScape.
When you add configurations, they are simply added to a list. This means that if TotalView supplies a definition named foo and you create a definition also named foo, both exist and your product chooses the first one in the list. Because both are displayed, be careful to give each new definition a unique name.