This option details how you can use CA InterTest for CICS to test and debug a composite module. Composite support is an CA InterTest for CICS feature designed to help programmers who are responsible for testing and debugging called subroutines. Skip this option if you are not responsible for these subroutines.
To perform this option, you should have set monitoring for the composite module as described in Using Composite Support part of Demo Preliminaries.
In this section you will be testing three programs, as follows:
The CA InterTest Demo Session Options Menu should be displayed.
A description of what occurs in this part of the demo displays.
********************************************************************** **** **** **** CA InterTest Demo Session **** **** Composite Support **** **** **** ********************************************************************** Program COBDEML calls two subroutines: ASBIN25 and CSBIN25. 1. CA InterTest halts the program at an automatic breakpoint caused by an ASRA. Without composite support, you will see only that you are stopped at the CALL to ASBIN25. 2. You abend the task, and then set composite support for COBDEML. 3. Type in transaction id DEMC again. This time you will see the actual instruction causing the ASRA within the subroutine. 4. You correct the problem that caused the automatic breakpoint. 5. You then set an unconditional breakpoint in CSBIN25. When you resume execution, the program is halted at that breakpoint. 6. You remove the breakpoint and the program completes execution. When this section of the demo completes, you will return to the Options Menu. Press ENTER to continue or CLEAR to terminate.
The composite module halts at an automatic breakpoint at statement CALL ASBIN25.
Note: If a screen other than the following screen displays, someone at your site has already set composite support for the composite module. In this case, skip to Re-execute the Demo Program.
CA InterTest for CICS V9.1‑ PROTSYM FILE SOURCE LISTING BREAKPOINT COMMAND ===> Program= COBDEML Option # Stmt # Margin= 01 Search= ‑‑‑‑‑‑‑‑‑+‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ 00154 _ 00155 CALL‑ASSEMBLER. A ==> CALL 'ASBIN25' USING DFHEIBLK. ==> ==> ASRA ABEND (0C7) detected and prevented. Caused by invalid decimal ==> arithmetic data format. ==> ==> Press PF1 for a detailed description. ==> _ 00157 MOVE COMM‑SW2 TO NUM‑CHOICES. 00158 _ 00159 CALL‑COBOL. . . .
CA InterTest for CICS halted the composite module at an automatic breakpoint because it detected and prevented an error in ASBIN25 when control passed to that subroutine. However, so far you do not know where in ASBIN25 the error occurred.
Note: The name in the Program field is the name of the composite module COBDEML. This is the program CA InterTest for CICS is monitoring—the main composite program for which you set monitoring before you began the advanced demo session.
Setting composite support lets you test and debug a called subroutine as if it were a separate program, with full symbolic support. That means you can set breakpoints and other monitoring options for that subroutine. When CA InterTest for CICS detects an error, it generates an automatic breakpoint at the statement that triggered the abend, not at the CALL.
You can set composite support before you begin to test a program or at any time during testing. In this case, you are going to abend the task, set composite support, and then resume testing.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|