The typical DB2 Query Patroller Client requires two DB2 Query Patroller components to be installed on their desktop. The QueryEnabler and the QueryMonitor. The QueryMonitor allows the user to manage queries. The QueryEnabler is the component of DB2 Query Patroller that traps the ODBC query.
From the perspective of the ODBC 32-bit query application, QueryEnabler is an ODBC driver. From the DB2 perspective, QueryEnabler is an ODBC application. When you are configuring an ODBC query application to access a DB2 data warehouse through QueryEnabler, keep this distinction in mind to avoid confusion between the DB2 data source name and QueryEnabler data source name. Configuring QueryEnabler involves the following tasks:
| Note: | You should use a naming convention which easily distiguishes a DB2 data source name from a DB2 Query Patroller data source name. |
If a connection can not be established for the ODBC query application using the DB2 Query Patroller defined data source name, a connection using the DB2 data source name should be attempted. Once the DB2 connection is successful, try a connection to DB2 Query Patroller once again.
| Note: | Other DB2 Query Patroller client-side tools, such as QueryMonitor, use the DB2 alias to access the data warehouse. If you have specified the DB2 Query Patroller ODBC data source name with these tools, the QueryEnabler scheduling window will open when you submit a query. |