Programs compiled with Cobol 6.1 display <no keep entries available> at an EVALUATE statement
search cancel

Programs compiled with Cobol 6.1 display <no keep entries available> at an EVALUATE statement

book

Article ID: 71735

calendar_today

Updated On:

Products

InterTest - CICS InterTest - Batch InterTest VSE - CICS

Issue/Introduction

 When coming across an ‘EVALUATE’ statement, the value is not displaying as it was in the previous version. Both COBOL versions are using Intertest 10.
COBOL 4.2 – Good Displays
------------------------------------------------------------------------------------
_____ SFSP-CALL-TYPE | 0
---------+--------------------------------------------------------------------------
024128*****************************************************************
U 024129 EVALUATE SFSP-CALL-TYPE
U ==> WHEN '0' THRU '2'
_ 024131 PERFORM 0100-PROCESS-STMTS
_ 024132 WHEN '5'
_ 024133 PERFORM 0500-RELEASE-DETAIL-LIST
_ 024134 END-EVALUATE.
_ 024135 0010-EXIT.

COBOL 6.1
------------------------------------------------------------------------------------
< no keep entries available >
---------+--------------------------------------------------------------------------
024018*****************************************************************
 _024019 EVALUATE SFSP-CALL-TYPE
U ==> WHEN '0' THRU '2'
_ 024021 PERFORM 0100-PROCESS-STMTS
_ 024022 WHEN '5'
_ 024023 PERFORM 0500-RELEASE-DETAIL-LIST
_ 024024 END-EVALUATE.
_ 024025 0010-EXIT.

Intertest for CICS offers an option to automatically display the values of the fields referenced on a highlighted line of code in a KEEP window above the source listing display.  The option, SLBAKEEP = YES/NO, is set in IN25OPTS; SLBAKEEP=YES is the default.
Cobol programs compiled with COBOL compiler releases 5.1 and above will not show these values automatically at a COBOL EVALUATE statement      

Environment

Attempting to display value(s) of a variable in a KEEP window at an EVALUATE statement while monitoring Cobol programs compiled with compiler release 5.1 or greater with CA InterTest for CICS releases 10 or 11.  AUTOKEEP (SLBAKEEP=YES) is active.     

Resolution

Until a permanent solution is found, a workaround is to set an unconditional breakpoint at the EVALUATE and physically set the KEEP on the variable while stopped at the breakpoint.   

Additional Information

Please refer to the CA Intertest and CA Symdump Documentation wiki for information on the KEEP window and the IN25OPTS SLBAKEEP keyword.