DBG$HELP.HLB  —  DEBUG  CANCEL

1  –  ALL

    Cancels all breakpoints, tracepoints, and watchpoints. Restores
    the scope and type to their default values. Restores the line,
    symbolic, and G_floating modes established with the SET MODE
    command to their default values.

    Format

      CANCEL ALL

1.1  –  Qualifiers

1.1.1    /PREDEFINED

    Cancels all predefined (but no user-defined) breakpoints and
    tracepoints.

1.1.2    /USER

    Cancels all user-defined (but no predefined) breakpoints,
    tracepoints, and watchpoints. This is the default unless you
    specify /PREDEFINED.

1.2  –  Description

    The CANCEL ALL command does the following:

    1. Cancels all user-defined eventpoints (those created with
       the commands SET BREAK, SET TRACE, and SET WATCH). This is
       equivalent to entering the commands CANCEL BREAK/ALL, CANCEL
       TRACE/ALL, and CANCEL WATCH/ALL. Depending on the type of
       program (for example Ada, multiprocess), certain predefined
       breakpoints or tracepoints might be set automatically when
       you start the debugger. To cancel all predefined but no user-
       defined eventpoints, use CANCEL ALL/PREDEFINED. To cancel
       all predefined and user-defined eventpoints, use CANCEL
       ALL/PREDEFINED/USER.

    2. Restores the scope search list to its default value
       (0,1,2, . . . ,n). This is equivalent to entering the CANCEL
       SCOPE command.

    3. Restores the data type for memory locations that are
       associated with a compiler-generated type to the associated
       type. Restores the type for locations that are not associated
       with a compiler-generated type to "longword integer". This is
       equivalent to entering the CANCEL TYPE/OVERRIDE and SET TYPE
       LONGWORD commands.

    4. Restores the line, symbolic, and G_floating modes established
       with the SET MODE command to their default values. This is
       equivalent to entering the following command:

       DBG> SET MODE LINE,SYMBOLIC,NOG_FLOAT

    The CANCEL ALL command does not affect the current language
    setting or modules included in the run-time symbol table.

    Related commands:

       (CANCEL,DEACTIVATE) BREAK
       CANCEL SCOPE
       (CANCEL,DEACTIVATE) TRACE
       CANCEL TYPE/OVERRIDE
       (CANCEL,DEACTIVATE) WATCH
       (SET,CANCEL) MODE
       SET TYPE

1.3  –  Examples

    1.DBG> CANCEL ALL

      This command cancels all user-defined breakpoints and
      tracepoints and all watchpoints, and restores scopes, types,
      and some modes to their default values. In this example, there
      are no predefined breakpoints or tracepoints.

    2.DBG> CANCEL ALL
      %DEBUG-I-PREDEPTNOT, predefined eventpoint(s) not canceled

      This command cancels all user-defined breakpoints and
      tracepoints and all watchpoints, and restores scopes, types,
      and some modes to their default values. In this example, there
      is a predefined breakpoint or tracepoint; this is not canceled
      by default.

    3.DBG> CANCEL ALL/PREDEFINED

      This command cancels all predefined breakpoints and
      tracepoints, and restores scopes, types, and some modes
      to their default values. No user-defined breakpoints or
      tracepoints are affected.

2  –  BREAK

    Cancels a breakpoint.

    Format

      CANCEL BREAK  [address-expression[, . . . ]]

2.1  –  Parameters

 address-expression

    Specifies a breakpoint to be canceled. Do not use the asterisk
    (*)  wildcard character. Instead, use the /ALL qualifier. Do not
    specify an address expression when using any qualifiers except
    /EVENT, /PREDEFINED, or /USER.

2.2  –  Qualifiers

2.2.1    /ACTIVATING

    Cancels the effect of a previous SET BREAK/ACTIVATING command.

