Detector collections (option 5 on the main menu), obtains Collection Activity data from DB2's Control Blocks. It does not use IFCID data. Since most accounting class data is collected within these blocks by DB2, even when DB2 accounting class 1 is not active, Detector is able to attain & display most of the data it needs.
However, certain counts & times are not written to DB2's control blocks unless the Trace classes are active. When these classes are not active, Detector will display zeros in the wait time & count fields. It won't start these classes itself. Accounting & Monitor Classes "3" are examples of this.
Detector accumulates it's statistics internally. Once an executable SQL call has completed, Detector adds it's counts, or times into a bucket. Non-executable statements (like SQL Comment), BIND, LOAD , UNLOAD & other request of this type are not included in the buckets.
However, if the SQL Trace option is enabled (Option 8 - Detector main menu), IFCID data is used. A performance trace like this is started:
03 PERFM 30 OP1 YES 015,016,017,018,021,022,053,055,058