Includes or excludes data associated with specific OMEGAMON XE for DB2 PE identifiers.
For
details, see INCLUDE and EXCLUDE subcommand options, which
lists other allowed identifiers with this command and subcommand combination,
and OMEGAMON XE for DB2 PE identifiers.
Special
considerations for DDF trace data:
For single DB2 systems
the PLANNAME identifier can be used to filter data and order reports
in a meaningful manner.
When DB2 is
acting as a DDF server, the PLANNAME identifier has a constant value
of DISTSERV for requesters using DRDA®.
For OM XE for DB2 PE Accounting data, DISTSERV is replaced
with the first eight characters of the name of the client application
so that filtering on PLANNAME, is meaningful.
Because this
replacement is done by the batch accounting component, you need to
consider the impact when using the INCLUDE and EXCLUDE subcommand
options with other commands. This can cause unexpected results, for
example when GLOBAL INCLUDE is used.
The following example
shows how PLANNAME can be used in Accounting reports with DDF data
to include data from a PLANNAME with the value CAPPNAME:
GLOBAL
INCLUDE (PLANNAME(DISTSERV)) // to include all DDF data
ACCOUNTING
REDUCE
INCLUDE (PLANNAME(CAPPNAME))
REPORT
INCLUDE (PLANNAME(CAPPNAME))
·
·
·
When GLOBAL INCLUDE is omitted, a report is produced,
containing replaced names.
When REDUCE INCLUDE is omitted,
no report is produced. This is because REDUCE is called implicitly
by REPORT by using the GLOBAL filter. As accounting works with the
replaced values, DISTSERV is not found in the input records.
When
INCLUDE is omitted from REPORT, there is no data to report. The GLOBAL
filter is used as default, explicitly including DISTSERV. As accounting
works with the replaced values, DISTSERV is not found in the input
records.
If the use of PLANNAME as a filter causes unexpected
results across reports, use REQLOC, CONNTYPE and THREADTYPE, which
are interpreted in exactly the same way in all OM XE for DB2 PE
reports.
