Prism 6.0 Reference Manual

`prism`

Enter the Prism programming environment.

SYNTAX

To run Prism in the LSF environment:

prism [program-name] [-C
| -CX] [-n | -np nprocs] [-W] 
[Xoption ...] [core-file | pid | jid] [< infile] [> outfile] 
[-bsubargs "option [option...
]"] [-q queue]

To run Prism in the CRE environment:

prism [program-name] [-C
| -CX] [-n | -np nprocs] [-W] 
[Xoption ...] [core-file | pid | jid] [< infile] [> outfile]
[-mprunargs "option [option...]"] [-c cluster] [-p partition]

DESCRIPTION

prism enters Prism, an X-based graphical programming environment within which you can develop, execute, debug, and visualize data in serial and parallel programs.

You must execute the prism command from a terminal or workstation running the X Window System (unless you specify the -C option).

If issued without the -n (or -np) option prism starts scalar Prism, the version of Prism designed for use on serial programs.

If issued with the -n (or -np) option, prism starts MP Prism, the version of Prism designed for use on message-passing or other multiprocess programs. The -c and -p options for Prism in the CRE environment also start MP Prism. Message-passing programs must be written in the SPMD style (that is, each process must run the same executable program).

If you specify -n (or -np), you can also include other options to specify where the processes are to run. These control where the processes are run unless overridden by a Prism option. If you don't specify -n (or -np), -bsubargs, or -mprunargs, one copy of the program runs on your login node.

If issued without the name of an executable program, prism displays the main window of the Prism environment, with no program loaded. If you issue it with the name of an executable program, prism loads that program into Prism upon startup.

If you specify core-file, prism associates that core file with the program you load. Within Prism, you can then examine the stack and display the values of variables at the point at which core was dumped.

If you specify pid, prism loads the running process with that process ID into Prism. The process is interrupted, and you can then work with the program in Prism as you normally would. When attaching to a running serial process in this manner, Prism must be started on the same node on which the process is running. In MP Prism, you can specify jid, the job ID for a multiprocess program running in a Sun HPC system. To load a multiprocess program by its job ID, you must also use one of the arguments that specifies the message-passing version of Prism, MP Prism, such as the -n or -np arguments (in the CRE environment, you can also use the -c and -p arguments to specify the message-passing version of Prism).

If you specify infile, prism reads and executes commands from the specified file upon startup. Specifying infile redirects standard input (stdin), blocking subsequent user input to Prism. If you specify outfile, prism logs all its input and output to this file. This includes commands from infile and commands typed on the command line within Prism.

If there is a .prisminit file in your current working directory, prism executes the commands in it upon startup. If .prisminit isn't in your current working directory, prism looks for it in your home directory. If it isn't in either place, prism starts up without executing a .prisminit file.

Environment-Specific Prism Descriptions

You can run Prism in either of the LSF or CRE environments. To determine which environment is in effect, execute the script hpc_rte from a shell prompt.

To Run Prism in the LSF Environment:

If you are running Prism in the LSF environment, you can specify bsub options that you want to apply to your message-passing program on the Prism command line as a quoted string following the -bsubargs option. Once you have entered Prism you can issue the bsubargs command on the Prism command line to specify bsub options. Prism stores these options, then applies them when you start up a multiprocess program. Specifying the setting of an option via the bsubargs command supersedes the setting of the entire list of options you have established via the prism command line. You must reset every one of your bsub options every time you issue the bsubargs command.

The string given to bsubargs should not contain the -I, -Ip, or -n flags, because Prism internally generates values for them, and the results will be undefined. The same considerations apply using the -bsubargs switch to Prism.

To remove any existing bsub options you have specified, issue the command bsubargs off This removes options you have set via the prism command line and the bsubargs command. Issuing the bsubargs command with no options shows the current bsub options.

The bsubargs command and the -bsubargs option differ in one respect. Since the -bsubargs option is issued at a shell prompt, you must refer to the documentation for your shell program for the specific syntax for handling any quoted string supplied as an argument to the -bsubargs option. The bsubargs command does not interact with a shell, thus the bsubargs command requires no additional string quoting syntax.

To Run Prism in the CRE Environment:

If you are running Prism in the CRE environment, you can specify mprun options that you want to apply to your message-passing program on the Prism command line as a quoted string following the -mprunargs option. Once you have entered Prism you can issue the mprunargs command on the Prism command line to specify mprun options. Prism stores these options, then applies them when you start up a multiprocess program. Specifying the setting of an option via the mprunargs command overrides the setting of the same option you have established via the prism command line. If it is an option that has otherwise not been specified, it is added to the existing settings.

The string given to mprunargs should not contain the -I, -Ip, or -n flags, because Prism internally generates values for them, and the results will be undefined. The same considerations apply using the -mprunargs switch to Prism.

To remove any existing mprun options you have specified, issue the command mprunargs off This removes options you have set via the prism command line and the mprunargs command. Issuing the mprunargs command with no options shows the current mprun options.

The mprunargs command and the -mprunargs option differ in one respect. Since the -mprunargs option is issued at a shell prompt, you must refer to the documentation for your shell program for the specific syntax for handling any quoted string supplied as an argument to the -mprunargs option. The mprunargs command does not interact with a shell, thus the mprunargs command requires no additional string quoting syntax.

Use the -c and -p options to specify a CRE cluster and partition. These options override the CRE environment variables SUNHPC_CLUSTER and SUNHPC_PART. You can use these options only when launching Prism in the CRE environment.

OPTIONS

-C - Commands-only execution. Prism displays a prompt from which you can issue any Prism commands. If you use this option, you don't need an X terminal or workstation.

-CX - Commands-only execution with output. Start a version of Prism that uses commands-only execution (like -C), but in which the output of certain Prism commands can be sent to X windows.

-n [ or -np] nprocs - Start nprocs processes of the executable program. Without this argument, prism starts a single process. Specify 0 (zero) to indicate that you want to start one process on each available node.

-W - Start as many processes as the -n argument specifies, even when the number of processes exceeds the number of processors. The default is to launch one process per processor.

Xoption - Apply X toolkit option. The prism command accepts all standard X toolkit options. However, the -font, -title, and -rv options have no effect, and the -bg option is overridden in part by the setting of the Prism.textBgColor resource. X toolkit options are meaningless, of course, if you use -C to run Prism in commands-only mode.

Options for Prism in the LSF Environment:

-bsubargs "option [option]..." - Start the executable program using the specified bsub options. Using the -bsubargs option implies -n and starts MP Prism. If the bsub option itself uses quotation marks, refer to the documentation for your shell program for the syntax for handling quotes.

-q queue - Start the executable program in the specified queue. Without this argument, Prism starts the program in the default queue. Using the -q option implies MP Prism.

Options for Prism in the CRE Environment:

-mprunargs "option [option]..." - Start the executable program, using the specified mprun options. -mprunargs implies -n, and starts MP Prism. If the mprun option itself uses quotation marks, refer to the documentation for your shell program for the syntax for handling quotes.

-c cluster - Start the executable program on the specified cluster. Using this option implies -n, and starts MP Prism. The cluster overrides the value of the CRE SUNHPC_CLUSTER environment vari able.

-p partition - Start the executable program on the specified partition. Using this option implies -n, and starts MP Prism. The partition overrides the value of the CRE SUNHPC_PART environment variable.

FILES

.prisminit - Prism initialization file.

.prism_defaults - Prism defaults file.

IDENTIFICATION

Prism Version 6.0.

prism