TMON for DB2 Release Notes Version 1.5

Transcription

1 TMON for DB2 Release Notes Version 1.5

2 TMON for DB2 Release Notes Version 1.5 Copyright Notice Copyright IBM Corporation 2001 All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose. U.S. Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Trademarks IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, Cross-Site, DB2, MVS, NetView, OS/390, and TME are trademarks or registered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries, or both. Lotus is a registered trademark of Lotus Development Corporation. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Landmark Systems Corporation, PerformanceWorks, and The Monitor are registered trademarks of Landmark Systems Corporation. Other company, product, and service names may be trademarks or service marks of others. Notices References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York , U.S.A. Copyright International Business Machines Corporation All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 2 Version 1.5

3 Table of Contents OVERVIEW OF TMON FOR DB SOFTWARE REQUIREMENTS... 4 OVERVIEW OF TBSM PROCESSING... 5 PROCESSING EVENTS... 5 EVENT FLOW... 6 CUSTOMIZATION... 9 CUSTOMIZING TMON FOR DB CUSTOMIZING NETVIEW Members Used In This Customization Customization You Should Already Have Done EVENT PROCESSING SCENARIO TROUBLESHOOTING APPENDIX A. TBSM EXCEPTIONS CAUSED BY TMON FOR DB DB2 SUBSYSTEM BUFFER POOL EDM POOL LOGS Tivoli Business Systems Manager TMON for DB2 Release Notes 3

4 Overview of TMON for DB2 The Monitor for DB2 (TMON for DB2) is a DB2 performance monitoring system from LandMark Systems Corporation. TMON for DB2 is a component of the LandMark PerformanceWorks for MVS and OS/390 product line. This document describes how to integrate TMON for DB2 with Tivoli Business Systems Manager (TBSM), so that TMON for DB2 default exceptions are translated into exception events for the relevant DB2 objects in TBSM. Integrating TMON for DB2 with TBSM involves capturing TMON for DB2 default exceptions, translating these exceptions into events understood by TBSM, then passing the events to TBSM. (Only the default exceptions supplied with TMON for DB2 are captured; not any site-specific exceptions that you might have defined.) This process is described in detail in the next section. Note: This document assumes that you have already integrated your DB2 subsystems with TBSM, as described in the TBSM DB2 and DB2 PM Release Notes. Integrating TMON for DB2 with TBSM builds on this existing DB2 integration, using TMON for DB2 to provide additional monitoring. For more information about the existing DB2 integration assumed by this document, see the TBSM DB2 and DB2 PM Release Notes. Software Requirements The Monitor for DB2 Version 3.2 Rework Level or higher. Tivoli Business Systems Manager Version 1.5. Tivoli NetView for OS/390 Version 1.2 or higher. OS/390 Version 1.3 or higher. 4 Version 1.5

5 Overview of TBSM Processing TBSM operates through these key processes: Initial discovery Before you can use TBSM to monitor your systems, you need to register the systems as objects in the (Windows NT-based) TBSM Object database. This involves running batch jobs that detect the configuration of your systems and register the appropriate objects in the TBSM Object database. This process is known as initial discovery. This document assumes that you have already performed DB2 initial discovery, as described in the TBSM DB2 and DB2 PM Release Notes. Rediscovery After the initial discovery process, TBSM uses incoming events from monitored systems to identify changes in the configuration of those systems. This process is known as rediscovery. TMON for DB2 events are not used for rediscovery. For more information about DB2 re-discovery, see the TBSM DB2 and DB2 PM Release Notes. Event processing Involves capturing specific events and routing them to TBSM. TBSM uses these events to update the TBSM Object database, resulting in updates to the TBSM graphical user interface. Event processing for TMON for DB2 is described below to allow you to understand the overall sequence as well as key facilities that are used. Before the event processing described below can occur, you need to perform some minor customization steps. These steps are briefly described below; for detailed instructions, see Customization on page 9. Processing Events To allow TBSM to capture TMON for DB2 default exceptions, you need to customize TMON for DB2 to use the WTO (Write to Operator) macro to direct default exception messages to the MVS system console. NetView uses an automation table to detect when specific messages appear on the console, and take appropriate action. To allow NetView to detect and act on default exceptions from TMON for DB2, you need to customize the NetView automation table to capture these messages and run a REXX exec. The REXX exec translates the messages into TBSM events, then routes the events to TBSM. Tivoli Business Systems Manager TMON for DB2 Release Notes 5

