Starting an application trace
When you start an application trace you should begin by checking the current traces.
To start an application trace
From the EZDB2 easy menu, select the Current Traces option in the Thread Activity section.The CT view lists all current traces. The Status column indicates whether the trace is active and collecting data from Db2, or already completed but not yet purged. You will return here later to view your own trace.
>W1 =CT================DIT2=====*========24FEB2011==14:12:52====MVDB2====D====2
- Current Traces
Commands: ST (Start Application Trace) HT (History Traces) JOURNAL
Line CMDs: S (Select), W (Show), M (Modify), I (Switch)
Z (Stop), P (Purge), R (Replicate), Q (Quiesce Logging)
CM Trace ID Typ User ID Trace Title Start Date Start Status Log
-- -------- --- ------- ------------------------ ---------- Time -------- Stat
BIGELAP Sum BOLDJW1 LARGE ELAPSED TIMES 23FEB2011 11:00 Active
THRDHIST Sum BOLDJW1 THREAD HISTORY 23FEB2011 11:00 Active- Type ST on the COMMAND line to display the Start DB2 Trace Request dialog.You must be authorized to start a trace and to specify certain options. See your system administrator for the trace privileges you have. If you cannot start a trace, browse these instructions and then go to Identifying-application-problems-with-trace-displays to view an already active trace.
This section contains the following topics:
Related topic
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*