IBM DB2 Query Patroller Administration Guide

Windows Specific DB2 Profile Variables

The DB2 Query Patroller system is integrated with the operating system features of Windows and runs as a service. For this reason, the DB2 Query Patroller system on Windows has a slightly different implementation. The following profile variables are specific to DB2 Query Patroller running on a Windows operating system, and are set on the server.

DQP_MAPI_PROFILE

The DQP_MAPI_PROFILE environment variable is set to the name of the mail profile that will be used when logging on to MAPI. The mail profile specifies the mail service that will be used to send e-mail notification. In the address book for the mail profile, list the addresses that mail should be sent to. The default address for mail notification must be set to iwm. Setting the DQP_MAPI_PROFILE variable is required for notification to work. If DQP_MAPI_PROFILE is not set, notification will be written to the DB2 Query Patroller log file. For more information about DB2 Query Patroller e-mail notification, see DB2 Query Patroller E-Mail Notification.

DQP_MAPI_PASSWORD

If the DQP_MAPI_PASSWORD profile variable is set, the password provided will be used to logon to the MAPI subsystem. It should not be necessary to set this variable when using Microsoft Exchange or Microsoft Internet Mail. For more information about DB2 Query Patroller e-mail notification, see DB2 Query Patroller E-Mail Notification.

DQP_MAIL_ACCOUNT

If the DQP_MAIL_ACCOUNT profile variable is set, DB2 Query Patroller will attempt to send mail under the account you specify. Use the following format to specify account information: username, password. Setting the DQP_MAIL_ACCOUNT environment variable is not required for Microsoft Exchange or Microsoft Internet Mail. For more information about DB2 Query Patroller e-mail notification, see DB2 Query Patroller E-Mail Notification.

DQP_STARTUP

The DQP_STARTUP profile variable must be set on each node. It can be set to all, server, or agent. The default setting, all, specifies that both the server and agent processes are to be started. The server option starts only the server processes. The agent option starts only the agent processes. Only one node per system should be started with the all or server option.