Advanced Demo Session › Option 05: How to Test a Composite Module

Option 05: How to Test a Composite Module

This option details how you can use CA InterTest for CICS to test and debug a composite module. Composite support is a 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 earlier in this chapter in Composite Support.

Note: This program uses mixed case in the display of source code and maps on the screen. If you need or wish to use a program that displays in UPPERCASE only, substitute the letters UEML in lieu of DEML as the last four characters of the program name (that is, select PLIUEML instead of PLIDEML).

In this section you will test three programs:

• The main program, PLIDEML, which like PLIDEMO, is invoked by the transaction, demp.
• Two subroutines called by PLIDEML:
  • ASBIN25, written in Assembler
  • PSBIN25, written in PL/I

PLIDEML has several subroutines; however, you need to test only two of them.

Similarly, composite modules at your site might have many called subroutines, but you need to tell CA InterTest for CICS only about the ones you want to test.

1. Display the CA InterTest for CICS Demo Session Options Menu.
2. Select option 05, and press Enter.

   The demo program displays a description of what will occur in this part of the demo.

       **********************************************************************      
       ****                                                              ****      
       ****                  CA InterTest Demo Session                   ****      
       ****                     Composite Support                        ****      
       ****                                                              ****      
       **********************************************************************      
                                                                                   
    Program PLIDEML calls two subroutines:  ASBIN25 and PSBIN25.                 
                                                                                   
    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 PLIDEML.          
    3. Type in transaction id DEMP 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 PSBIN25. 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
   

3. Press Enter.

   The composite module halts at an automatic breakpoint at statement CALL ASBIN25.

   Note: If a screen other than the one below appears, someone at your site has already set composite support for the composite module.

   CA InterTest for CICS r8.5   - PROTSYM FILE  ABEND DETECTED BREAKPOINT         
   COMMAND ===>                                                                    
   Program= PLIDEML  Option #       Stmt #                             Margin= 01  
                                           Search=                                 
   ---------+--------------------------------------------------------------------- 
    _  1644.1     1                GOTO END_SESSION;                               
    _  1645.1                                                                      
    A   ==>.1     1      CALLCOMP:      ==>                                     
        ==> CICS abend intercepted. Abend code = ASRA.   EXEC CICS request was  
        ==> LINK. Abend in program ASBIN25  at offset 000000E8.                 
        ==>                                                                     
        ==>      Press PF1 for a detailed description.                          
        ==>                                                                     
                                                                                   
    _  1647.1                       /* EXEC CICS LINK PROGRAM ('PLIDEML') */       
    _  1648.1                       DO;                                            
    _  1649.1     1  1              DCL DFHENTRY_BF6577CC_B52431E6 BASED(ADDR(DFH  
    _  1650.1            NTER ASSEMBLER) ENTRY(*,CHAR(8));                         
    _  1651.1     1  1              CALL DFHENTRY_BF6577CC_B52431E6('000011100000  
    _  1652.1            00000000000110000000000000000000000010000000011110000111  
    _  1653.1            11011011110000111100001111000011110000'B /* '0E 02 80 00  
    _  1654.1             F0 F5 F9 F6 F0 F0 F0 F0 'X */,'PLIDEML');                
    _  1655.1     1  1              END;                                           
    _  1656.1     1                 GOTO SENDMP00;                              
   

   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.

   Notice that the name in the Program field is PLIDEML, the name of the composite module. This is the program CA InterTest for CICS is monitoring; the 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. This means you can set breakpoints and other monitoring options for that subroutine, and 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 will abend the task, set composite support, and then resume testing.