6 Event Flow The following diagram shows how NetView captures WTO messages for TMON for DB2 default exceptions, and routes them to TBSM. DB2 OS/390 NT Server monitored by TMON for DB2 default exceptions WTO messages 1 Tivoli Business Systems Manager Source/390 Object Server 5 LU6.2 or TCP/IP SNA Server Event Server 6 System console captured by NetView Automation table uses autotask to run REXX exec 2 3 Dataspace Object Pump PPI receiver NetView PPI 4 SQL Database Server Object database Propagation Server PPI sender defines CGLOBAL variables used by REXX exec on 15-minute timer PPI sender 4 exception events resolution events Application Server Graphical user interface 7 8 Workstation (The Windows NT-based TBSM History Server is deliberately omitted from this diagram, because it does not affect event flow.) 6 Version 1.5

7 Here is a detailed description of the event flow: 1. A DB2 event occurs that matches the criteria of a TMON for DB2 default exception. TMON for DB2 uses the WTO macro to issue a message to the MVS system console. (TMON for DB2 also displays the exception on the TMON for DB2 Exception Monitor Display screen.) 2. The NetView automation table recognizes the TMON for DB2 default exception WTO message ID, and passes the message to a NetView autotask that runs a REXX exec. TMON for DB2 default exception WTO message IDs begin with the characters TMDB. For a complete list of the default exceptions captured by NetView, see Appendix A. TBSM Exceptions Caused by TMON for DB2 on page The REXX exec translates the TMON for DB2 default exception into a TBSM exception event. This translation is described in the box below. Translating TMON for DB2 default exceptions into TBSM exception events Two types of TBSM event are visible on the TBSM graphical user interface: exceptions and messages. Exception events are transient and typically reflect a condition of duress, whereas message events reflect the current state of an object (such as starting, active or inactive). Note: Outside of TBSM, message is often used as a general descriptive term; for example, TMON for DB2 issues WTO messages. However, within TBSM, the term message refers specifically to a type of TBSM event. The REXX exec translates TMON for DB2 default exceptions into TBSM exception events. The TBSM exception event name is the same as the WTO message ID. Exception alert state and priority TBSM exceptions have an alert state and a priority. For each object type in TBSM, there is a table listing the exceptions that the object type can receive, and the alert state and priority of each exception. You can either use the Tivoli-supplied default values for alert state and priority, or you can change some or all of these values to reflect the importance of exceptions to your particular enterprise. For details on the default alert state and priority of the exceptions caused by TMON for DB2, see Appendix A. TBSM Exceptions Caused by TMON for DB2 on page 15. After translating the TMON for DB2 default exception into a TBSM exception event, the REXX exec uses the NetView program-to-program interface (PPI) to send the exception event to the TBSM Object Pump. The REXX exec also stores the WTO message ID and time in NetView CGLOBAL variables. These variables are used later by another, timed REXX exec to create a resolution event for the exception (as described in the next step). 4. The NetView customization described in the TBSM DB2 and DB2 PM Release Notes (which this document assumes that you have already performed) includes using the automation table to set up various REXX execs to run every 15-minutes. One of these timed REXX execs looks for NetView CGLOBAL variables containing information about TMON for DB2 exceptions. If any such variables exist, and they indicate that the exception event occurred at least 15 minutes ago, then the timed REXX exec sends a resolution event for that exception to the TBSM Source/390 Object Pump. Tivoli Business Systems Manager TMON for DB2 Release Notes 7

