Note:   This  command  applies  to   a   multiprocess   debugging
     configuration (when DBG$PROCESS has the value MULTIPROCESS).

     The DO command executes commands in the context of  one  or  more
     processes.   By  default, commands are executed in the context of
     the visible process.  The  DO  command  enables  you  to  execute
     commands  in  the context of specific processes or all processes.
     The DO command is equivalent to entering  a  SET  PROCESS/VISIBLE
     command  for  each  process specified with the /PROCESS qualifier
     (or for all processes, if /PROCESS is  not  specified)  and  then
     entering  the specified commands.  To change the visible process,
     use the SET PROCESS command.

 Format:

       DO [/qualifier]  (command[; . . . ])

Additional information available:

ExamplesParametersQualifiers

     1   DBG_2> DO (SHOW CALLS)
         For %PROCESS_NUMBER 1
             module name     routine name    line       rel PC    abs PC
            *MAIN_MODULE     MAIN              31      0000001E  0000041E
         For %PROCESS_NUMBER 2
             module name     routine name    line       rel PC    abs PC
            *SUB_MODULE      SUB                4      0000000B  0000040B

     This command executes a SHOW CALLS command in the
     context of all processes.


     2   DBG_3> DO/PROCESS=(%PROC 2,%PROC 1) (EVAL/ADDR X;EXAM X)
         For %PROCESS_NUMBER 2
           %DEBUG-E-NOSYMBOL, symbol 'X' is not in the symbol table
         For %Process_number 1
           512
           TEST\X: 1

     This command executes the two commands EVAL/ADDR X and
     EXAM X in the context of processes 2 and 1.

 command

     Specifies a debugger command  that  is  to  be  executed  in  the
     context of the processes specified.

Additional information available:

/PROCESS

     Specifies one or more processes in whose context the commands are
     to  be  executed.   You must include the parentheses even if only
     one process is specified.  If you do not  specify  /PROCESS,  the
     commands  are  executed  in  the  context  of all processes (this
     effect is also achieved if  you  specify  the  asterisk  wildcard
     character (*) for process-spec).  Use any of the following forms:

     [%PROCESS_NAME] process-name    The VMS process name, if that
                                     name contains no spaces or
                                     lowercase characters[1].

     [%PROCESS_NAME] "process-name"  The VMS process name, if that
                                     name contains spaces or lowercase
                                     characters. You can also use
                                     apostrophes (') instead of
                                     quotation marks (").

     %PROCESS_PID process_id         The VMS process identification
                                     number (PID, a hexadecimal number).

     %PROCESS_NUMBER process-number  The number assigned to a process
     (or %PROC process-number)       when it comes under debugger control.
                                     Process numbers appear in a
                                     SHOW PROCESS display.

     process-group-name              A symbol defined with the
                                     DEFINE/PROCESS_GROUP command to
                                     represent a group of processes.

     %NEXT_PROCESS                   The next process in the debugger's
                                     circular process list after the
                                     visible process.

     %PREVIOUS_PROCESS               The previous process in the
                                     debugger's circular process list
                                     before the visible process.

     %VISIBLE_PROCESS                The process whose stack, register
                                     set, and images are the current
                                     context for looking up symbols,
                                     register values, routine calls,
                                     breakpoints, and so on.
     _______________________________________________________
     [1]The process name can include the asterisk wildcard
     character (*)