Problems detected in exception event processing

If you detect a problem using the online exception event processing and the Online Monitor panels do not provide sufficient information to determine the cause, collect the appropriate trace data to produce Locking reports, I/O Activity reports, Audit reports, or Record Trace reports. This section describes how to proceed with specific exception events.

Deadlock or Timeout: If deadlocks or timeouts occur too often, generate a Lockout report to see which applications and objects are affected. Having identified the objects and applications causing the deadlocks or timeouts, use EXPLAIN to understand the locking behavior of the SQL statements or consider reorganizing the database.
EDM Pool Full: First check online or batch statistics to obtain more information about the EDM Pool situation. More details are provided in the I/O Activity EDM Pool report.
Authorization Failure: If authorization failures occur too often, generate an Audit authorization failure report for details.
Thread Commit Indoubt: Run a Record trace on the Statistics Class 4 IFCIDs to see details of communication problems. These are likely to be either VTAM® or DB2® internal problems.
Coupling Facility Rebuild: Use the COLLECT command to automatically start tracing IFCID 268 (CF rebuild end) when a coupling facility rebuild starts, and run a Record trace for this IFCID. You can get more details about coupling facility behavior from RMF reports.