DBG$HELP.HLB  —  DEBUG  ACTIVATE

1  –  BREAK

    Activates a breakpoint that you have previously set and then
    deactivated.

    Format

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

1.1  –  Parameters

 address-expression

    Specifies a breakpoint to be activated. 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.

1.2  –  Qualifiers

1.2.1    /ACTIVATING

    Activates a breakpoint established by a previous SET
    BREAK/ACTIVATING command.

1.2.2    /ALL

    By default, activates all user-defined breakpoints. When used
    with /PREDEFINED, activates all predefined breakpoints but
    no user-defined breakpoints. To activate all breakpoints, use
    /ALL/USER/PREDEFINED.

1.2.3    /BRANCH

    Activates a breakpoint established by a previous SET BREAK/BRANCH
    command.

1.2.4    /CALL

    Activates a breakpoint established by a previous SET BREAK/CALL
    command.

1.2.5    /EVENT

       /EVENT=event-name

    Activates a breakpoint established by 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.

1.2.6    /EXCEPTION

    Activates a breakpoint established by a previous SET
    BREAK/EXCEPTION command.

1.2.7    /HANDLER

    Activates a breakpoint established by a previous SET
    BREAK/HANDLER command.

1.2.8    /INSTRUCTION

    Activates a breakpoint established by a previous SET
    BREAK/INSTRUCTION command.

1.2.9    /LINE

    Activates a breakpoint established by a previous SET BREAK/LINE
    command. Do not specify an address expression with this
    qualifier.

1.2.10    /PREDEFINED

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

1.2.11    /SYSEMULATE

    (Alpha only) Activates a breakpoint established by a previous SET
    BREAK/SYSEMULATE command.

1.2.12    /TERMINATING

    Activates a breakpoint established by a previous SET
    BREAK/TERMINATING command.

1.2.13    /UNALIGNED_DATA

    (Alpha and Integrity servers only) Activates a breakpoint
    established by a previous SET BREAK/UNALIGNED_DATA command, or
    reactivates a breakpoint previously disabled by a DEACTIVATE
    BREAK/UNALIGNED_DATA command.

1.2.14    /USER

    Activates a specified user-defined breakpoint without affecting
    any predefined breakpoints. To activate all user-defined
    breakpoints, use the /ALL qualifier.

1.3  –  Description

    User-defined breakpoints are activated when you set them with
    the SET BREAK command. Predefined breakpoints are activated by
    default. Use the ACTIVATE BREAK command to activate one or more
    breakpoints that you deactivated with DEACTIVATE BREAK.

    Activating and deactivating breakpoints enables you to run and
    rerun your program with or without breakpoints without having to
    cancel and then reset them. By default, the RERUN command saves
    the current state of all breakpoints (activated or deactivated).

    You can activate and deactivate user-defined breakpoints or
    predefined breakpoints or both. To check if a breakpoint is
    activated, use the SHOW BREAK command.

    Related commands:

       CANCEL ALL
       RERUN
       (SET,SHOW,CANCEL,DEACTIVATE) BREAK
       (SET,SHOW) EVENT_FACILITY

1.4  –  Examples

    1.DBG> ACTIVATE BREAK MAIN\LOOP+10

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

    2.DBG> ACTIVATE BREAK/ALL

      This command activates all user-defined breakpoints.

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

      This command activates all breakpoints, both user-defined and
      predefined.

2  –  TRACE

    Activates a tracepoint that you have previously set and then
    deactivated.

    Format

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

2.1  –  Parameters

 address-expression

    Specifies a tracepoint to be activated. 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

    Activates a tracepoint established with a previous SET
    TRACE/ACTIVATING command.

2.2.2    /ALL

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

2.2.3    /BRANCH

    Activates a tracepoint established with a previous SET
    TRACE/BRANCH command.

2.2.4    /CALL

    Activates a tracepoint established with a previous SET TRACE/CALL
    command.

2.2.5    /EVENT

       /EVENT=event-name

    Activates a tracepoint established with 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.

2.2.6    /EXCEPTION

    Activates a tracepoint established with a previous SET
    TRACE/EXCEPTION command.

2.2.7    /INSTRUCTION

    Activates a tracepoint established with a previous SET
    TRACE/INSTRUCTION command.

2.2.8    /LINE

    Activates a tracepoint established with a previous SET TRACE/LINE
    command.

2.2.9    /PREDEFINED

    Activates a specified predefined tracepoint without affecting
    any user-defined tracepoints. When used with /ALL, activates all
    predefined tracepoints.

2.2.10    /TERMINATING

    Activates a tracepoint established with a previous SET
    TRACE/TERMINATING command.

2.2.11    /USER

    Activates a specified user-defined tracepoint without affecting
    any predefined tracepoints. To activate all user-defined
    tracepoints, use the /ALL qualifier.

2.3  –  Description

    User-defined tracepoints are activated when you set them with
    the SET TRACE command. Predefined tracepoints are activated by
    default. Use the ACTIVATE TRACE command to activate one or more
    tracepoints that you deactivated with DEACTIVATE TRACE.

    Activating and deactivating tracepoints enables you to run and
    rerun your program with or without tracepoints without having to
    cancel and then reset them. By default, the RERUN command saves
    the current state of all tracepoints (activated or deactivated).

    You can activate and deactivate user-defined tracepoints or
    predefined tracepoints or both. To check if a tracepoint is
    activated, use the SHOW TRACE command.

    Related commands:

       CANCEL ALL
       RERUN
       (SET,SHOW) EVENT_FACILITY
       (SET,SHOW,CANCEL,DEACTIVATE) TRACE

2.4  –  Examples

    1.DBG> ACTIVATE TRACE MAIN\LOOP+10

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

    2.DBG> ACTIVATE TRACE/ALL

      This command activates all user-defined tracepoints.

3  –  WATCH

    Activates a watchpoint that you have previously set and then
    deactivated.

    Format

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

3.1  –  Parameters

 address-expression

    Specifies a watchpoint to be activated. 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.

3.2  –  Qualifiers

3.2.1    /ALL

    Activates all watchpoints.

3.3  –  Description

    Watchpoints are activated when you set them with the SET WATCH
    command. Use the ACTIVATE WATCH command to activate one or more
    watchpoints that you deactivated with DEACTIVATE WATCH.

    Activating and deactivating watchpoints enables you to run and
    rerun your program with or without watchpoints without having to
    cancel and then reset them.

    By default, the RERUN command saves the current state of all
    static watchpoints (activated or deactivated). The state of
    a particular nonstatic watchpoint might or might not be saved
    depending on the scope of the variable being watched relative to
    the main program unit (where execution restarts).

    To check if a watchpoint is activated, use the SHOW WATCH
    command.

    Related commands:

       CANCEL ALL
       RERUN
       (SET,SHOW,CANCEL,DEACTIVATE) WATCH

3.4  –  Examples

    1.DBG> ACTIVATE WATCH SUB2\TOTAL

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

    2.DBG> ACTIVATE WATCH/ALL

      This command activates all watchpoints you have set and
      deactivated.
Close Help