A CA Earl SQL request is terminating with error CALR873E and SQLCODE -818 after upgrade to CA Common Services r11 or above. Why? How do we resolve this?

Products

• Earl

Issue/Introduction

A CA Earl SQL request is terminating with error CALR873E and SQLCODE -818 after upgrade to CA Common Services r11. Why? How do we resolve this?

Environment

Release: EARL..00200-6.1-Earl
Component:

Resolution

After an upgrade to CA Common Services r11 or above, a CA Earl SQL request is terminating with CALR873E and SQLCODE -818.

Solution:

After upgrading to CA Common Services, a CA Earl SQL request received the following set of errors:

 SQL FIKA     SQL SELECT FAILED
 SQL FLAG:- SQLCODE   hex: FFFFFCCE, dec:      -818
 SQL FIKA     SQLERRM IS: 143E08280C4F6DFC 168FCDD412D0CE24 CAISSQL3
 SQL FIKA     DISCONNECT DB2,SQLDS SQL
 CALR873E FAILURE IN SEND TO SQL

The above errors indicate that the CA Common Services (CCS) SQI (SQL Interface) has not been completely installed and BINDed. The DB2 DBRM modules CAISSQL2, CAISSQL3, and CAISSQL9 are installed via CCS r11 FMID CAG3000 (CA Viewpoint). The necessary BINDs are done via CCS SAMPJCL member SP23BIND.

Note, with CCS r11 or above, a number of previously separate components were combined into one. The Viewpoint component now provides release 3.0 via a new FMID (CAG3000), and is a combination of the following components at previous CA Common Services levels: Viewpoint (CWC2000), SQI (CSP2300), CBASE Mapper CF62300), CBASE Common (CIF2300), CBASEX (CAG2300), CBASE Template (CTB2300), CBASE Help (CBS2300).

Prior to CCS390 r11, the CAISSQLx modules were found with SQI (FMID CSP2300).

FYI, CA Earl uses CAISSQL3 and CAISSQL9 and does not use CAISSQL9.