Breakpoint Displays for NonSymbolic Programs › Unconditional Breakpoint

Unconditional Breakpoint

The following panel shows a sample non‑symbolic breakpoint screen for an unconditional breakpoint:

Œ					            Ž       
CNTL=GO,TASK=00063,C             at +00BB0           pgm=COBDEMO ,addr=24510BD0
 UBP: F=U056,T=U056 Unconditional breakpoint.                                
‘Mon.as COBDEMO        ’   Pgm COBDEMO  Trx DEMC Fac U056 Trm     in.....out  
“Task 00063 at +00BB0            ”TIOA none                    +00A90  +00B16
 DSA 23708B88  TGT 23709D60  •CWK 2370A058                      +00B06  +00B16
 BLLS:  0 001000D0  1 00000000  2 00001000  3 00002000            00002  times 
        4 00003000  5 00004000  6 00000000  7 00000000           +00B06  +00B24
      8 00000000  9 00000000                                   +00B36  +00BA4
                                                              ‚ +00BA8  curr. 
NEXT MVC   X'B0'(4,R8),8(R7)                  AT +00BB0  ƒ               
PREV OI    X'84'(RD),X'01'                    AT +00BAC  „               
        Press ENTER to execute the default command on line 1,                
        OVERTYPE it, or use any of the following PF KEYS:                    
 1 Help  2         3 Source  4         5 Resume     6 Menu  …              
 7       8         9 1 Inst 10        11 Backtrace 12 Status                   
 Addr and content of relevant area:                                            
23708C0C 21        †        †    

Œ

Default CNTL command and location information. For an automatic breakpoint, the default command abends the task. For all other breakpoints, the default is to continue task execution. The command can be modified or overtyped with any other CA InterTest for CICS command.



Displacement of the instruction about to be executed follows the command on the top line.

Ž

Name of the program that was stopped by CA InterTest for CICS follows the displacement.



Address of the instruction that triggered the breakpoint.

Note: CA InterTest for CICS stopped the program before this instruction was executed.



Type of breakpoint: automatic (ABP), unconditional (UBP), conditional (CBP), request (RBP), or single‑stepping (SBP). In most cases, there is a one or two line message explaining exactly why the breakpoint occurred.

‘

Name of the monitoring table entry.

’

Program name (Pgm), transaction code (Trx), and CICS facility (Fac) associated with the task; in this case, terminal (Trm) U056.

“

Task number and displacement of the instruction about to be executed.

”

Address of the first TIOA on the chain of such areas allocated to the task. To display the area, issue the command CORE=TIOA.

•

Addresses of the areas containing the copy of COBOL DSA, TGT, Working‑Storage, and Local-Storage for this task. If the program does not contain a DSA or Local-Storage, the fields are left blank. To display the area, issue the appropriate CORE command (for example, CORE=CWK).



COBOL BLL cells or general registers 0‑15 for Assembler or PL/I programs.

‚

Backtrace of the starting (IN) and ending (OUT) displacements or addresses of the most recently executed pieces of code. Every break in the sequential execution of the program results in a new entry. A loop counter tells how many times the piece of code above it was executed. The entry curr. stands for current location.

ƒ

Machine code and offset (or absolute address) of the instruction that triggered the breakpoint.

„

Machine code and offset (or absolute address) of the last instruction executed.

…

Program function keys for immediate access to CA InterTest for CICS facilities.

†

Address and representation (in both character and hexadecimal form) of the area of main storage that would have been modified by the next instruction.