8 Resolution events are another type of TBSM event. Resolution events occur after an exception, and indicate that the condition that caused the exception no longer exists. Resolution events are not directly visible on the TBSM graphical user interface: when TBSM receives a resolution event, it removes the matching (visible) exception. The timed REXX exec runs every 15 minutes, and only sends resolution events for exception events that occurred at least 15 minutes ago. Therefore, a TMON for DB2 exception event remains on the TBSM graphical user interface for between 15 minutes minimum to 30 minutes maximum (approximately), depending on when the exception event occurred in the 15-minute cycle of the timed REXX exec. However, the REXX exec does not send a resolution event for the TMDB EDMPOOL FAILURES > 0 exception: the TBSM user must manually resolve this exception event. 5. The TBSM Source/390 Object Pump stores the exception or resolution event in the TBSM Source/390 Dataspace. 6. The TBSM Source/390 Object Server retrieves the event from the TBSM Source/390 Dataspace, and forwards it to TBSM on Windows NT; either via an LU 6.2 session to the TBSM SNA Server, or via a TCP/IP session directly to the TBSM Event Server. 7. The TBSM Event Server updates the appropriate DB2 object in the TBSM Object database (managed by the TBSM SQL Database Server). The event might also be propagated by the TBSM Propagation Server to parent objects in the TBSM object model hierarchy, involving further updates to the TBSM Object database. 8. The TBSM Application Server forwards the event to the TBSM graphical user interface (on a Windows NT workstation). 9. Finally, on the TBSM graphical user interface, either: a new exception appears (on the Attributes tab of the property sheet for the appropriate DB2 object), or an old exception is removed (by a resolution event). 8 Version 1.5

9 Customization To integrate TMON for DB2 with TBSM, you need to do some minor customization of TMON for DB2 and NetView. These customization steps are described below. Customizing TMON for DB2 For each of the TMON for DB2 default exceptions that you want captured and passed to TBSM, you need to: Activate the relevant exception set Insert the DB2 name as the first token in the exception message text Specify WTO (write to operator) as an action to be taken when the exception is detected Autostart monitoring for the exception Follow this procedure (for details, see the TMON for DB2 Reference Manual): 1. Go to the TMON for DB2 Exception Definitions screen (option 3.1). 2. Select the exception record type, then the particular exception set. 3. Enter act to activate the exception set. 4. Enter e to edit the exception set. The Exception Definition Detail screen appears. 5. Cursor-select the EDIT EXCEPTION TEXT SUBSTITUTION FIELDS command. The Exception Text Substitution Data screen appears. 6. Add DB2 name as the first text substitution field. 7. Press PF3 to return to the Exception Definition Detail screen. 8. Cursor-select the SPECIFY ACTIONS TAKEN WHEN EXCEPTION DETECTED command. The Exception Action Definition screen appears. 9. Under ACTIONS TAKEN WHEN EXCEPTION IS DETECTED, specify: BEGIN AT STOP AFTER WTO EXCEPTION TEXT MESSAGE TO SYSTEM LOG : Press PF3 to return to the Exception Definitions screen. Tivoli Business Systems Manager TMON for DB2 Release Notes 9

10 11. In the EXCEPTION TEXT field, insert (a string of four at signs), followed by a space, in front of the existing text. This causes TMON for DB2 to insert the DB2 subsystem name as the first token in the text of the WTO message, enabling TBSM to route the event to the appropriate TBSM DB2 object. 12. In the AUTOSTART field, enter Y. Note: Do not change the value of the TEXT MESSAGE # field. (The NetView automation table detects TMON for DB2 exceptions based on this TMDBnnnnns value; if you change this value, then the exception will either not be passed to TBSM or, potentially, be interpreted as a different type of event.) 10 Version 1.5