2.2.2    /ALL

    By default, cancels all user-defined breakpoints. When used
    with /PREDEFINED, cancels all predefined breakpoints but no
    user-defined breakpoints. To cancel all breakpoints, use CANCEL
    BREAK/ALL/USER/PREDEFINED.

2.2.3    /BRANCH

    Cancels the effect of a previous SET BREAK/BRANCH command.

2.2.4    /CALL

    Cancels the effect of a previous SET BREAK/CALL command.

2.2.5    /EVENT

       /EVENT=event-name

    Cancels the effect of a previous SET BREAK/EVENT=event-name
    command. Specify the event name (and address expression, if
    any) exactly as specified with the SET BREAK/EVENT command. To
    identify the current event facility and the associated event
    names, use the SHOW EVENT_FACILITY command.

2.2.6    /EXCEPTION

    Cancels the effect of a previous SET BREAK/EXCEPTION command.

2.2.7    /HANDLER

    Cancels the effect of a previous SET BREAK/HANDLER command.

2.2.8    /INSTRUCTION

    Cancels the effect of a previous SET BREAK/INSTRUCTION command.

2.2.9    /LINE

    Cancels the effect of a previous SET BREAK/LINE command.

2.2.10    /PREDEFINED

    Cancels a specified predefined breakpoint without affecting
    any user-defined breakpoints. When used with /ALL, cancels all
    predefined breakpoints.

2.2.11    /SYSEMULATE

    (Alpha only) Cancels the effect of a previous SET
    BREAK/SYSEMULATE command.

2.2.12    /TERMINATING

    Cancels the effect of a previous SET BREAK/TERMINATING command.

2.2.13    /UNALIGNED_DATA

    (Alpha only) Cancels the effect of a previous SET
    BREAK/UNALIGNED_DATA command.

2.2.14    /USER

    Cancels a specified user-defined breakpoint without affecting any
    predefined breakpoints. This is the default unless you specify
    /PREDEFINED. To cancel all user-defined breakpoints, use the /ALL
    qualifier.

2.3  –  Description

    Breakpoints can be user defined or predefined. User-defined
    breakpoints are set explicitly with the SET BREAK command.
    Predefined breakpoints, which depend on the type of program
    you are debugging (for example, Ada or ZQUIT multiprocess), are
    established automatically when you start the debugger. Use the
    SHOW BREAK command to identify all breakpoints that are currently
    set. Any predefined breakpoints are identified as such.

    User-defined and predefined breakpoints are set and canceled
    independently. For example, a location or event can have both
    a user-defined and a predefined breakpoint. Canceling the user-
    defined breakpoint does not affect the predefined breakpoint, and
    conversely.

    To cancel only user-defined breakpoints, do not specify
    /PREDEFINED with the CANCEL BREAK command (the default is /USER).
    To cancel only predefined breakpoints, specify /PREDEFINED
    but not /USER. To cancel both predefined and user-defined
    breakpoints, specify both /PREDEFINED and /USER.

    In general, the effect of the CANCEL BREAK command is symmetrical
    with that of the SET BREAK command (even though the SET BREAK
    command is used only with user-defined breakpoints). Thus, to
    cancel a breakpoint that was established at a specific location,
    specify that same location (address expression) with the CANCEL
    BREAK command. To cancel breakpoints that were established
    on a class of instructions or events, specify the class of
    instructions or events with the corresponding qualifier (/LINE,
    /BRANCH, /ACTIVATING, /EVENT=, and so on). For more information,
    see the qualifier descriptions.

    If you want the debugger to ignore a breakpoint without your
    having to cancel it (for example, if you want to rerun the
    program with and without breakpoints), use the DEACTIVATE BREAK
    instead of the CANCEL BREAK command. Later, you can activate the
    breakpoint (with ACTIVATE BREAK).

    Related commands:

       (ACTIVATE,DEACTIVATE) BREAK
       CANCEL ALL
       (SET,SHOW) BREAK
       (SET,SHOW) EVENT_FACILITY
       (SET,SHOW,CANCEL) TRACE

