DISABLE command

The DISABLE command makes an AT or pattern-match breakpoint inoperative. However, the breakpoint is not cleared. Later, you can make the breakpoint operative by using the ENABLE command.

>>-DISABLE--+-AT_command-----------------------------------------------+--;-><
            +-CADP--+-*-------------------------------------------+----+      
            |       '-+----------------------+--+---------------+-'    |      
            |         '-PROGRAM--+-prog_id-+-'  '-CU--+-cu_id-+-'      |      
            |                    '-*-------'          '-*-----'        |      
            '-DTCN--+-*----------------------------------------------+-'      
                    '-+-------------------------+--+---------------+-'        
                      '-LOADMOD--+-loadmod_id-+-'  '-CU--+-cu_id-+-'          
                                 '-*----------'          '-*-----'            

AT_command

An enabled AT command. The AT command must be complete except that the every_clause and command are omitted. Valid forms are the same as those allowed with CLEAR AT.

DTCN LOADMOD, DTCN CU, CADP PROGRAM, or CADP CU

Prevents Debug Tool from being started by a program, load module, or compile unit specified in prog_id, loadmod_id, or cu_id that matches a program or compile unit specified in a DTCN or CADP profile. The following comparisons are made:

• For DTCN, Debug Tool compares loadmod_id with the value in the LoadMod field and cu_id with the value in the CU field.
• For CADP, prog_id is compared to what is specified in the Program field and cu_id is compared to what is specified in the Compile Unit field.

You can specify a specific name (for example, PROG1) or a partial name with the wild card character (for example, EMPL*).

Usage notes

• You can use the DISABLE CADP and DISABLE DTCN commands in remote debug mode.
• You can use the DISABLE command to disable either active or suspended breakpoints. However, you cannot use it to disable suspended label breakpoints.
• If you want to disable a suspended breakpoint, you must specify both the load module and CU name.
• To reenable a disabled AT command, use the ENABLE command.
• Disabling an AT command does not affect its replacement by a new (enabled) version if an overlapping AT command is later specified. It also does not prevent removal by a CLEAR AT command.
• Breakpoints already disabled within the range(s) specified in the specific AT command are unaffected; however, a warning message is issued for any specified range found to contain no enabled breakpoints.
• The DISABLE command cannot be used while you replay recorded statements by using the PLAYBACK commands.
• For pseudo-conversational applications running under CICS®, the DISABLE CADP or DISABLE DTCN commands apply only to the current CICS pseudo-conversational task.
• For PL/I, COBOL, LangX COBOL, assembler and disassembly, if the cu_id is mixed case or case sensitive, you must enclose the name in quotation marks (") or apostrophes (').
• For C and C++, Debug Tool always treats the cu_id as case sensitive, even if it is not enclosed in quotation marks (").

Examples

• Disable the breakpoint that was set by the command AT ENTRY myprog CALL proc1;.

  DISABLE AT ENTRY myprog;

• If statement 25 is in a loop and you set the following breakpoint:

  AT EVERY 5 FROM 1 TO 100 STATEMENT 25 LIST x;

  to disable it, enter:

  DISABLE AT STATEMENT 25;

  You do not need to reenter the every_clause or the command list. To restore the breakpoint, enter:

  ENABLE AT STATEMENT 25;

• Debug Tool starts every time PROGA runs because you have a DTCN profile that specifies an asterisk (*) in the LoadMod field and PROGA in the CU field. field. If you do not want Debug Tool to start every time PROGA runs, enter one of the following commands:
  • DISABLE DTCN LOADMOD * CU PROGA;
  • DISABLE DTCN CU PROGA;
• You have a CADP profile that specifies PROG1 in the Program field and CU1 in the Compile Unit field. If you do not want Debug Tool to start every time this program and compile unit are run, enter the following command:

  DISABLE CADP PROGRAM PROG1 CU CU1;

• You have a CADP profile that specifies CU1 in the Compile Unit field. If you do not want Debug Tool to start every time the compile unit is run, enter one of the following commands:
  • DISABLE CADP PROGRAM * CU CU1;
  • DISABLE CADP CU CU1;
• You have several CADP profiles and Debug Tool is started every time a program matches one of these profiles. If you do not want Debug Tool to be started every time a program matches any of these profiles, enter the following command:

  DISABLE CADP *;

Refer to the following topics for more information related to the material discussed in this topic.

• Related tasks
• "Controlling pattern-match breakpoints with the ENABLE and DISABLE commands" in the Debug Tool User's Guide
• Related references
• ENABLE command
• DISABLE prefix (full-screen mode)
• LIST DTCN or CADP command
• Debug Tool commands supported in remote debug mode