11 Customizing NetView Customizing NetView involves a single step. Insert the following statement in your NetView automation table: %INCLUDE IHSBTMAT Members Used In This Customization The following table describes the members used in this NetView customization: Member IHSBTMAT IHSBTMON Description Contains NetView automation table statements that: Capture TMON for DB2 default exceptions, then Use the IHSBAT00 autotask (for details, see Customization You Should Already Have Done ) to run the IHSBTMON REXX exec (described below). REXX exec that: Translates TMON for DB2 default exception WTO messages into TBSM exception events Sends the exception events to TBSM Defines NetView CGLOBAL variables used by the IHSBTMCL REXX exec (described below) IHSBTMCL Timed REXX exec that sends a resolution event to TBSM, minutes after each TMON for DB2 exception event (excluding only the TMDB01123 EDMPOOL FAILURES > 0 exception event, which the TBSM user must manually resolve). The IHSBTMCL REXX exec looks for NetView CGLOBAL variables containing information about TMON for DB2 default exceptions. (These variables are defined by the IHSBTMON REXX exec, described above.) If any such variables exist, and they indicate that the exception event occurred at least 15 minutes ago, then IHSBTMCL sends a resolution event for that exception to the TBSM Source/390 Object Pump. Supplied in TBSM data set SGTMSAMP SGTMEXEC Tivoli Business Systems Manager TMON for DB2 Release Notes 11

12 Customization You Should Already Have Done This customization of NetView relies on the assumption that you have already performed the steps described in the TBSM DB2 and DB2 PM Release Notes. In particular, you should have: Concatenated this TBSM data set To this NetView DD statement SGTMEXEC DSICLD SGTMSAMP DSIPARM This allows NetView to find the members used in this customization. Inserted the following statement in the DSIOPF NetView member: %INCLUDE IHSBOPR The IHSBOPR member defines the IHSBAT00 autotask that the IHSBMTAT automation table member uses to process TMON for DB2 events. This is the same autotask that is used to process some DB2 and DB2 PM events. 12 Version 1.5

13 Event Processing Scenario The following scenario assumes that you have performed the customization steps described earlier in this document. 1. A TMON for DB2 default exception causes the following WTO message: TMDB01103C - DB6S BP4K00 DM CRITICAL REACHED 46 TIMES 2. The NetView automation table captures the message, and invokes the IHSBTMON REXX exec. The REXX exec translates the TMDB01103C message into an exception event for the DB6S DB2 subsystem object in TBSM. 3. The IHSBTMON REXX exec routes the exception event to the DB6S DB2 subsystem object in TBSM. 4. In the TBSM graphical user interface, a TMDB01103C exception appears on the Attributes tab of the property sheet for the DB6S DB2 subsystem object. Tivoli Business Systems Manager TMON for DB2 Release Notes 13

14 Troubleshooting For problems with TMON for DB2, see the TMON for DB2 product documentation. Otherwise, see the Troubleshooting section in the TBSM DB2 and DB2 PM Release Notes. 14 Version 1.5

15 Appendix A. TBSM Exceptions Caused by TMON for DB2 This appendix lists the TBSM exception types that can be caused by TMON for DB2 default exceptions. The exception types are listed under the TBSM object types that can receive the exceptions: DB2 subsystems Buffer pools EDM pools Logs The tables in this appendix contain the following columns: This column Name Description Priority Alert state Contains this information The exception name, as displayed on the Attributes tab of the TBSM object property sheet. The exception name matches the TMON for DB2 default exception WTO message ID. The exception description, as displayed on the TBSM object type property sheet. The Tivoli-supplied default priority of the exception, as displayed on the Attributes tab of the TBSM object property sheet. The Tivoli-supplied default alert state of the exception, as displayed on the Attributes tab of the TBSM object property sheet. Note: minutes after each TMON for DB2 exception event, the IHSBTMCL timed REXX exec sends a matching resolution event to TBSM (removing the earlier exception event). However, the REXX exec does not send a resolution event for the TMDB ( EDMPOOL FAILURES > 0 ) exception: the TBSM user must manually resolve this exception event. Changing the priority and alert state from the Tivoli-supplied default values For each object type in TBSM, there is a table listing the exceptions that the object type can receive, with priority and alert state values for each exception. You can either use the Tivoli-supplied defaults (listed in this appendix), or you can change these values to reflect the importance of exceptions to your particular enterprise. For details on changing the priority and alert state of exceptions, see the TBSM Administration Guide. Tivoli Business Systems Manager TMON for DB2 Release Notes 15

