You can set unconditional breakpoints directly on the Source Listing screen just as easily as you displayed and modified TASKNUM. Type u to the left of each statement where you want CA InterTest for CICS to halt program execution. Let us see how to set a breakpoint at the following IF statement:
IF TASKNUM = 1 THEN
CA InterTest for CICS Release 9.1.00 - PROTSYM FILE ABEND DETECTED BREAKPOINT COMMAND ===> Program= PLIDEMO Option # Stmt # Margin= 01 Search= ------------------------------------------------------------------------------- _____ TASKNUM | 00000. ---------+--------------------------------------------------------------------- _ 636.1 CONTINUE_TASK: _ 637.1 MAPNUM = '00'; A ==>.1 1 TASKNUM = TASKNUM + 1; _ 639.1 1 IF TASKNUM > 2 THEN _ 640.1 1 GOTO END_SESSION; u 641.1 1 IF TASKNUM = 1 THEN _ 642.1 1 GOTO SENDSCR3; _ 643.1 1 GOTO END_SESSION; _ 644.1 _ 645.1 1 SENDSCR3: /** ASRA CONGRATULAT _ 646.1 /* EXEC CICS SEND MAP('DASRA') _ 647.1 MAPSET('IN25PMP') _ 648.1 WAIT _ 649.1 ERASE */ _ 650.1 DO; _ 651.1 1 1 DCL DFHENTRY_BF5EF358_068E978B BASED(ADDR(DFHEI0) _ 652.1 ASSEMBLER) ENTRY(*,CHAR(7),*,FIXED BIN(15),CHAR(7));
CA InterTest for CICS resumes program execution and continues until it reaches the breakpoint you just set. CA InterTest for CICS halts the program before that statement executes and displays the following screen.
CA InterTest for CICS Release 9.1.00 - PROTSYM FILE UNCOND BEFORE BREAKPOINT COMMAND ===> Program= PLIDEMO Option # Stmt # Margin= 01 Search= ------------------------------------------------------------------------------- _____ TASKNUM | +00001. ---------+--------------------------------------------------------------------- _ 639.1 1 IF TASKNUM > 2 THEN _ 640.1 1 GOTO END_SESSION; U ==>.1 1 IF TASKNUM = 1 THEN _ 642.1 1 GOTO SENDSCR3; _ 643.1 1 GOTO END_SESSION; . . .
Notice the U to the left of the highlighted statement. It identifies the breakpoint as an unconditional breakpoint. For an Automatic, Conditional, or Request breakpoint, CA InterTest for CICS displays an A, C, or R, respectively.
Note: The value of TASKNUM is now 1 because the TASKNUM = TASKNUM + 1 statement executed successfully.
When you are stopped at a breakpoint, you have many choices. You can do the following tasks:
In fact, a special Breakpoint Primary Option menu displays when you press PF6 Menu at a breakpoint. This menu makes it easy to choose a breakpoint activity to accomplish your testing goal. When debugging your own programs, you typically perform one or more of these activities, which are detailed in the next chapter. Since PLIDEMO has no more errors, we will complete the demo session.
As you continue testing and debugging, you should clean up by removing breakpoints that are no longer needed so that when retesting the program it will not stop unnecessarily. Next, remove the unconditional breakpoint you just set so that PLIDEMO does not stop at this statement when it re-executes.
CA InterTest for CICS Release 9.1.00 - PROTSYM FILE UNCOND BEFORE BREAKPOINT COMMAND ===> Program= PLIDEMO Option # Stmt # Margin= 01 Search= ------------------------------------------------------------------------------- _____ TASKNUM | +00001. ---------+--------------------------------------------------------------------- _ 639.1 1 IF TASKNUM > 2 THEN _ 640.1 1 GOTO END_SESSION; x ==>.1 1 IF TASKNUM = 1 THEN _ 642.1 1 GOTO SENDSCR3; _ 643.1 1 GOTO END_SESSION; . . .
CA InterTest for CICS removes the unconditional breakpoint.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|