1 – BREAK
Deactivates a breakpoint, which you can later activate.
Format
DEACTIVATE BREAK [address-expression[, . . . ]]
1.1 – Parameters
address-expression
Specifies a breakpoint to be deactivated. 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
Deactivates a breakpoint established by a previous SET
BREAK/ACTIVATING command.
1.2.2 /ALL
By default, deactivates all user-defined breakpoints. When used
with /PREDEFINED, deactivates all predefined breakpoints but
no user-defined breakpoints. To deactivate all breakpoints, use
/ALL/USER/PREDEFINED.
1.2.3 /BRANCH
Deactivates a breakpoint established by a previous SET
BREAK/BRANCH command.
1.2.4 /CALL
Deactivates a breakpoint established by a previous SET BREAK/CALL
command.
1.2.5 /EVENT
/EVENT=event-name
Deactivates 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
Deactivates a breakpoint established by a previous SET
BREAK/EXCEPTION command.
1.2.7 /HANDLER
Deactivates a breakpoint established by a previous SET
BREAK/HANDLER command.
1.2.8 /INSTRUCTION
Deactivates a breakpoint established by a previous SET
BREAK/INSTRUCTION command.
1.2.9 /LINE
Deactivates a breakpoint established by a previous SET BREAK/LINE
command.
1.2.10 /PREDEFINED
Deactivates a specified predefined breakpoint without affecting
any user-defined breakpoints. When used with /ALL, deactivates
all predefined breakpoints.
1.2.11 /SYSEMULATE
(Alpha only) Deactivates a breakpoint established by a previous
SET BREAK/SYSEMULATE command.
1.2.12 /TERMINATING
Deactivates a breakpoint established by a previous SET
BREAK/TERMINATING command.
1.2.13 /UNALIGNED_DATA
(Alpha only) Deactivates a breakpoint established by a previous
SET BREAK/UNALIGNED_DATA command.
1.2.14 /USER
Deactivates a specified user-defined breakpoint. To deactivate
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 DEACTIVATE BREAK command to deactivate one or
more breakpoints.
If you deactivate a breakpoint, the debugger ignores the
breakpoint during program execution. To activate a deactivated
breakpoint, use the ACTIVATE BREAK command. You can activate and
deactivate user-defined and predefined breakpoints separately.
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).
To check if a breakpoint is deactivated, use the SHOW BREAK
command.
Related commands:
CANCEL ALL
RERUN
(SET,SHOW,CANCEL,ACTIVATE) BREAK
(SET,SHOW) EVENT_FACILITY
1.4 – Examples
1.DBG> DEACTIVATE BREAK MAIN\LOOP+10
This command deactivates the user-defined breakpoint set at the
address expression MAIN\LOOP+10.
2.DBG> DEACTIVATE BREAK/ALL
This command deactivates all user-defined breakpoints.
2 – TRACE
Deactivates a tracepoint, which you can later activate.
Format
DEACTIVATE TRACE [address-expression[, . . . ]]
2.1 – Parameters
address-expression
Specifies a tracepoint to be deactivated. 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
Deactivates a tracepoint established with a previous SET
TRACE/ACTIVATING command.
2.2.2 /ALL
By default, deactivates all user-defined tracepoints. When used
with /PREDEFINED, it deactivates all predefined tracepoints but
no user-defined tracepoints. To deactivate all tracepoints, use
/ALL/USER/PREDEFINED.
2.2.3 /BRANCH
Deactivates a tracepoint established with a previous SET
TRACE/BRANCH command.
2.2.4 /CALL
Deactivates a tracepoint established with a previous SET
TRACE/CALL command.
2.2.5 /EVENT
/EVENT=event-name
Deactivates 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
Deactivates a tracepoint established with a previous SET
TRACE/EXCEPTION command.
2.2.7 /INSTRUCTION
Deactivates a tracepoint established with a previous SET
TRACE/INSTRUCTION command.
2.2.8 /LINE
Deactivates a tracepoint established with a previous SET
TRACE/LINE command.
2.2.9 /PREDEFINED
Deactivates a specified predefined tracepoint without affecting
any user-defined tracepoints. When used with /ALL, it deactivates
all predefined tracepoints.
2.2.10 /TERMINATING
Deactivates a tracepoint established with a previous SET
TRACE/TERMINATING command.
2.2.11 /USER
Deactivates a specified user-defined tracepoint without affecting
any predefined tracepoints. When used with /ALL, it deactivates
all user-defined tracepoints. The /USER qualifier is the default
unless you specify /PREDEFINED.
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 DEACTIVATE TRACE command to deactivate one or
more tracepoints.
If you deactivate a tracepoint, the debugger ignores the
tracepoint during program execution. To activate a deactivated
tracepoint, use the ACTIVATE TRACE command. You can activate and
deactivate user-defined and predefined tracepoints separately.
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).
To check if a tracepoint is deactivated, use the SHOW TRACE
command.
Related commands:
CANCEL ALL
RERUN
(SET,SHOW) EVENT_FACILITY
(SET,SHOW,CANCEL,ACTIVATE) TRACE
2.4 – Examples
1.DBG> DEACTIVATE TRACE MAIN\LOOP+10
This command deactivates the user-defined tracepoint at the
location MAIN\LOOP+10.
2.DBG> DEACTIVATE TRACE/ALL
This command deactivates all user-defined tracepoints.
3 – WATCH
Deactivates a watchpoint, which you can later activate.
Format
DEACTIVATE WATCH [address-expression[, . . . ]]
3.1 – Parameters
address-expression
Specifies a watchpoint to be deactivated. 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
Deactivates all watchpoints.
3.3 – Description
Watchpoints are activated when you set them with the SET WATCH
command. Use the DEACTIVATE WATCH command to deactivate one or
more watchpoints.
If you deactivate a watchpoint, the debugger ignores the
watchpoint during program execution. To activate a deactivated
watchpoint, use the ACTIVATE WATCH command. 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 deactivated, use the SHOW WATCH
command.
Related commands:
CANCEL ALL
RERUN
(SET,SHOW,CANCEL,ACTIVATE) WATCH
3.4 – Examples
1.DBG> DEACTIVATE WATCH SUB2\TOTAL
This command deactivates the watchpoint at variable TOTAL in
module SUB2.
2.DBG> DEACTIVATE WATCH/ALL
This command deactivates all watchpoints you have set.