16 DB2 Subsystem Name Description Priority Alert-state TMDB00001I CONN=x, PLAN=x, CPUTM=x TMDB00001I CONN=x, PLAN=x, ELAPS=x TMDB00001I CONN=x, PLAN=x, READ I/O=x TMDB00001I INACTIVE THREAD.CORRID=x TMDB01001W ABORTS IN INTERVAL TMDB01002I AUTHORIZATION FAILURES > 0 TMDB01003W DDL ON AUDITED OBJECT > 0 TMDB01004W THREAD DEADLOCKS > 0 TMDB01005I DISPLAY THREAD COMMANDS > 5 TMDB01006W THREADS INDOUBT > 0 High Red TMDB01007W THREAD LOCK ESCALATIONS TO SHARE > 10 TMDB01008W THREAD LOCK ESCALATION TO EXCLUSIVE > 5 TMDB01009I START DATABASE COMMANDS > 0 TMDB01010I STOP DATABASE COMMANDS > 0 TMDB01011W CREATE THREAD WAITS > 5 TMDB01012W THREAD TIMEOUTS > 10 TMDB01117W CHECKPOINTS = x PER MINUTE TMDB01118W DB2 DBM1 ADDR SPACE CPU TIME = x TMDB01119W DB2 DIST ADDR SPACE CPU TIME = x TMDB01120W DB2 IRLM ADDR SPACE CPU TIME = x TMDB01121W DB2 MSTR ADDRESS SPACE CPU TIME = x TMDB02001W THREAD ABORTED TMDB02005W THREAD WITH DB2 ELAPSED TIME OF x TMDB02006C DEADLOCK FOR AUTH ID XYZ, SPUFI PLAN DSNESP* TMDB02007W THREAD WITH ELAPSED TIME OF x TMDB02008C THREAD TERMINATED INDOUBT High Red TMDB02009W INDOUBT TIME > CONN ID CICSP, PLAN CICST* TMDB02010I THREAD WITH I/0 WAIT TIME OF x TMDB02011W THREAD LOCK ESCALATION(S) SHARED PLAN ABC TMDB02012W THREAD LOCK ESCALATION(S) EXCLUSIVE PLAN ABC TMDB02013I THREAD WITH LOCK WAIT TIME > 1.0 TMDB02014W SPUFI THREAD EXECUTED WITH FETCHS > 1000 TMDB02015W SPUFI THREAD # RECORDS SORTED > Version 1.5

17 Name Description Priority Alert-state TMDB02016W PLAN DSNESPCS SORT ELAPSED TIME > 1.5 TMDB02017W PLAN DSNESPRR SORT ELAPSED TIME > 1.5 TMDB02018W TMDB05001W TMDB05002W THREAD TIMEOUT AUTH ID XYZ, SPUFI PLAN DSNESP* AUTH ID LSCUSER TIMEOUT OR DEADLOCK OCCURRED CONNECTION NAME SPUFI TIMEOUT OR DEADLOCK OCCURRED TMDB05003W CORRELATION ID LSCUSER TIMEOUT / DEADLOCK OCCURRED TMDB05004W TMDB06001I TMDB06002I TMDB06003I PLAN NAME DSNESPRR TIMEOUT OR DEADLOCK OCCURRED AUTHID LSCUSER ISSUED SET CURRENT SQLID CONNECTION NAME SPUFI ISSUED SET CURRENT SQLID PLAN NAME DSNESPRR ISSUED SET CURRENT SQLID TMDB08001I THREAD IDENTIFY - AUTH ID LSCUSER TMDB08001I AUTH ID LSCUSER SIGN ON TO DB2 TMDB08002I THREAD IDENTIFY CONNECTION ID CICSP TMDB08002I CONNECTION NAME LSCUSER SIGN ON TO DB2 TMDB08003C PLAN NAME CICS1111 SIGN ON TMDB08003I TMDB09001W TMDB09002I THREAD IDENTIFY - PLAN ABC12345THREAD IDENTIFY - PLAN ABC12345 AUTH ID SYSOPR AUTHORIZATION FAILURE OCCURRED BIND ADD AUTHORIZATION FAILURE OCCURRED TMDB09003W BUFFER POOL AUTHORIZATION FAILURE TMDB09004W TMDB09005W TMDB09006W TMDB09007I TMDB09008W TMDB09009W DATABASE AUTHORIZATION FAILURE OCCURRED APPLICATION PLAN AUTHORIZATION FAILURE OCCURRED PLAN NAME DSNESPCS AUTHORIZATION FAILURE OCCURRED START DATABASE COMMAND AUTHORIZATION FAILURE STOGROUP AUTHORIZATION FAILURE OCCURRED TABLESPACE AUTHORIZATION FAILURE OCCURRED TMDB10001I DATABASE AUTHORIZATION GRANT Tivoli Business Systems Manager TMON for DB2 Release Notes 17

