Which parameters to check when the interface from Sysview for Db2 to Detector collections are not working correctly

Products

• SYSVIEW Performance Management Option for DB2 for z/OS
• Detector for DB2 for z/OS

Issue/Introduction

Attempting to get details on an SQL accounting values and tried to use the Sysview Performance Management Option for Db2 for z/OS (IDB2) SQL Detail Screen.

It failed indicating that History Detail was not being recorded. Checked parameters in IDB2 data collector startup and there
was HIST-ACCT-DETAIL=('PDTSQL', ...) parameter, with PDTSQL option accounting values should be updated from
Xmanager/Detector for Db2 for z/OS (PDT) collection.

Resolution

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

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

2) The IDB2 data collector parameters in hlq.SOURCE(IDDCPRMS) member do not specify the correct XMANID. 

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

Second in your 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, update the SUFFIX= parameter in hlq.SOURCE(IDDCPRMS) member to point to the correct Xmanager
parameters. Or review the SETUPxx member in PTIPARM data set and double check the setup is correct.