2.4  –  Examples

    1.DBG> CANCEL BREAK MAIN\LOOP+10

      This command cancels the user-defined breakpoint set at the
      address expression MAIN\LOOP+10.

    2.DBG> CANCEL BREAK/ALL

      This command cancels all user-defined breakpoints.

    3.DBG> CANCEL BREAK/ALL/USER/PREDEFINED

      This command cancels all user-defined and predefined
      breakpoints.

    4.all> CANCEL BREAK/ACTIVATING

      This command cancels a previous user-defined SET
      BREAK/ACTIVATING command. As a result, the debugger does not
      suspend execution when a new process is brought under debugger
      control.

    5.DBG> CANCEL BREAK/EVENT=EXCEPTION_TERMINATED/PREDEFINED

      This command cancels the predefined breakpoint set on task
      terminations due to unhandled exceptions. This breakpoint
      is predefined for Ada programs and programs that call POSIX
      threads or Ada routines.

3  –  DISPLAY

    Permanently deletes a screen display.

                                   NOTE

       This command is not available in the VSI DECwindows Motif for
       OpenVMS user interface to the debugger.

    Format

      CANCEL DISPLAY  [display-name[, . . . ]]

3.1  –  Parameters

 display-name

    Specifies the name of a display to be canceled. Do not specify
    the PROMPT display, which cannot be canceled. Do not use
    the asterisk (*)  wildcard character. Instead, use the /ALL
    qualifier. Do not specify a display name with /ALL.

3.2  –  Qualifiers

3.2.1    /ALL

    Cancels all displays, except the PROMPT display.

3.3  –  Description

    When a display is canceled, its contents are permanently lost,
    it is deleted from the display list, and all the memory that was
    allocated to it is released.

    You cannot cancel the PROMPT display.

    Related commands:

       (SHOW) DISPLAY
       (SET,SHOW,CANCEL) WINDOW

3.4  –  Examples

    1.DBG> CANCEL DISPLAY SRC2

      This command deletes display SRC2.

    2.DBG> CANCEL DISPLAY/ALL

      This command deletes all displays, except the PROMPT display.

4  –  MODE

    Restores the line, symbolic, and G_floating modes established by
    the SET MODE command to their default values. Also restores the
    default input/output radix.

                                   NOTE

       This command is not available in the VSI DECwindows Motif for
       OpenVMS user interface to the debugger.

    Format

      CANCEL MODE

4.1  –  Description

    The effect of the CANCEL MODE command is equivalent to the
    following commands:

    DBG> SET MODE LINE,SYMBOLIC,NOG_FLOAT
    DBG> CANCEL RADIX

    The default radix for both data entry and display is decimal for
    most languages.

    On Alpha processors, the exceptions are BLISS, MACRO-32, and
    MACRO-64, which have a default radix of hexadecimal.

    On Intel[R] Itanium[R] processors, the exceptions are BLISS,
    MACRO, and Intel[R] Assembler (IAS).

    Related commands:

       (SET,SHOW) MODE
       (SET,SHOW,CANCEL) RADIX

4.2  –  Example

  DBG> CANCEL MODE

      This command restores the default radix mode and all default
      mode values.

5  –  RADIX

    Restores the default radix for the entry and display of integer
    data.

    Format

      CANCEL RADIX

5.1  –  Qualifiers

5.1.1    /OVERRIDE

    Cancels the override radix established by a previous SET
    RADIX/OVERRIDE command. This sets the current override radix
    to "none" and restores the output radix mode to the value
    established with a previous SET RADIX or SET RADIX/OUTPUT
    command. If you did not change the radix mode with a SET RADIX
    or SET RADIX/OUTPUT command, the CANCEL RADIX/OVERRIDE command
    restores the radix mode to its default value.

