This document provides some hints and tips if you would like to use CA InterTest for CICS to monitor DB2 applications. It also includes an JCL sample and how to resolve SQL error codes -805 and -818.
If you are using CA InterTest for CICS to monitor your DB2 applications, you likely already know the following steps from the Installation Guide:
- The CSDDB2 member on CAI.CAIOPTN provides RDO entries.
- Bind the DBRM members provided on the CAI.CAIOPTN into an InterTest DB2 plan (the recommended name is IN85PLAN), as indicated following:
The DBA must grant bind and execute authority to the plan created in task 2.
- For DB2 subsystems running in new function mode (version 8.1.0 or higher), bind IN85FIDB and IN85AID8.
- For all other DB2 subsystems, bind IN85FIDB and IN85AIDB.
For DB2 subsystems running in new function mode (version 8.1.0 or higher), ensure that the library containing the customized DSNHDECP (either SDSNEXIT or SDSNLOAD) is in the DFHRPL DD concatenation after the CICS program libraries.
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.
Here is some useful additional information on these topics.
- Although the recommended name is IN85PLAN for release 8.5, you can use another DB2 PLAN name if necessary. You need to change the name in the CSDDB2 job before submitting it:
...DEFINE DB2ENTRY(IN85DB2E) GROUP(INT85065) PLAN(IN85PLXY)...Please check the definition when your CICS is up and running via:CEDA V DB2ENTRY(IN85DB2E) GR(INT85065)It should look like (CTS 3.2 in this case):
CEDA View DB2Entry(IN85DB2E) DB2Entry : IN85DB2E Group : INT85065 Description : INTERTEST 8.5 DB2 ENTRYTHREAD SELECTION ATTRIBUTES TRansid :THREAD OPERATION ATTRIBUTES ACcountrec : None None | TXid | TAsk | Uow AUTHId : AUTHType : Userid Userid | Opid | Group | Sign | TErm | TX DRollback : Yes Yes | No PLAN : IN85PLXY
- The following sample JCL is going to BIND the InterTest PLAN for DB2 version 8.1.0 and higher, running in New Function Mode, and it grants access to the PLAN:
...JOBCARD//BIND EXEC PGM=IKJEFT01//STEPLIB DD DISP=SHR,DSN=your.DB2810.SDSNEXIT// DD DISP=SHR,DSN=your.DB2810.SDSNLOAD//DBRMLIB DD DISP=SHR,DSN=your.INTERT85.CAIOPTN//SYSPRINT DD SYSOUT=*//SYSTSPRT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSTSIN DD * DSN SYSTEM(yourDB2system) BIND PLAN (IN85PLXY) - ACQUIRE (USE) - ACTION (REPLACE) - RETAIN - EXPLAIN (YES) - ISOLATION (CS) - RELEASE (COMMIT) - VALIDATE (RUN) - MEMBER(IN85FIDB,IN85AID8,IN85AIDB) END/*//SYSIN DD *GRANT EXECUTE ON PLAN IN85PLXY TO PUBLIC;//
- See JCL sample above.
- It is required to add the DB2 SDSNLOAD and/or SDSNEXIT library to your CICS DFHRPL concatenation. Without the DB2 library in the DFHRPL, when viewing the LASTSQL via CORE=LASTSQL from an InterTest breakpoint, you will get:
CAIN0413 REQUESTED AREA WAS NOT FOUND
When viewing the LAST SQL STATEMENT from CA SymDump, you will get message:
"CASD6553 SQL STMT NOT FOUND."
You will encounter an SQL code -805 if the DB2 library is not in the DFHRPL and if member IN85AIDB is not defined in SYSTSIN - see item 2. above.
- You can check whether the XRMIO exit is running by the CA InterTest IGLU transaction. The following display is showing the expected result:
CA INTERTEST/CA SYMDUMP FOR CICS CICS GLOBAL USER EXIT LIST EXIT NAME PROGRAM ENTRY NAME ADDRESS STATUS XDUREQ IN25HOOK IN25XDUR 80065EA8 STARTEDXMEOUT IN25HOOK IN25XMEO 80065EA8 STARTEDXPCFTCH IN25HOOK IN25XPCF 80065EA8 STARTEDXPCTA IN25HOOK IN25XPCT 80065EA8 STARTEDXRMIOUT IN25RMIO IN25RMIO B8A61000 STARTED
If you still encounter an SQLCODE -805 or -818, please rebind the plan and check carefully the libraries being used at BIND as well as the DB2 and CA InterTest load libraries in your CICS JCL.
Open an issue with CA Support if you need assistance or if the problem persists.