QueryMonitor and QueryAdministrator are Java applications that access DB2 using JDBC. Diagnostic information can be obtained from four sources:
In order to help identify problems, IBM support representatives may employ the following tracing mechanisms collectively or separately:
Typically those trace tools are launched using a Java Virtual Machine (JVM) that does not have a console (JREW.EXE). These trace tools may also be run in a JVM that has a console (JRE.EXE), in which case DB2 Query Patroller will print information to the console. You can use this information to help identify the cause of a problem.
QueryAdministrator and QueryMonitor may be launched from the command line with a -t switch, which will cause a console to appear for a Java trace, or a --tf filename switch causing the trace information to be output to a file. Note that the current directory must be set to DQP_RUNTIME\qp directory on Windows, or the DQP_RUNTIME/qp path on UNIX. To initiate a Java trace for the QueryAdministrator and have the trace information output to a file, execute the following command from the DQP_RUNTIME\qp directory on Windows, or the DQP_RUNTIME/qp path on UNIX:
QueryAdmin -tf filename
where filename is a fully qualified path and file name for the Java trace to place diagnostic information.
To initiate a Java trace for the QueryMonitor and have the trace information output to a file, execute the following command from the DQP_RUNTIME\qp directory:
QueryMonitor -tf filename
where filename is a fully qualified path and filename for the Java trace to place diagnostic information.