5.2  –  Description

    The CANCEL RADIX command cancels the effect of any previous SET
    RADIX and SET RADIX/OVERRIDE commands. It restores the input and
    output radix to their default value.

    The default radix for both data entry and display is decimal for
    most languages. The exceptions are BLISS and MACRO, which have a
    default radix of hexadecimal.

    The effect of the CANCEL RADIX/OVERRIDE command is more limited
    and is explained in the description of the /OVERRIDE qualifier.

    Related commands:

       EVALUATE
       (SET,SHOW) RADIX

5.3  –  Examples

    1.DBG> CANCEL RADIX

      This command restores the default input and output radix.

    2.DBG> CANCEL RADIX/OVERRIDE

      This command cancels any override radix you might have set with
      the SET RADIX/OVERRIDE command.

6  –  SCOPE

    Restores the default scope search list for symbol lookup.

    Format

      CANCEL SCOPE

6.1  –  Description

    The CANCEL SCOPE command cancels the current scope search list
    established by a previous SET SCOPE command and restores the
    default scope search list, namely 0,1,2, . . . ,n, where n is the
    number of calls in the call stack.

    The default scope search list specifies that, for a symbol
    without a path-name prefix, a symbol lookup such as EXAMINE X
    first looks for X in the routine that is currently executing
    (scope 0); if no X is visible there, the debugger looks in the
    caller of that routine (scope 1), and so on down the call stack;
    if X is not found in scope n, the debugger searches the rest of
    the run-time symbol table (RST), then searches the global symbol
    table (GST), if necessary.

    Related commands:

       (SET,SHOW) SCOPE

6.2  –  Example

  DBG> CANCEL SCOPE

      This command cancels the current scope.

7  –  SOURCE

    Cancels a source directory search list, a source directory search
    method, or both a list and method established by a previous SET
    SOURCE command.

    Format

      CANCEL SOURCE

7.1  –  Qualifiers

7.1.1    /DISPLAY

    Cancels the effect of a previous SET SOURCE/DISPLAY command,
    which specifies the directory search list to be used by the
    debugger when displaying source code. Canceling this command
    means the debugger searches for a source file in the directory in
    which it was compiled.

7.1.2    /EDIT

    Cancels the effect of a previous SET SOURCE/EDIT command, which
    specifies the directory search list to be used during execution
    of the debugger's EDIT command. Canceling this command means the
    debugger searches for a source file in the directory in which it
    was compiled.

7.1.3    /EXACT

    Cancels the effect of a previous SET SOURCE/EXACT command, which
    specifies a directory search method. Canceling this command means
    that the debugger no longer searches for the exact version of the
    source file from compilation; it reverts to the default behavior
    of searching for the latest version of the file.

7.1.4    /LATEST

    Cancels the effect of a previous SET SOURCE/LATEST command, which
    specifies a directory search method. In this case, the CANCEL
    SOURCE/LATEST command directs the debugger to return to searching
    for the exact version of the source file from compilation.
    Because /LATEST is the default setting, this qualifier only makes
    sense when used with other qualifiers, for example, /MODULE.

7.1.5    /MODULE

       /MODULE=module-name

    Cancels the effect of a previous SET SOURCE/MODULE=module-
    name command in which the same module name and qualifiers were
    specified. (The /MODULE qualifier allows you to specify a unique
    directory search list, directory search method, or both, for
    the named module.) You can append one or more of the qualifiers
    listed above to the SET SOURCE/MODULE and CANCEL SOURCE/MODULE
    commands.

    If you issue a CANCEL SOURCE/MODULE command with additional
    qualifiers, you cancel the effect of the specified qualifiers
    on the module. If you issue an unqualified CANCEL SOURCE/MODULE
    command, the debugger no longer differentiates the module from
    any other module in your directories.

7.1.6    /ORIGINAL

    (Applies to STDL programs only. Requires the installation of the
    Correlation Facility (a separate layered product) and invocation
    of the kept debugger.) Cancels the effect of a previous SET
    SOURCE/ORIGINAL command. The SET SOURCE/ORIGINAL command is
    required to debug STDL source files, and must be canceled when
    you debug source files written in other languages.

