It was noted that not all SQL transactions are being recorded in Detector for Db2 for z/OS (PDT).
The scenarios noted are queries from SPUFI and DSNTEP4 when attempting to view this
information within PDT for View By ==> K for (K)eys / Key ==> U *-User.
Verify the PDT Collection Profile in use option View Group Type ==> K
for (K)eys has the proper connection type enabled. In this specific
instance both TSO and Batch would need to be enabled:
Display of data enabled for the following connection types
TSO ==> Y Batch ==> N CICS ==> N
DL/I Batch ==> N IMS ==> N Distributed ==> N
Please note:
Enabling additional keys collection can significantly increase the main
storage requirements for active collections and the DASD requirements for
the externalized historical activity. We recommend limiting additional keys collection
to one or two views and connect types that you consider to be the most important.