The following qualifiers affect what output is displayed when a
    breakpoint is reached:

       /[NO]SILENT
       /[NO]SOURCE

    The following qualifiers affect the timing and duration of
    breakpoints:

       /AFTER:n
       /TEMPORARY

    Use the /MODIFY qualifier to monitor changes at program locations
    (typically changes in the values of variables).

    If you set a breakpoint at a location currently used as
    a tracepoint, the tracepoint is canceled in favor of the
    breakpoint, and vice versa.

    On OpenVMS Alpha and Integrity servers, the SET BREAK/UNALIGNED_
    DATA command calls the $START_ALIGN_FAULT_REPORT system service
    routine. Do not issue this command if the program you are
    debugging includes a call to the same $START_ALIGN_FAULT_REPORT
    routine. If you issue the command before the program call, the
    program call fails. If the program call occurs before you issue
    the command, unaligned breaks are not set.

    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 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.

    Related commands:

       (ACTIVATE,DEACTIVATE,SHOW,CANCEL) BREAK
       CANCEL ALL
       GO
       (SET,SHOW) EVENT_FACILITY
       SET STEP [NO]SOURCE
       SET TRACE
       SET WATCH
       STEP