COBOL Advanced Demo Session › Option 07: How to Test a Composite Module › Re-execute the Demo Program

Re-execute the Demo Program

Now you can re-execute the demo program.

1. Press PF4.
2. CA InterTest for CICS displays the Primary Option Menu.
3. Select option X Exit to exit to CICS.
4. Clear the screen and type the transaction ID DEMC for the COBOL demo program and press Enter.

   CA InterTest for CICS displays the automatic breakpoint at which you were initially halted. However, now the breakpoint occurs at the actual statement in ASBIN25 that triggered the abend, not at the CALL to ASBIN25.

   CA InterTest for CICS V9.1 ‑ PROTSYM FILE SOURCE LISTING BREAKPOINT      
   COMMAND ===>                                                             
   Program= ASBIN25  Option #       Stmt #        Displacement=   Margin= 01  
                                           Search=                          
   ‑‑‑‑‑‑‑‑‑+‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
        LOC  OBJECT CODE    ADDR1 ADDR2  STMT        SOURCE STATEMENT        
    _ 0000BA                              280 CONTINUE DS    0H             
    A 0000BA FA20 D1A0 211B 001A0 0011B   ==>          AP    TASKNUM,=P'1'  
        ==>                                                         
        ==> ASRA ABEND (0C7) detected and prevented. Caused by invalid decimal     
        ==> arithmetic data format.                                
        ==>                                                           
        ==>      Press PF1 for a detailed description.               
        ==>                                                          
    _ 0000C0 F920 D1A0 211C 001A0 0011C   282          CP    TASKNUM,=P'2'
   .
   .
   .            
   

   Note: The name in the Program field is ASBIN25. When control passes to ASBIN25, CA InterTest for CICS starts monitoring that program because you set composite support. Setting composite support enables CA InterTest to identify and display the statement in the subroutine where the error occurred.

   The error occurred because of improperly formatted data in TASKNUM. The AP instruction tries to move a packed decimal 1 to TASKNUM. TASKNUM is defined as a packed decimal field, but it contains binary zeros instead of a valid packed decimal value. This is the same type of error you corrected in the basic demo session.