How to Install CA InterTest for CICS release 9.1 for sites that are not licensed for DB2?

Document ID : KB000009913
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

How to install CA Intertest for CICS r 9.1 S1510 using CSM for sites not licensed for DB2? The apply step fails with error messages

GIM23901E ** LINK-EDIT PROCESSING FOR SYSMOD CABA910 FAILED FOR MODULE IN64FIDB IN LMOD IN64FIDB IN THE CABALOAD LIBRARY. THE RETURN CODE (08) EXCEEDED THE ALLOWABLE VALUE. 

GIM23901E ** LINK-EDIT PROCESSING FOR SYSMOD CABA910 FAILED FOR MODULE IN64RCCI IN LMOD IN64FIDB IN THE CABALOAD LIBRARY. THE RETURN CODE (08) EXCEEDED THE ALLOWABLE VALUE. 

Instructions:

CA Intertest and Symdump CICS r 9.1 S1510 have the same problem under CSM. Both products only allow a return code of FOUR on the link edit step in the XML file that CSM uses to install the products. So when the DB2 modules are not found the link returns an RC=8 and CSM fails. 

Your only choice is to do JCL installs for both products using the PAX ESD installation files. Once the base install has been completed you can migrate the CSI to CSM and then put on the outstanding maintenance using CSM. 

You will also need to reassemble and link the CA Intertest for CICS IN25OPTS module to turn off the DB2 last SQL capture for DB2 parameter XRMIO=NO the default is yes 

This parameter is documented in the install guide in the DB2 install step. 

5. In order to support the CORE=LASTSQL command for CA InterTest for CICS, the global exit XRMIOUT is started (by default) when you start the product. 
This exit then collects DB2-related call information for every DB2 call done in the system. 
This can have significant performance implications in some DB2 shops. 
The parameter XRMIO=YES/NO IN25OPTS controls the use of this exit. 
The default is XRMIO=YES. We recommend that you carefully review this prior to using the default settings. 

The instructions for changing the CA Intertest for CICS options is outlined in the r 9.1 Install guide. 

In the next release this problem will be resolved. DB2 will have a separate FMID. So If your site does not have DB2 then you will not apply the DB2 FMID.