Why does Release 9.1 of CA InterTest for CICS now require that I add the Common Component loadlib, CAVHLOAD, to the startup JCL of my CICS region?

Document ID : KB000033201
Last Modified Date : 14/02/2018
Show Technical Document Details
Question: 
 
Why does Release 9.1 of CA InterTest for CICS now require that I add the Common Component loadlib, CAVHLOAD, to the startup JCL of my CICS region?
 
With previous releases of CA InterTest for CICS and CA Symdump for CICS, we did not include the Common Component, CAILIB, in the CICS regions but only in the trace formatting started task (SYMDTRCx) concatenation.  We are wondering if, with r9.1 of  CA InterTest and Symdump why do we need to add CAVHLOAD to the CICS region's startup?  
 
Answer:
 
The CA InterTest for CICS Release 9.1 Common Component library, CAVHLOAD, contains modules needed to support the DATAMON debugging feature and needs to be present in the CICS startup JCL to enable this feature.  DATAMON is a debugging feature only available for Cobol programs that allows CA InterTest for CICS to:
  • Capture the data values for each statement in a program as it is executed
  • Provide the ability to redisplay the values as you page both forward and backward while stopped at a breakpoint   
If both CA InterTest for CICS and CA Symdump for CICS are installed in the same region, then CAVHLOAD is required in the startup JCL.   However, if CA Symdump for CICS Release 9.1 is installed as a standalone product, then CAVHLOAD is not needed.  CA Symdump for CICS uses CAVHLOAD for the Trace Formatting Region which can be run as a separate job or started task and the loadlib simply needs to be added to the STEPLIB concatenation of the job.      

Additional Information:

Refer to the CA InterTest for CICS Release 9.1 Installation Guide and the CA InterTest for CICS Release 9.1 User Guide for more detailed information pertaining to the CAVHLOAD Common Component library and the DATAMON debugging feature.