The CA Intertest for CICS variable VBP breakpoints do not work.

book

Article ID: 5746

calendar_today

Updated On:

Products

CA InterTest - CICS CA InterTest - Batch CA InterTest VSE - CICS

Issue/Introduction

The client just upgraded to CA Intertest CICS release 9.1. The user sets a variable breakpoint VBP by placing a V next to the data item and pressing enter. But when the data item changes the variable break point does not trigger. You can see the data item in the KEEP window has changed but the variable breakpoint did not trigger and display a breakpoint. 

Cause

The clients load module did not match the program Symbolics(source code) stored in the PROTSYM file.  The Symbolic listing is used to navigate the load module and provide product functionally. If the load and symbolics do not match the programmer can experience unpredictable results.

 

 

Environment

Z/OS CICS

Resolution

If you compile your program between debugging sessions, you should remove your program from CA Intertest control which will delete your existing breakpoints. You then must issue a CEMT SET PROG(PROGRAM NAME) NEW to refresh the load module. Then put your program under CA Intertest control  again and set breakpoints.

The Symbolic listing is used to navigate the load module. So best practice is to make sure the load and symbolics match. CA Intertest for CICS will issue a warning message to the user when they try to set a breakpoint if the load and symbolics are not in sync. The warning message is only issued when the first breakpoint is set. The user will be displayed the following message 

CAIN8002 WARNING - Symbolic file date/time not equal to load module date/time. 

 

The user can override the warning message which is not recommended since you can have unpredictable results when testing. A mismatch listing may be used if the programmer does not have the ability to create a matching load and symbolic and they are trying to debug a production problem.