DB2 Version 9.7 for Linux, UNIX, and Windows

Reviewing all work running on the system

When you review all the work currently running on the system, you can check for patterns that might identify the problem category or the SQL statements involved in the slowdown.

About this task

Use the Current Applications report to review all applications that are currently running on the system.

The report presents the current instantaneous state of processing of unit of work agents, and activities for each connection. The report starts with a summary section showing the number of current connections and activities and a series of summaries, such as current units of work by workload occurrence state.

Procedure

Call the routine MONREPORT.CURRENTAPPS to generate the Current Applications report.
```
call monreport.currentapps;
```
Review the "Part 1 - Summary of application processing" section.
1. Determine whether there is an abnormal proportion of current activities in a state associated with a slowdown, especially a wait state. For example, determine whether a large proportion of Event Object:Event Type records display the LOCK:ACQUIRE value. This indicates that many activities may be waiting to acquire a lock.
2. Determine which users or applications are currently running. What has been the history of slowdowns in the past for the users or applications that are currently running? Have some of these users or applications been subject to particular types of slowdowns in the past?
Optional: Rerun the report multiple times, every few seconds, and look for whether requests seem to be progressing.
- In "Part 2 - Details by connection" section, review the "Agents for this connection" section for the connections where you suspect a problem. Determine whether the REQUEST_TYPE values are changing. This indicates that old requests are not completing and new requests are not starting.
- In "Part 2 - Details by connection" section, review the "Activities for this connection" section for the connections where you suspect a problem. Determine whether the ACTIVITY_STATE values are changing over time. If they are not, this indicates a problem.
- In "Part 2 - Details by connection" section, review the "Agents for this connection" section for the connections where you suspect a problem. Determine whether the EVENT_OBJECT:EVENT_TYPE values are progressing. If they are not, this indicates a problem.