QUALIFIER statement and parameter
The QUALIFIER statement uses qualifier values to filter the data to be included in reports that are produced by subsequent REPORT statements in the same job stream.
If default qualifiers are specified in the report, the QUALIFIER statement overrides those default qualifiers. If the qualifiers are locked in any of the requested reports, a message is printed in the Report Disposition Summary, and the default qualifiers are used for those reports.
When used as a parameter of the REPORT statement, the included or excluded qualifiers relate only to the reports that are specified in that REPORT statement. The QUALIFIER parameter overrides default qualifiers and any previously specified QUALIFIER statement.
Valid abbreviations for QUALIFIER are QUAL and Q. The following figure shows the syntax of the QUALIFIER statement and parameter.

The following tables provide details and permissible values of the keywords for the QUALIFIER statement and parameter.
The INCLUDE and EXCLUDE keywords filter the records that are selected to satisfy report requests. You can specify either INCLUDE or EXCLUDE for each qualifier type, but you cannot specify both of them. INCLUDE is the default selection.
Value | Description of value |
|---|---|
INCLUDE | Includes in the reports only records with the qualifier values that are specified in this statement Valid abbreviation: I |
EXCLUDE The EXCLUDE keyword cannot be specified with DB2 | Excludes from the reports records containing the qualifier values that are specified in this statement Valid abbreviation: E |
The type values define the type of qualifiers to be included or excluded. At least one qualifier type must be specified. Multiple values must be separated by commas (,). Wildcards are permitted (Show in following point - Using Wildcards ).
type parameter
Value | Description of value |
|---|---|
AUTHID | Authorization ID Valid abbreviations: AUTH, A |
COLLECTION | Collection ID Valid abbreviation: COLL |
CONNECTION | Connection ID Valid abbreviations: CONN, N |
CONTYP | Connection type (DRDA, CICS, DB2_CALL, DB2_UTILITY, DLI, IMS_ATT_BMP, IMS_ATT_MPP, IMS_CTL, IMS_TRAN_BMP, RRSAF_ATTACH, RMT_PRIV_PRO, TSO) Valid abbreviation: CONT |
CORRID | Correlation ID Valid abbreviations: CORR, C |
DB2 1 | DB2 SSID Valid abbreviation: U |
ENDUNAME | End user name Valid abbreviation: EUN |
ENDWSNAME | End workstation name Valid abbreviations: ENDWSN, EWN, EUW |
ENDTNAME | End transaction name Valid abbreviation: ETN |
LLOCATION | Local location Valid abbreviations: LLOC, KL |
OPERATOR | Original operator ID Valid abbreviations: OPID, OPER, O |
PACKAGE | Package or DBRM name Valid abbreviations: PROGRAM, PROG, G, DBRM |
PLAN | Plan name Valid abbreviations: P |
RLOCATION | Requesting location Valid abbreviations: RLOC, KR |
ROLE | Role name Valid abbreviation: no abbreviation |
1 The EXCLUDE keyword cannot be specified with DB2.
Although you are not prevented from specifying any qualifier with any report, not all qualifiers are valid for all reports. Be careful to choose qualifiers that are appropriate to the data that you are collecting.
The following table lists the reports that have been designed specifically for Data Collector reporting and indicates which qualifiers are valid with each report.
Valid qualifiers for Data Collector reporting
Report | Description | Valid Qualifiers |
|---|---|---|
BACCPKSR | Thread accounting package summary |
|
BACCTDR | Accounting detail trace long |
|
BACCTLT | Accounting detail trace long |
|
BACCTSR | Accounting summary short |
|
BACCTST | Accounting detail trace short |
|
BAUDTAUT | DB2 authorization failures |
|
BDB2UTIL | DB2 utility events |
|
BDEADLCK | DB2 deadlock report |
|
BIOSUM | I/O active summary report |
|
BIOSUMAR | I/O summary detail archive log report |
|
BIOSUMBP | I/O summary detail buffer pool report |
|
BIOSUMBS | I/O summary detail BSDS report |
|
BIOSUMED | I/O summary detail BSDS report |
|
BIOSUMLG | I/O summary detail active log report |
|
BIOSUMXI | I/O summary detail cross invalidation activity report |
|
BLKSUMDT | Lock summary detail report |
|
BLKSUMLO | Lock summary lockout report |
|
BLKSUMSU | Lock summary suspensions report |
|
BLKTRCDT | Lock trace event detail report |
|
BLKTRCLO | Lock trace lockout report |
|
BLKTRCSU | Lock trace suspensions report |
|
BRIDFAIL (PTF BQU2045 applied) | RID failures report |
|
BRIDLIST | RID list failures report |
|
BSQLIX | SQL create thread index report |
|
BSQLLT | SQL long trace report |
|
BSQSUMP | Summary SQL report by PGM/PKG |
|
BSQSUMPW | Summary SQL report by PGM/PKG with workloads |
|
BSQTRCCC | SQL compatibility exception trace by event report |
|
BSQTRCP | Thread SQL trace summary report by PGM/PKG |
|
BSQTRCPW | Thread SQL trace summary report by PGM/PKG with workloads |
|
BSQTRCS | Thread SQL trace summary report by PGM/PKG and statement number |
|
BSQTRCSW | Thread SQL trace summary report by PGM/PKG and statement number with workloads |
|
BSQTRCT | SQL summary trace report by occurrence |
|
BSQTRCTW | SQL summary trace report by occurrence with workloads |
|
BSTATDI | DB2 statistics IFCID tracing detail |
|
BSTATDR | DB2 statistics detail |
|
BSTATLT | DB2 statistics trace long |
|
BSTATSTX | Virtual storage status |
|
BSTATSUM | Virtual storage status summary |
|
BTHACDTL | Accounting thread detail—long report (BTHACDTL) |
|
BTHAUDIT | Audit event history |
|
BTHDADTL | Thread detail by AUTHID |
|
BTHDASUM | Thread summary by interval |
|
BTIMEOUT | DB2 timeout report |
|
THSQLDYN | Dynamic SQL Miniplan by period |
|
THSQLDYS | Dynamic SQL Miniplan summary |
|
Using Wildcards
Only an asterisk (*) and exclamation mark (!) are valid wildcards.
An asterisk, when used alone, matches all values for the identifier. All characters following an asterisk are ignored.
An asterisk, when used at the end of a character string matches all identifiers beginning with that character string.
An asterisk, where components of a qualifier are separated by a period (.), can be used within each component.
The exclamation point is used to replace a single character at any position in a string. You cannot use this wildcard in the text hash or data sharing group qualifier.
Related topic