For the DB2® report, CMF record
selection is the same as for all CMF Performance reports, with an
additional criterion:
- LISTZERO. List CMF performance class records that do not
involve DB2 activity (DB2REQCT=0)
when they are part of a network unit-of-work that involves some DB2 activity.
DB2 accounting record selection
is based on:
- CMFONLY. Suppress DB2 record
processing.
- SMFSTART, SMFSTOP. Like the CMF performance records, filter
the DB2 Accounting records based
on the SMF time stamp.
- SELECT(PERFORMANCE. INCLUDE or EXCLUDE DB2 Accounting records based on whether the DB2 thread Begin-End times are within
the specified FROM-TO report intervals. Also you can filter the DB2 Accounting records based on
UOWID field values.
- APPLID. Select by CICS® generic
APPLID.
- SSID. Select by DB2 Subsystem
ID.
Note: DB2 end time can be after
CMF stop time if thread protection is in place. Consequently, if
you specify SMFSTOP when protected threads are in use, it is possible
that DB2 Accounting records
are excluded that relate to CMF records that are included. In normal
circumstances, 5 minutes (the initial DB2 thread
PURGECYCLE delay after CICS startup)
is expected to be the longest period an inactive DB2 thread is present before it is terminated
by a PURGECYCLE. To allow for this, you should specify the SMFSTOP
time at least 5 minutes after the ‘required stop time' specified
in the FROM/TO report interval in the SELECT statement.