Using Psets in Commands

As mentioned at the beginning of "Using Psets in MP Prism", some commands can take a pset as a qualifier; they are listed at the end of this section. Put this qualifier after any arguments to the command, but before the optional on window syntax that specifies the window in which output is to be displayed. A command with a pset qualifier applies only to the processes in the set. If you omit the qualifier, the command applies to the processes in the current set.

Thus,

stop at 12 pset error

sets a breakpoint at line 12 for the processes in pset error.

where pset 0:10 on dedicated

displays the Where graph for processes 0 through 10. See " Where Graph" for a description of the Where graph.

trace at 12 if x > 10

creates a trace event for the members of the current pset.

Note that this last command applies only to the members of the current pset. To apply it to all processes, use the syntax

trace at 12 if x > 10 pset all

Many commands, of course, cannot logically take a pset qualifier. You get an error message if you try to issue one of these commands with a pset qualifier.

Here are the Prism commands that can take a pset qualifier:

address/
assign
call
catch
cont, contw
display
ignore
interrupt
next, nexti
print
pstatus
return
step, stepi
stop, stopi
trace, tracei
wait
whatis
where