7.2  –  Description

    CANCEL SOURCE cancels the effect of a previous SET SOURCE
    command. The nature of this cancellation depends on the
    qualifiers activated in previous SET SOURCE commands. See the
    CANCEL SOURCE examples to see how CANCEL SOURCE and SET SOURCE
    interact.

    When you issue a SET SOURCE command, be aware that one of the
    two qualifiers -/LATEST or /EXACT-will always be active. These
    qualifiers affect the debugger search method. The /LATEST
    qualifier directs the debugger to search for the version last
    created (the highest-numbered version in your directory). The
    /EXACT qualifier directs the debugger to search for the version
    last compiled (the version recorded in the debugger symbol table
    created at compile time). For example, a SET SOURCE/LATEST
    command might search for SORT.FOR;3 while a SET SOURCE/EXACT
    command might search for SORT.FOR;1.

    CANCEL SOURCE without the /DISPLAY or /EDIT qualifier cancels the
    effect of both SET SOURCE/DISPLAY and SET SOURCE/EDIT, if both
    were previously given.

    The /DISPLAY qualifier is needed when the files to be displayed
    are no longer in the compilation directory.

    The /EDIT qualifier is needed when the files used for the display
    of source code are different from the editable files. This is the
    case with Ada programs. For Ada programs, the (SET,SHOW,CANCEL)
    SOURCE commands affect the search of files used for source
    display (the "copied" source files in Ada program libraries);
    the (SET,SHOW,CANCEL) SOURCE/EDIT commands affect the search of
    the source files that you edit when using the EDIT command.

    For information specific to Ada programs, see the
    Language_Support Ada help topic.

    Related commands:

       (SET,SHOW) SOURCE

7.3  –  Examples

    1.DBG> SET SOURCE/MODULE=CTEST/EXACT [],SYSTEM::DEVICE:[PROJD]
      DBG> SET SOURCE [PROJA],[PROJB],[PETER.PROJC]
       . . .

      DBG> SHOW SOURCE
         source directory search list for CTEST,
          match the exact source file version:
              []
              SYSTEM::DEVICE:[PROJD]
          source directory list for all other modules,
          match the latest source file version:
              [PROJA]
              [PROJB]
              [PETER.PROJC]
      DBG> CANCEL SOURCE
      DBG> SHOW SOURCE
         source directory search list for CTEST,
          match the exact source file version:
              []
              SYSTEM::DEVICE:[PROJD]
          all other source files will try to match
          the latest source file version

      In this example, the SET SOURCE command establishes a directory
      search list and a search method (the default, latest version)
      for source files other than CTEST. The CANCEL SOURCE command
      cancels the directory search list but does not cancel the
      search method.

    2.DBG> SET SOURCE /EXACT
      DBG> SHOW SOURCE
          no directory search list in effect,
           match the exact source file
      DBG> SET SOURCE [JONES]
      DBG> SHOW SOURCE
          source directory list for all modules,
           match the exact source file version:
               [JONES]
      DBG> CANCEL SOURCE /EXACT
      DBG> SHOW SOURCE
           source directory list for all modules,
           match the latest source file version:
               [JONES]

      In this example, the SET SOURCE/EXACT command establishes a
      search method (exact version) that remains in effect for the
      SET SOURCE [JONES] command. The CANCEL SOURCE/EXACT command not
      only cancels the SET SOURCE/EXACT command, but also affects the
      SET SOURCE [JONES] command.

8  –  TRACE

    Cancels a tracepoint.

    Format

      CANCEL TRACE  [address-expression[, . . . ]]

8.1  –  Parameters

 address-expression

    Specifies a tracepoint to be canceled. Do not use the asterisk
    (*)  wildcard character. Instead, use the /ALL qualifier. Do not
    specify an address expression when using any qualifiers except
    /EVENT, /PREDEFINED, or /USER.

