Replace IBM DB2 Omegamon with Sysview for Db2 setup of traces
search cancel

Replace IBM DB2 Omegamon with Sysview for Db2 setup of traces


Article ID: 138390


Updated On:


SYSVIEW Performance Management Option for DB2 for z/OS


Replace Omegamon with Sysview Performance Management Option for Db2 for z/OS (IDB2) and need to have the same
level of reporting on as it was for Omegamon. See the traces that were ON as follows for Omegamon:

 04  AUDIT 01           OP1 NO                          
 05  MON   30           OP1 NO  031                    
 06  STAT  04           OP1 NO                          
 07  STAT  03           OP1 NO                          
 08  PERFM  30          OP1  NO  090                    
 09  ACCTG  01,02,03,07  OP2 NO                          
 10  MON   01           OP2 NO                          
 11  PERFM 31           OP2 NO   022,063,105,107,172,196

How to start these traces using IDB2 as used by Omegamon?


IDB2 sets up the traces a little bit differently from Omegamon. It appears that Omegamon starts a STATS trace and a PERFM trace.
We do not. The STATS trace is designed to get IFCID 1,2, and 225. We do not explicitly start this trace. The SYSPARM HISTORY-STATS-TIME controls
how often we obtain these records via the IFI READS function.

For the trace records specified in the Omegamon PERFM trace, they will be collected by our MON trace. You should simply verify that the
IFCID numbers that are present in the Omegamon PERFM trace are present in the IDB2 MON trace. 

To start the ACCTG 01,02,03,07 you have to specify ACCTTRACE=7, then traces 01,02,03 will also start. The best option is to specify ACCTTRACE=8
as we sent as the default value in sample hlq.SOURCE(IDDCPRMS) member. 

To understand how the list of IFCIDs is built, you must remember that we read all of the requests at startup, and when parsing the requests we
determine which IFCID is required to satisfy the request. If there is some IFCID that is either 

a) in their list but is not wanted, or 
b) not in their list, but wanted, 
it is simply a matter of finding out which request(s) control that particular IFCID and activating/deactivating them as required. 


The DBGPRINT file contains a line of output for each request that was started, and which IFCIDs it uses.