Starting MemoryScape on an MPICH Job

Before you can bring an MPICH job under MemoryScape’s control, both MemoryScape and the Debugger Server must be in your path. You can do this in a login or shell startup script.

The official syntax for starting Memoryscape is as follows:

mpirun –tv [ other_mpich-args ] program [ program-args ]

For example:

mpirun –tv –np 4 sendrecv

The –tv option tells mpirun that it should obtain information from the TOTALVIEW environment variable.

For example, the following is the C shell command that sets the TOTALVIEW environment variable so that mpirun passes the –verbosity option to MemoryScape:

setenv TOTALVIEW "memscape –verbosity 1"

In this example, the memscape command must be in your path. If it isn’t, you’ll need to specify either an absolute or relative path to the memscape command. MemoryScape begins by starting the first process of your job, the master process, under its control.

On the IBM SP computer with the ch_mpl device, the mpirun command uses the poe command to start an MPI job. While you still must use the MPICH mpirun (and its –tv option) command to start an MPICH job, the way you start MPICH differs. For details on using MemoryScape with poe, see “Starting MemoryScape on a PE Program”.

Starting MemoryScape using the ch_p4mpd device is similar to starting MemoryScape using poe on an IBM computer or other methods you might use on Sun and HP platforms. In general, you start MemoryScape using the memscape command, with the following syntax;

memscape mpirun [ memscape_args ] –a [ mpich-args ] \
program [ program-args ]

As your program executes, MemoryScape automatically acquires the processes that are part of your parallel job as your program creates them. MemoryScape automatically copies memory configuration information to the slave processes.