8.2  –  Qualifiers

8.2.1    /ACTIVATING

    Cancels the effect of a previous SET TRACE/ACTIVATING command.

8.2.2    /ALL

    By default, cancels all user-defined tracepoints. When used
    with /PREDEFINED, it cancels all predefined tracepoints but
    no user-defined tracepoints. To cancel all tracepoints, use
    /ALL/USER/PREDEFINED.

8.2.3    /BRANCH

    Cancels the effect of a previous SET TRACE/BRANCH command.

8.2.4    /CALL

    Cancels the effect of a previous SET TRACE/CALL command.

8.2.5    /EVENT

       /EVENT=event-name

    Cancels the effect of a previous SET TRACE/EVENT=event-name
    command. Specify the event name (and address expression, if
    any) exactly as specified with the SET TRACE/EVENT command. To
    identify the current event facility and the associated event
    names, use the SHOW EVENT_FACILITY command.

8.2.6    /EXCEPTION

    Cancels the effect of a previous SET TRACE/EXCEPTION command.

8.2.7    /INSTRUCTION

    Cancels the effect of a previous SET TRACE/INSTRUCTION command.

8.2.8    /LINE

    Cancels the effect of a previous SET TRACE/LINE command.

8.2.9    /PREDEFINED

    Cancels a specified predefined tracepoint without affecting any
    user-defined tracepoints. When used with /ALL, it cancels all
    predefined tracepoints.

8.2.10    /TERMINATING

    Cancels the effect of a previous SET TRACE/TERMINATING command.

8.2.11    /USER

    Cancels a specified user-defined tracepoint without affecting any
    predefined tracepoints. This is the default unless you specify
    /PREDEFINED. To cancel all user-defined tracepoints, use /ALL.

8.3  –  Description

    Tracepoints can be user defined or predefined. User-defined
    tracepoints are explicitly set with the SET TRACE command.
    Predefined tracepoints, which depend on the type of program you
    are debugging (for example, Ada or multiprocess), are established
    automatically when you start the debugger. Use the SHOW TRACE
    command to identify all tracepoints that are currently set. Any
    predefined tracepoints are identified as such.

    User-defined and predefined tracepoints are set and canceled
    independently. For example, a location or event can have both
    a user-defined and a predefined tracepoint. Canceling the user-
    defined tracepoint does not affect the predefined tracepoint, and
    conversely.

    To cancel only user-defined tracepoints, do not specify
    /PREDEFINED with the CANCEL TRACE command (the default is /USER).
    To cancel only predefined tracepoints, specify /PREDEFINED
    but not /USER. To cancel both user-defined and predefined
    tracepoints, use CANCEL TRACE/ALL/USER/PREDEFINED.

    In general, the effect of CANCEL TRACE is symmetrical with
    that of SET TRACE (even though SET TRACE is used only with
    user-defined tracepoints). Thus, to cancel a tracepoint that
    was established at a specific location, specify that same
    location (address expression) with CANCEL TRACE. To cancel
    tracepoints that were established on a class of instructions
    or events, specify the class of instructions or events with the
    corresponding qualifier (/LINE, /BRANCH, /ACTIVATING, /EVENT=,
    and so on). For more information, see the qualifier descriptions.

    To cause the debugger to temporarily ignore a tracepoint, but
    retain definition of the tracepoint, use the command DEACTIVATE
    TRACE. You can later activate the tracepoint (with ACTIVATE
    TRACE).

    Related commands:

       (ACTIVATE,DEACTIVATE,SET,SHOW) TRACE
       CANCEL ALL
       (SET,SHOW,CANCEL) BREAK
       (SET,SHOW) EVENT_FACILITY

