Increase of ACCT trace records following new install of Sysview for Db2
search cancel

Increase of ACCT trace records following new install of Sysview for Db2


Article ID: 12375


Updated On:


SYSVIEW Performance Management Option for DB2 for z/OS


Noted an increase of ACCT trace records in SMF data being collected due to package tracing after new install of
Sysview Performance Management Option for Db2 for z/OS (IDB2). In IDDCPRMS tracing parameters ACCTTRACE=8 is set.

Display trace command shows them being collected in its own buffer.
Does this buffer get externalized to SMF and if so, what is the trigger and can it be turn off?    

-DIS TRACE(*)                                                                 

DSNW127I  -ssid CURRENT TRACE ACTIVITY IS -                                   

TNO TYPE   CLASS        DEST QUAL IFCID                                       

01  STAT   01,03,04,05, SMF  NO                                               

01         06                                                                 

02  AUDIT  01,02,03     SMF  NO                                               

03  ACCTG  01,02,03     SMF  NO                                               

04  MON    30           OP1  NO   003,023,024,025,090,091,105,107,172         

04                                196,197,199,203,204,205,206,207,208         

04                                209,210,221,224,235,236,239,250,258         

04                                313,318,335,337,343                         

05  MON    01,02,03,05, OP1  NO                                               

05         07,08                                                              

*********END OF DISPLAY TRACE SUMMARY DATA*********                           



The IFI parameter controls the destination of the IDB2 traces.

If IFI=YES, the destination is usually OP1 for Online Performance monitor buffer number 1.

If other performance monitoring programs using the IFI are active, IDB2 will be assigned the next destination
number in sequence, so you could see destination OP2 or OP3.

Some trace data can be externalized to SMF and other cannot. Technically, READA (tracing of events in Db2)
data can and READS data cannot be written to SMF (traces reflecting real-time snapshot of subsystem and thread information).

However, to get READA data written to SMF, you need to start a trace with the appropriate trace classes and IFCIDs with DEST(SMF).                           

The monitor(Insight) does not write data to SMF nor start traces for destination of SMF.  Insight does provide support for a SAVEIFI file
which will cause the data collector to capture and write out raw trace records to the linear dataset, which can be unloaded to
SMF formatted file or used directly as input to the batch report writer.