Which parameters to check when the interface from CA SYSVIEW for DB2 to Xmanager/Detector collections is not working correctly?

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

A user was attempting to get details on an SQL accounting values and tried to use the SQL Detail Screen. It failed indicating that History Detail was not being recorded. Checked parameters in CA SYSVIEW for DB2 Data collector startup and there was HIST-ACCT-DETAIL=('PDTSQL', ...) parameter, with PDTSQL option accounting values should be updated from Xmanager/Detector collection.

Instructions:

Not getting data from Xmanager/Detector collection has two likely causes:

1) The Detector collection for that DB2 subsystem is not active. 

2) The CA SYSVIEW for DB2 Data Collector parameters in *.SOURCE(IDDCPRMS) member do not specify the correct XMANID. 

First double check the Detector collection was started for the DB2 subsystem.

Second in your CA SYSVIEW for DB2 Data Collector output locate the following messages.

DBG02177I ... INVOKING PARMLIB READER USING "EP=PTTDUMMY,SUFFIX=xx       "
DBG02179I ... PARMLIB OPTIONS USED: PTISYSxx, SETUPxx, PLANSxx, XMID=nnnnn

If this is not correct, you should update your SUFFIX= parameter in *.SOURCE(IDDCPRMS) member to point to the correct Xmanager parameters. Or review the SETUPxx member in PTIPARM data set and double check the set up is correct.