8.4  –  Examples

    1.DBG> CANCEL TRACE MAIN\LOOP+10

      This command cancels the user-defined tracepoint at the
      location MAIN\LOOP+10.

    2.DBG> CANCEL TRACE/ALL

      This command cancels all user-defined tracepoints.

    3.all> CANCEL TRACE/TERMINATING

      This command cancels a previous SET TRACE/TERMINATING command.
      As a result, a user-defined tracepoint is not triggered when a
      process does an image exit.

    4.DBG> CANCEL TRACE/EVENT=RUN %TASK 3

      This command cancels the tracepoint that was set to trigger
      when task 3 (task ID = 3) entered the RUN state.

9  –  TYPE

9.1    /OVERRIDE

    Cancels the override type established by a previous SET
    TYPE/OVERRIDE command.

    Format

      CANCEL TYPE/OVERRIDE

9.1.1  –  Description

    The CANCEL TYPE/OVERRIDE command sets the current override type
    to "none." As a result, a program location associated with a
    compiler-generated type is interpreted according to that type.

    Related commands:

       DEPOSIT
       EXAMINE
       (SET,SHOW) EVENT_FACILITY
       (SET,SHOW) TYPE/OVERRIDE

9.1.2  –  Example

  DBG> CANCEL TYPE/OVERRIDE

      This command cancels the effect of a previous SET TYPE/OVERRIDE
      command.

10  –  WATCH

    Cancels a watchpoint.

    Format

      CANCEL WATCH  [address-expression[, . . . ]]

10.1  –  Parameters

 address-expression

    Specifies a watchpoint to be canceled. With high-level languages,
    this is typically the name of a variable. Do not use the asterisk
    (*)  wildcard character. Instead, use the /ALL qualifier. Do not
    specify an address expression with /ALL.

10.2  –  Qualifiers

10.2.1    /ALL

    Cancels all watchpoints.

10.3  –  Description

    The effect of the CANCEL WATCH command is symmetrical with the
    effect of the SET WATCH command. To cancel a watchpoint that was
    established at a specific location with the SET WATCH command,
    specify that same location with CANCEL WATCH. Thus, to cancel
    a watchpoint that was set on an entire aggregate, specify the
    aggregate in the CANCEL WATCH command; to cancel a watchpoint
    that was set on one element of an aggregate, specify that element
    in the CANCEL WATCH command.

    The CANCEL ALL command also cancels all watchpoints.

    To cause the debugger to temporarily ignore a watchpoint, but
    not delete the definition of the watchpoint, use the command
    DEACTIVATE WATCH. You can later activate the watchpoint (with
    ACTIVATE WATCH).

    Related commands:

       (ACTIVATE,DEACTIVATE,SET,SHOW) WATCH
       CANCEL ALL
       (SET,SHOW,CANCEL) BREAK
       (SET,SHOW,CANCEL) TRACE

10.4  –  Examples

    1.DBG> CANCEL WATCH SUB2\TOTAL

      This command cancels the watchpoint at variable TOTAL in module
      SUB2.

    2.DBG> CANCEL WATCH/ALL

      This command cancels all watchpoints you have set.

11  –  WINDOW

    Permanently deletes a screen window definition.

                                   NOTE

       This command is not available in the VSI DECwindows Motif for
       OpenVMS user interface to the debugger.

    Format

      CANCEL WINDOW  [window-name[, . . . ]]

11.1  –  Parameters

 window-name

    Specifies the name of a screen window definition to be canceled.
    Do not use the asterisk (*)  wildcard character. Instead, use
    the /ALL qualifier. Do not specify a window definition name with
    /ALL.

11.2  –  Qualifiers

11.2.1    /ALL

    Cancels all predefined and user-defined window definitions.

11.3  –  Description

    When a window definition is canceled, you can no longer use its
    name in a DISPLAY command. The CANCEL WINDOW command does not
    affect any displays.

    Related commands:

       (SHOW,CANCEL) DISPLAY
       (SET,SHOW) WATCH

11.4  –  Example

  DBG> CANCEL WINDOW MIDDLE

      This command permanently deletes the screen window definition
      MIDDLE.
Close Help