-DISPLAY TRACE (*) not all IFCIDs started by Sysview for Db2 were in the output
Article ID: 142392
Updated On:
Products
Issue/Introduction
Replacing Omegamon with Sysview Performance Management Option for Db2 for z/OS (IDB2) and need to have the same level of reporting on as Omegamon.
With a -DISPLAY TRACE (*) command see there are IFCIDs records that are required to create some reports that are not in the output.
DSNW127I xxx CURRENT TRACE ACTIVITY IS -
TNO TYPE CLASS DEST QUAL IFCID
01 STAT 01,03,04,05, SMF NO
01 06
02 ACCTG 01,02 SMF NO
03 MON 30 OP1 NO 003,006,007,008,009,020,023,024,025
03 044,045,053,058,059,060,061,062,063
03 064,065,066,073,090,091,095,096,105
03 172,177,196,197,199,203,204,205,206
03 207,208,209,210,219,220,221,224,235
03 236,239,250,258,313,316,318,335,337
03 343,360,369,370,376,389,400,401,402
03 503
04 MON 01,02,03,05, OP1 NO
04 07,08,09,10
For example, looking for trace records IFCID 106, 202, and 230 which will help to capture the historical ZPARM values but the values are not in the output.
Resolution
The MONITOR TRACE will only collect asynchronous IFCIDs that are placed by Db2 into the READA buffer. Records that can only be obtained
synchronously by the IFI READS function will not be in the list.
Here is a link the the list of READS trace records:
https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/perf/src/tpc/db2z_synchronousdatareadsifi.html
Note there was the following in the IDB2 data collector output:
...
DBG04006I 13:41:53 FOLLOWING IFCIDS ARE USED BY REQUEST NAMED HSPARMS :
106,1006
DBG04005I 13:41:53 START SUCCESSFUL FOR REQUEST HSPARMS .
DBG04006I 13:41:53 FOLLOWING IFCIDS ARE USED BY REQUEST NAMED HSPRMBP :
202
DBG04005I 13:41:53 START SUCCESSFUL FOR REQUEST HSPRMBP .
DBG04006I 13:41:53 FOLLOWING IFCIDS ARE USED BY REQUEST NAMED HSPRGBP :
230
and you can display the 'DB2 Subsystem Parameters History' panel from Main Menu:
2 System History
Select an interval.
6 More...
3 System Parameters (106, 202, 230)
Feedback
