The CA Intertest for CICS keep window does not display data items values.
Article ID: 5852
Updated On:
Products
Issue/Introduction
The client just upgrade to CA Intertest CICS release 9.1. The client reports that when single stepping through the program source code the keep window does not display the value of the data item – variable name for some working storage fields.
For example, MOVE WS-FIELDA to WS-FIELDB no values are displayed for the contents of the data items WS-FIELDA and WS-FIELDB. Instead the keep window displays message
< no keep entries available >
CA InterTest for CICS V9.1 - PROTSYM FILE STEP BEFORE BREAKPOINT
COMMAND ===>
Program= PROGRAMA Option # Stmt # Margin= 01 Search=
-------------------------------------------------------------------------------
< no keep entries available >
---------+--------------------------------------------------------------
6662 MOVE WS-FIELDA to WS-FIELDB
Environment
Cause
The clients load module does not match the program Symbolics stored in the PROTSYM file. The Symbolic listing is used to navigate the load module. If they are not identical you will have unpredictable results when debugging your program.
Resolution
If you compile your program between debugging sessions, you should remove your program from CA Intertest control which will delete your existing breakpoints. Then you must issue CICS command CEMT SET PROG(PROGRAM NAME) NEW. Then put your program under CA Intertest control and set breakpoints again.
. The Symbolic listing is used to navigate the load module. So best practice is to make sure they are insync. CA Intertest for CICS will warn the user when they try to set a breakpoint if the load and symbolics are not in sync. 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 maybe 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.
Feedback