18 Name Description Priority Alert-state TMDB10002I DATABASE AUTHORIZATION REVOKED TMDB10003I TMDB10004I TMDB10005I TMDB11001W TMDB11002W DATABASE USER AUTHORIZATION GRANTED BY DBCTRL GRANT HAS BEEN ISSUED BY AUTH ID LSCUSER REVOKE HAS BEEN ISSUED BY AUTH ID LSCUSER AUTH ID LSCUSER ISSUED DDL ON AUDITED OBJECT CONNECT NAME SPUFI ISSUED DDL ON AUDITED OBJECT TMDB11003W CREATE DDL ISSUED ON AUDITED OBJECT TMDB11004W DROP DDL ISSUED ON AUDITED OBJECT TMDB11005W DROP DDL ISSUED ON AUDITED TABLE TMDB11006W PLAN DSNESPRR ISSUED DDL ON AUDITED OBJECT TMDB11007W DDL ISSUED ON AUDITED TABLE HISTCTL1 TMDB12001W TMDB12002W TMDB13001W TMDB13002W AUTH ID LSCUSER ISSUED 1ST WRITE ON AUDITED OBJECT PLAN NAME DSNESPRR 1ST WRITE ON AUDITED OBJECT AUTH ID LSCUSER 1ST READ OF AUDITED OBJECT PLAN NAME DSNESPRR 1ST READ OF AUDITED OBJECT TMDB14001W AUTH ID LSCUSER DML ON AUDITED OBJECT TMDB14002W DELETE DML ISSUED ON AN AUDITED OBJECT TMDB14003W Buffer Pool PLAN NAME DSNESPRR DML ON AUDITED OBJECT Name Description Priority Alert-state TMDB01103C BP4K00 DM CRITICAL REACHED x TIMES High Red TMDB01104W BP4K00 DEFERRED WRITE THRESHOLD > 50 High Red TMDB01105W BP4K00 EXPANSIONS > 0 High Red TMDB01114C BP32K0 DM CRITICAL REACHED x TIMES High Red TMDB01115W BP32K0 DEFERRED WRITE THRESHOLD > 50 High Red TMDB01116W BP32K0 EXPANSIONS > 0 High Red TMDB02002W THREAD BP4K00 SYNC READS > Version 1.5

19 EDM Pool Name Description Priority Alert-state TMDB01123W EDMPOOL FAILURES > 0 Note: No automatic resolution event is generated for this exception: the TBSM user must manually resolve this exception event. Critical TMDB04001C BATCH PROGRAM EDMPOOL FAIL High Red TMDB04002C PLAN DSNESPCS EDMPOOL FAIL High Red TMDB04003C PLAN DSNESPRR EDMPOOL FAIL High Red TMDB04004C SPUFI CONNECTION EDMPOOL FAIL High Red TMDB04005C UTILITY PROGRAM EDMPOOL FAIL High Red Logs Name Description Priority Alert-state TMDB01101W ACTIVE LOG WRITE WAITS IN INTERVAL Medium TMDB01102W ARCHIVE LOG READS > 0 Medium Red Tivoli Business Systems Manager TMON for DB2 Release Notes 19