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.
DBG04006I ssid 09:43:15 FOLLOWING IFCIDS ARE USED BY REQUEST NAMED THRDACTV: