MainView for DB2 Release Notes - IBM Supportpublib.boulder.ibm.com/tividd/td/BSM/MainViewDB2ReleaseNotes15/e… · The MVS system console is monitored by Tivoli ... Tivoli Business

MainView for DB2 Release Notes Version 1.5

2 Version 1.5

MainView for DB2 Release Notes Version 1.5

Copyright Notice

© Copyright IBM Corporation 2001 All rights reserved. May only be used pursuant to a Tivoli SystemsSoftware License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products toIBM 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 anymeans, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior writtenpermission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or otherreproductions of any machine-readable documentation for your own use, provided that each suchreproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are grantedwithout prior written permission of IBM Corporation. The document is not intended for production and isfurnished �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 ADPSchedule Contract with IBM Corporation.

Trademarks

IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, CICS, Cross-Site, MVS, NetView, OS/390, and TME aretrademarks 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 theUnited States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

MAINVIEW is a registered trademark of BMC Software, Inc. in the United States. AutoOPERATOR andBMC Software are trademarks of BMC Software, Inc.

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 thatthey will be available in all countries in which Tivoli Systems or IBM operates. Any reference to theseproducts, 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 ofTivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of thereferenced product, program, or service. The evaluation and verification of operation in conjunction withother products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of theuser. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter inthis document. The furnishing of this document does not give you any license to these patents. You cansend license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive,Armonk, New York 10504-1785, U.S.A.

© Copyright International Business Machines Corporation 2001. All rights reserved.US Government Users Restricted Rights � Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.

Tivoli Business Systems Manager MainView for DB2 Release Notes 3

Table of Contents

OVERVIEW OF MAINVIEW FOR DB2 MONITORING ...................................................................... 4

SOFTWARE REQUIREMENTS......................................................................................................................... 4

OVERVIEW OF TBSM PROCESSING .................................................................................................... 5

PROCESSING EVENTS ................................................................................................................................... 5EVENT FLOW ............................................................................................................................................... 6

CUSTOMIZATION...................................................................................................................................... 9

CUSTOMIZING MAINVIEW FOR DB2............................................................................................................ 9CUSTOMIZING THE NETVIEW AUTOMATION TABLE.................................................................................. 10

What This NetView Customization Does............................................................................................... 10Customization You Should Already Have Done.................................................................................... 10Members Used In This Customization .................................................................................................. 11If You Are Already Using MainView AutoOPERATOR To Capture Messages .................................... 11

EVENT PROCESSING SCENARIOS...................................................................................................... 12

TSO USER EXCEEDS ITS CPU RESOURCE USAGE THRESHOLD ................................................................. 12TSO USER CPU RESOURCE USAGE DROPS BELOW THRESHOLD .............................................................. 12

TROUBLESHOOTING ............................................................................................................................. 13

APPENDIX A. TBSM EXCEPTIONS CAUSED BY MAINVIEW FOR DB2 WARNINGMESSAGES................................................................................................................................................. 14

DB2 SUBSYSTEM....................................................................................................................................... 15BUFFER POOL ............................................................................................................................................ 22EDM POOL................................................................................................................................................ 25LOGS.......................................................................................................................................................... 26DIST ......................................................................................................................................................... 27

4 Version 1.5

Overview of MainView for DB2 MonitoringMainView for DB2 is a software product from BMC Software that monitors the performance of DB2subsystems.

This document describes how to integrate MainView for DB2 with Tivoli Business Systems Manager(TBSM), translating messages issued by MainView for DB2 into events for the relevant DB2 objects inTBSM.

MainView for DB2 provides services that monitor DB2 performance indicators. Each service monitors asingle indicator, such as the percentage of buffer pool usage. When you start a service, you can define athreshold value for its indicator. If the indicator exceeds the threshold value, then the service issues awarning message. Later, if the indicator drops below the threshold value, then the service issues amatching �condition clear� message. (Note: the MainView for DB2 product documentation uses the terms�service� and �monitor� interchangeably; this document uses the term �service�.)

Integrating MainView for DB2 with TBSM involves capturing these warning and condition clear messages,translating them into events understood by TBSM, and passing them to TBSM. (This integration includesthe following types of MainView for DB2 services: Resource Monitors, Workload Monitors, andBackground Exception Samplers.) This event processing is described in detail in �Processing Events� onpage 5.

Note: This document assumes that you have already integrated your DB2 subsystems with TBSM, asdescribed in the TBSM DB2 and DB2 PM Release Notes. Integrating MainView for DB2 with TBSMbuilds on this existing DB2 integration, using MainView for DB2 to provide additional monitoring. Formore information about the existing DB2 integration assumed by this document, see the TBSM DB2 andDB2 PM Release Notes.

Software Requirements• MainView for DB2 Version 6.1 with PUT0002B service level (plus PTFs BPD1570 and BPD1571) 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.


Overview of TBSM ProcessingTBSM operates through these key processes:

Initial discoveryBefore 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 theconfiguration of your systems and register the appropriate objects in the TBSM Object database. Thisprocess is known as initial discovery.

This document assumes that you have already performed DB2 initial discovery, as described in the TBSMDB2 and DB2 PM Release Notes.

RediscoveryAfter the initial discovery process, TBSM uses incoming events from monitored systems to identifychanges in the configuration of those systems. This process is known as rediscovery.

MainView for DB2 events are not used for re-discovery. For more information about DB2 rediscovery, seethe TBSM DB2 and DB2 PM Release Notes.

Event processingInvolves capturing specific events and routing them to TBSM. TBSM uses these events to update theTBSM Object database, resulting in updates to the TBSM graphical user interface.

Event processing for MainView for DB2 is described below to allow you to understand the overallsequence 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 detailedinstructions, see �Customization� on page 9.

Processing EventsMainView for DB2 Resource Monitor, Workload Monitor, and Background Exception Sampler servicesissue messages for two types of events: when a performance indicator exceeds its threshold and when aperformance indicator drops below its threshold.

To allow TBSM to capture these events, you need to customize MainView for DB2 services to use theWTO (Write to Operator) macro to direct their messages to the MVS system console. The MVS systemconsole is monitored by Tivoli NetView for OS/390 (NetView). NetView uses an automation table todetect when specific messages appear on the console, and take appropriate action. To allow NetView todetect and act on messages from MainView for DB2 services, you need to customize the NetViewautomation table to capture these messages and run a REXX exec. The REXX exec translates the messagesinto TBSM events, then routes them to TBSM.

6 Version 1.5

Event FlowThe following diagram shows how NetView captures MainView for DB2 WTO messages, and routes themto TBSM.

DB2

MainView for DB2

monitored by

captured by

uses autotaskto run

WTO messages

Automation table

REXX exec

resource monitors,workload monitors,and backgroundexception handlers

PPI sender

System console

NetView2

3

1

NetView PPI

NTOS/390

LU6.2

TCP/IP

orSource/390

Tivoli BusinessSystems Manager

Workstation

Server

PPI receiver

Dataspace

Object Server

SNA Server

Event Server

SQL DatabaseServer

ApplicationServer

Graphicaluser interface

PropagationServer

ObjectdatabaseObject Pump

4

56

7

8

(The Windows NT-based TBSM History Server is deliberately omitted from this diagram, because it doesnot affect event flow.)


Here is a detailed description of the event flow:

1. A MainView for DB2 service uses the WTO macro to issue a warning message (when a performanceindicator exceeds its threshold) or a condition clear message (when a performance indicator dropsbelow its threshold) to the MVS system console:

Message ID DescriptionDSnnn0W Warning message from a Resource Monitor serviceDSnnn1I Condition clear message from a Resource Monitor service

DWnnn0W Warning message from a Workload Monitor serviceDWnnn1I Condition clear message from a Workload Monitor service

DZnnn0a Warning message from a Background Exception Sampler servicewhere a identifies the severity of the warning:I informationalW warningS severe

DZnnn1I Condition clear message from a Background Exception Sampler service

where nnn is a three-digit number that identifies the service that issued the message.

2. The Tivoli NetView for OS/390 automation table recognizes the message ID, and passes the messageto a NetView autotask that runs a REXX exec.

For a list of the MainView for DB2 messages captured by NetView, see �Appendix A. TBSMExceptions Caused by MainView for DB2 Warning Messages� on page 14.

3. The REXX exec translates the MainView for DB2 warning or condition clear message into a TBSMexception or resolution event. This translation is described in the box below.

Translating warning and condition clear messages into TBSM exception and resolution 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 eventsreflect the current state of an object (such as starting, active or inactive).

Resolution events are another type of TBSM event. Resolution events occur after an exception, andindicate that the condition that caused the exception no longer exists. Resolution events are not directlyvisible on the TBSM graphical user interface: when TBSM receives a resolution event, it removes thematching (visible) exception.

Note: Outside of TBSM, �message� is often used as a general descriptive term; for example,MainView for DB2 services issue �warning and condition clear messages�. However, within TBSM,the term �message� refers specifically to a type of TBSM event. This is an important distinction;especially here, where MainView for DB2 warning messages are translated into TBSM exceptionevents.

The REXX exec translates MainView for DB2 warning messages into TBSM exception events, andcondition clear messages into resolution events for those exceptions. The TBSM exception names aresimilar to the MainView for DB2 warning message ID (in some cases, without the I, W, or S severitysuffix; or appended by an underscore and a parameter, to help further identify the source of the event).For example, warning message DZ0530W becomes TBSM exception DZ0530, and the matchinginformation message DZ0531I becomes a resolution event that removes the exception.

8 Version 1.5

Exception alert state and priority

Exceptions have an alert state and a priority. For each object type in TBSM, there is a table listing theexceptions that the object type can receive, and the alert state and priority of each exception. You caneither use the Tivoli-supplied default values for alert state and priority, or you can change some or allof these values to reflect the importance of particular exceptions to your enterprise.

For details on the default alert state and priority of the exceptions caused by MainView for DB2warning messages, and the TBSM objects that can receive these exceptions, see �Appendix A. TBSMExceptions Caused by MainView for DB2 Warning Messages� on page 14.

After translating the MainView for DB2 warning or condition clear message into a TBSM exception orresolution event, the REXX exec uses the NetView program-to-program interface (PPI) to send theevent to the TBSM Source/390 Object Pump.

4. The TBSM Source/390 Object Pump stores the event in the TBSM Source/390 Dataspace.

5. The TBSM Source/390 Object Server retrieves the event from the TBSM Source/390 Dataspace, andforwards it to TBSM on Windows NT; either via an LU 6.2 session to the TBSM SNA Server, or via aTCP/IP session directly to the TBSM Event Server.

6. The TBSM Event Server updates the appropriate DB2 object in the TBSM Object database (managedby the TBSM SQL Database Server).

The event might also be propagated by the TBSM Propagation Server to parent objects in the TBSMobject model hierarchy, involving further updates to the TBSM Object database.

7. The TBSM Application Server forwards the event to the TBSM graphical user interface (on aWindows NT workstation).

8. Finally, on the TBSM graphical user interface, an exception either appears on the Attributes tab of theproperty sheet for the appropriate DB2 object (if it was a warning message) or is removed (if it was acondition clear message).


CustomizationTo integrate MainView for DB2 with TBSM, you need to do some minor customization of MainView forDB2 and the NetView automation table. These customization steps are described below.

Customizing MainView for DB21. Customize your MainView for DB2 Resource Monitor and Workload Monitor services to direct their

messages to the MVS system console.

To do this, you need to specify the keyword WMSG with the value WTO when you start the service.For example, when starting the THDQD service, specify:

REQ=THDQD … WMSG=WTO …

For details, see MainView for DB2 User Guide Volume 1: Overview/Analyzers/Monitors, documentnumber 100025669.

2. Customize your MainView for DB2 Background Exception Sampler services to direct their messagesto the MVS system console.

To do this, you need to specify BMSGWTO=YES (to apply to all exception samplers) or WTO=YES (forindividual exception samplers) in the DMRBEXxx MainView for DB2 member.

For details, see MainView for DB2 Customization Guide, document number 100025710.

3. Ensure that, in the MainView BBIJNTxx and BBIISPxx members, you have specified TARGETparameter values for your DB2 subsystems that match the DB2 started task name.

This is necessary because the messages issued by MainView for DB2 services use the TARGETparameter to identify which DB2 subsystem they refer to, whereas TBSM identifies DB2 subsystemsby started task name.

For details on specifying the TARGET parameter, see the step �Define BBI-SS PAS Suffixes andTarget System Parameters� under the heading �Customizing the MainView Environment� inMainView Implementation Guide, document number 100030030.

10 Version 1.5

Customizing The NetView Automation TableCustomizing the NetView automation table involves a single step.

• Insert the following statement in your NetView automation table:

%INCLUDE IHSBMVAT

What This NetView Customization DoesThe IHSBMVAT automation table member captures MainView for DB2 messages, and runs one of threeREXX execs:

REXX exec� Processes messages issued by�IHSBMVDS Resource MonitorIHSBMVDW Workload MonitorIHSBMVDZ Background Exception Sampler

These REXX execs translate the messages into TBSM events, and route them to TBSM.

Customization You Should Already Have DoneThis customization of the NetView automation table relies on the assumption that you have alreadyperformed the steps described in the TBSM DB2 and DB2 PM Release Notes. In particular, you shouldhave:

• Concatenated this TBSM data set� To this NetView DD statement�SGTMEXEC DSICLDSGTMSAMP DSIPARM

This allows NetView to find the members used in this customization.

• Inserted the following statement in the DSIOPF NetView member:

%INCLUDE IHSBOPR

Concatenating the SGTMEXEC and SGTMSAMP TBSM data sets to the DD statements in your NetViewstart procedure allows NetView to find the IHSBMVAT automation table member and the three REXXexecs.

The IHSBOPR member defines the IHSBAT00 autotask that the IHSBMVAT automation table memberuses to process MainView for DB2 events. This is the same autotask that is used to process some DB2 andDB2 PM events.


Members Used In This CustomizationThe following table describes the members used in this customization:

Member Description Supplied inTBSM data set

IHSBMVDSIHSBMVDWIHSBMVDZ

REXX execs that process MainView for DB2 messages SGTMEXEC

IHSBMVAT Contains NetView automation table statements that run the aboveREXX execs

SGTMSAMP

If You Are Already Using MainView AutoOPERATOR To Capture MessagesInstead of using NetView, you can also use the MainView AutoOPERATOR product to capture MainViewfor DB2 messages, then use the TBSM GTMEDIAO REXX exec to route them to TBSM. If you useMainView AutoOPERATOR to do this, then you may wish to edit the NetView automation tablestatements in IHSBMVAT, and remove the IF statement conditions that capture those message IDs.Otherwise, duplicate exceptions will appear on the TBSM graphical user interface.

For example, to stop the NetView automation table capturing the DS0080W warning message and itsmatching DS0081I condition clear message, remove the following line from IHSBMVAT (indicated by astrikethrough):

IF (MSGID = 'DS0030W' | MSGID = 'DS0031I'| MSGID = 'DS0040W' | MSGID = 'DS0041I'| MSGID = 'DS0050W' | MSGID = 'DS0051I'| MSGID = 'DS0060W' | MSGID = 'DS0061I'| MSGID = 'DS0070W' | MSGID = 'DS0071I'| MSGID = 'DS0080W' | MSGID = 'DS0081I'| MSGID = 'DS0090W' | MSGID = 'DS0091I'| MSGID = 'DS0100W' | MSGID = 'DS0101I'| MSGID = 'DS0110W' | MSGID = 'DS0111I'| MSGID = 'DS0120W' | MSGID = 'DS0121I')

For a list of the message IDs captured by the NetView automation table, and the MainView for DB2services that issue those messages, see �Appendix A. TBSM Exceptions Caused by MainView for DB2Warning Messages� on page 14.

For information about coding NetView automation table statements, see the Tivoli NetView for OS/390Automation Guide, SC31-8225.

For information about using the GTMEDIAO REXX exec to route messages to TBSM, see the TBSMInstallation and Customization Guide.

12 Version 1.5

Event Processing ScenariosThe following two scenarios assume that you have performed the customization steps described earlier inthis document.

TSO User Exceeds Its CPU Resource Usage Threshold1. A background exception sampler detects that a TSO user named TONYF has exceeded its CPU

resource usage threshold value, and issues warning message DZ0630W to the MVS system console:

DZ0630W DB6S RUNAWAY TSO QUERY USER TONYF CPU%=16.8 PGM=DSNECP10PLAN=DSNESPCS BBDB

2. The NetView automation table captures the message, and invokes the REXX exec that translates theDZ0630W message into a DZ0630_TONYF exception event for the DB6S DB2 subsystem object inTBSM. (For details on exception event naming, see �Appendix A. TBSM Exceptions Caused byMainView for DB2 Warning Messages� on page 14.)

3. The REXX exec routes the exception event to the DB6S DB2 subsystem object in TBSM.

4. In the TBSM graphical user interface, a DZ0630_TONYF exception appears on the Attributes tab ofthe property sheet for the DB6S DB2 subsystem transaction object.

TSO User CPU Resource Usage Drops Below Threshold1. A background exception sampler detects that the CPU resource usage for the TONYF TSO user has

dropped below the threshold value, and issues a DZ0631I condition clear message to the MVS systemconsole.

DZ0631I DB6S EXCEPTION CLEARED: RUNAWAY TSO QUERY USER TONYFCPU%=0.0 PGM=DSNECP10 PLAN=DSNESPCS BBDB

2. The NetView automation table captures the message, and invokes the REXX exec that translates theDZ0631I message into a resolution event for the earlier DZ0630_TONYF exception.

3. The REXX exec routes the resolution event to the DB6S DB2 subsystem object in TBSM.

4. In the TBSM graphical user interface, the DZ0630_TONYF exception disappears from the Attributestab of the property sheet for the DB6S DB2 subsystem object.

For details on which TBSM objects are affected by messages issued by MainView for DB2, see �AppendixA. TBSM Exceptions Caused by MainView for DB2 Warning Messages� on page 14.


TroubleshootingFor problems with MainView for DB2, see the MainView for DB2 product documentation.

Otherwise, see the Troubleshooting section in the TBSM DB2 and DB2 PM Release Notes.

14 Version 1.5

Appendix A. TBSM Exceptions Caused byMainView for DB2 Warning MessagesThis appendix lists the TBSM exception types that can be caused by warning messages from MainView forDB2 services.

The exception types are listed under the TBSM object types that can receive exceptions caused byMainView for DB2:

• DB2 subsystems• Buffer pools• EDM pools• DIST

The tables in this appendix contain the following columns:

This column� Contains this information�

Name The exception name, as displayed on the Attributes tab of the TBSM object propertysheet. The exception name consists of the MainView for DB2 warning message ID,in some cases followed by an underscore, then a parameter value (see the Parameterscolumn).

Description The exception description, as displayed on the TBSM object type property sheet..The exception description consists of the name of the MainView for DB2 service thatissued the warning message, followed by the performance indicator that the servicemonitors.

Priority The Tivoli-supplied default priority of the exception, as displayed on the Attributestab of the TBSM object property sheet.

Alert state The Tivoli-supplied default alert state of the exception, as displayed on the Attributestab of the TBSM object property sheet.

Parameters The MainView for DB2 service parameters you can specify that are appended to theexception name, to help you identify the source of the 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, withpriority and alert state values for each exception. You can either use the Tivoli-supplied defaults (listed inthis appendix), or you can change these values to reflect the importance of exceptions to your particularenterprise. For details on changing the priority and alert state of exceptions, see the TBSM AdministrationGuide.

You can change the priority and alert state of exceptions for each object type; the same exception name canhave a different priority and alert state for different object types. However, the Tivoli-supplied defaultpriority and alert state for each exception are the same for all of the object types that can receive theexception.


DB2 SubsystemName Description Priority Alert state ParametersDZ0010 (n) DB(s)/TS(s) Stopped Medium Yellow NoneDZ0020_user User (user) Lock Escalated Low Yellow userDZ0530 (n) DB(s)/TS(s) Restricted Low Yellow NoneDZ0550 Max TSO Users Connected High Red NoneDZ0560 Max Batch Users Connected High Red NoneDZ0570 Max Datasets Open Medium Yellow NoneDZ0590 SOS � Short On Storage Medium Yellow NoneDZ0610 Runaway IMS MPP Medium Yellow NoneDZ0620_user Runaway CICS Transaction User

userMedium Yellow user

DZ0630_user Runaway TSO Query User user Medium Yellow userDZ0640_user Runaway Batch User user Medium Yellow userDZ0650_user Runaway CAF User user Medium Yellow userDZ0660_user Runaway Utility Function User user Medium Yellow userDZ0670_user Runaway DBAT User user Medium Yellow userDZ0680 Runaway IMS BMP Medium Yellow NoneDZ0690 Runaway IMS TBMP Medium Yellow NoneDZ1010 Indoubt Threads High Red NoneDZ1020 IMS Task(s) Queued For Thread(s) High Red NoneDZ1030 CICS Task(s) Queued For Thread(s) High Red NoneDZ1140 Indoubt Thread Not Avail This Cycle High Red NoneDS0030 DSOPN DB Data Sets Open Low Yellow NoneDS0040_parm DSOPR DB Data Set Open

Requests(parm)Low Yellow Blank

BP0-BP49BP8K0-BP8K9BP16K0-BP16K9BP32K-BP32K9

DS0050 DSUTL Open DB Data Set % Util Low Yellow NoneDS0060_parm CONUT Connection %

Utilization(parm)Low Yellow Blank

TSOBATCHDBAT

DS0070 THDUT Thread % Utilization Low Yellow None

16 Version 1.5

Name Description Priority Alert state ParametersDS0080_parm THDAC ActiveThreads(parm) Low Yellow Blank

TSOBATCHCAFUTILIMSCICSDBATDISTDDFSPASRRSAF

DS0090_parm THDQD Queued Threads(parm) Low Yellow BlankTSOBATCHCAFUTILIMSCICSSPASRRSAF

DS0650 DBTQD Database Thread Queued Low Yellow NoneDS0100 THDID In Doubt Threads Medium Yellow NoneDS0110 THDCR Create Thread Requests Low Yellow NoneDS0120 THDWT Create Thread Waited Low Yellow NoneDS0130 THDAB Rollback Requests Low Yellow NoneDS0140 COMP2 Phase 2 Commits Low Yellow NoneDS0150 COMSY Sync Commits Low Yellow NoneDS0640 COMRO Read-Only Commits Low Yellow NoneDS0160 EOMFL EOM Failures Low Yellow NoneDS0170 EOTFL EOT Failures Low Yellow NoneDS0180 BINDS Successful Auto Binds Low Yellow NoneDS0190 BINDF Failed Auto Binds Low Yellow NoneDS0680 PLBND Plans Bound Low Yellow NoneDS0690 PKBND Packages Bound Low Yellow NoneDS0700 BNPKS Auto Bind Pkg Successful Low Yellow NoneDS0710 BNPKF Auto Bind Pkg Failed Low Yellow None


Name Description Priority Alert state ParametersDS0200_parm SQLAC SQL Activity(parm) Low Yellow Blank

DDLAUTHSELLOCKUIDDYNCTLOPENCLOSECALL

DS0660 RSQLS Remote SQL Sent Low Yellow NoneDS0670 RSQLR Remote SQL Received Low Yellow NoneDS0810_parm PRLG I/O PRLL-Groups

Executed(parm)Low Yellow Blank

PLANNEDREDUCED

DS0820_parm PRLF I/O PRLL-Fallback Seq(parm) Low Yellow BlankCURSORNOSORTBOBFRNOENCLAV

DS0830_parm PRLSF Sysplex PRLL QueryFails(Parm)

Low Yellow BlankCOORNOISORRCSKIP

DS1400_parm SPROC Stored Procedures(parm) Low Yellow BlankCALLSABENDSTIMEOUTSREJECTSFAILURES

DS1670 LOBMX Max LOB Storage Low Yellow NoneDS1590_parm DROWA Direct Row Access(parm) Low Yellow Blank

USEDFAILIXFAILTSFAILURES

DS1600_parm TRIGR Trigger Usage(parm) Low Yellow BlankSTMTROWERROR

DS1610 NESTM Max Nested SQL level Low Yellow None

18 Version 1.5

Name Description Priority Alert state ParametersDS1620_parm UDF UDF Usage(parm) Low Yellow Blank

EXECSABENDSTIMEOUTSREJECTSFAILURE

DS0210_parm USLOK Users suspended forLock(parm)

Low Yellow BlankTSOBATCHCAFUTILIMSCICSDBATDISTDDFSPASRRSAF

DS0220_parm TSLOK Tablespace LockCount(parm)

Low Yellow BlankSHREXCL

DS0230_parm IXLOK Index Space LockCount(parm)

Low Yellow BlankSHREXCL

DS0240_parm PGLOK Page Lock Count(parm) Low Yellow BlankSHREXCL

DS0250 MXLOK Max page Locks Low Yellow NoneDS0260 LDEAD Lock Deadlock Failures Low Yellow NoneDS0280 LTIME Lock Timeout Failures Low Yellow NoneDS0290_parm LESCL Lock Escalations(parm) Low Yellow Blank

SHREXCL

DS0270_parm LSUSP Suspensions(parm) Low Yellow BlankLOCKLATCHOTHER

DS0270_parm LREQ Lock Requests(parm) Low Yellow BlankLOCKUNLOCK

DS0580_parm ILREQ IRLM Request Counts(parm) Low Yellow BlankQUERYCHANGEOTHER


Name Description Priority Alert state ParametersDS0770 CLM Claim Requests Low Yellow NoneDS0780 CLMF Claim Failures Low Yellow NoneDS0790 DRN Drain Requests Low Yellow NoneDS0800 DRNF Drain Failures Low Yellow NoneDS1410_parm GPLK Global P-Lock Req(parm) Low Yellow Blank

LOCKCHANGEUNLOCK

DS1420_parm GXES Global Lock XES Req(parm) Low Yellow BlankLOCKCHANGEUNLOCKASYNC

DS1430_parm GSUSP Global LockSuspends(parm)

Low Yellow BlankIRLMXESFALSEINCOMPAT

DS1440_parm GNEG Negotiate P-Lock(parm) Low Yellow BlankPGSETPAGECHNGOTHER

DS1450 GNOEN No Engines-P-Lock Low Yellow NoneDS1480_parm GNTFM Notify Messages(parm) Low Yellow Blank

SENTRECV

DS0530_parm DB2DP Demand Paging(parm) Low Yellow BlankIRLMSSASDBASSPASDB2DDF

DS0540 CSAPG CSA Paging Low Yellow NoneDS0550 CSAP CSA % Utilization Low Yellow NoneDS0560 ECSAP ECSA % Utilization Low Yellow NoneDW0020_parm #SQLD DDL SQL Statements(parm) Low Yellow Blank

parmDW0200_parm #SQLM Data Manipulative

Stmts(parm)Low Yellow Blank

parmDW0210_parm #SQLA Administrative Stmts(parm) Low Yellow Blank

parm

20 Version 1.5

Name Description Priority Alert state ParametersDW0220_parm #SQLC SQL Stmts Per

Commit(parm)Low Yellow Blank

parmDW0030_parm #DYN Dynamic SQL

Statements(parm)Low Yellow Blank

parmDW0400_parm #CALL SQL Call Statements(parm) Low Yellow Blank

parmDW0410_parm #SPRC Sprocs Executed(parm) Low Yellow Blank

parmDW0600_parm #REOP Reoptimizations(parm) Low Yellow Blank

parmDW0180_parm @CPU Average CPU Used(parm) Low Yellow Blank

parmDW0190_parm @CPUD Avg CPU In DB2(parm) Low Yellow Blank

parmDW0090_parm #DDLK Deadlocks(parm) Low Yellow Blank

parmDW0100_parm #TMO Timeouts(parm) Low Yellow Blank

parmDW0110_parm #SUSP Suspensions(parm) Low Yellow Blank

parmDW0130_parm #ESCL Escalations(parm) Low Yellow Blank

parmDW0140_parm #MAXL Maximum Locks

Held(parm)Low Yellow Blank

parmDW0240_parm #CLMF Claim Fails(parm) Low Yellow Blank

parmDW0250_parm #DRNF Drain Fails(parm) Low Yellow Blank

parmDW0490_parm #GSUS Global Content

Suspends(parm)Low Yellow Blank

parmDW0500_parm #GFAL False Contention

Suspend(parm)Low Yellow Blank

parmDW0510_parm #GRTA Incomp Retain LK

Suspend(parm)Low Yellow Blank

parmDW0520_parm #GLRQ Global LK Lock Req(parm) Low Yellow Blank

parmDW0560_parm #GLKX Global Lock Xes Req(parm) Low Yellow Blank

parmDW0590_parm #GNTS Notify Messages Sent(parm) Low Yellow Blank

parmDW0120_parm @ELAP Avg Elapsed Time(parm) Low Yellow Blank

parm


Name Description Priority Alert state ParametersDW0150_parm @ELPD Avg Elapsed In DB2(parm) Low Yellow Blank

parmDW0430_parm @ELP3 Avg Elap Wait-All

Class3(parm)Low Yellow Blank

parmDW0160_parm @ELIO Avg Elapsed For I/O(parm) Low Yellow Blank

parmDW0170_parm @ELLK Avg Elapsed For

Locks(parm)Low Yellow Blank

parmDW0330_parm @ELPR Avg Elapsed For PF

Read(parm)Low Yellow Blank

parmDW0260_parm @ELDR Avg Elapsed For Drain

WT(parm)Low Yellow Blank

parmDW0270_parm @ELCL Avg Elapsed For Claim

WT(parm)Low Yellow Blank

parmDW0280_parm @ELPL Avg Elapsed For PG

Latch(parm)Low Yellow Blank

parmDW0420_parm @ELSP Avg Elap Wait-Sproc

TCB(parm)Low Yellow Blank

parmDW0470_parm @ELGM Avg Elap Wait-Ntfy

Msg(parm)Low Yellow Blank

parmDW0480_parm @ELGL Avg Elap Wait-Glbl

Lock(parm)Low Yellow Blank

parmDW0010_parm #PROC DB2 Trans Processed(parm) Low Yellow Blank

parmDW0340_parm #PRLG I/O PRLL-Groups

Execs(parm)Low Yellow Blank

parmDW0350_parm #PRLR I/O PRLL-Groups

Reduced(parm)Low Yellow Blank

parmDW0360_parm #PRLF I/O PRLL-Fallback

Seq(parm)Low Yellow Blank

parmDW0390_parm #PRLS Sysplex PRLL Query

Fails(parm)Low Yellow Blank

parm

22 Version 1.5

Buffer PoolName Description Priority Alert state ParametersDZ0040I_n BP(n) Deferred Write Reached High Red n=(0-49,K0-K9)DS0520W_n BP(n) Prefetch Disabled Medium Yellow n=(0-49,K0-K9)DZ0600W_n BP(n) (x) Expansions Medium Yellow n=(0-49,K0-K9)DZ1050S_n BP(n) DM Critical Threshold

ReachedHigh Red n=(0-49,K0-K9)

DZ1060S_n BP(n) Immediate Write ThresholdReached

High Red n=(0-49,K0-K9)

DZ1070S_n BP(n) Buffer Locate, Pool Full High Red n=(0-49,K0-K9)DZ1080S_n BP(n) Expansion Failure Virtual

Storage ShortageHigh Red n=(0-49,K0-K9)

DS0320W_parm BPUTL BPR Pool %Utilization(parm)

Medium Yellow BlankBP0-BP49BP8K0-BP8K9BP16K0-BP16K9BP32K-BP32K9

DS0330W BPUSE BFR Pool % In Use(parm) Low Yellow Buffer PoolDS0340W RWP Reads With Paging(parm) Low Yellow Buffer PoolDS0350W WWP Writes With Paging(parm) Low Yellow Buffer PoolDS0360W GETPG Getpage Requests(parm) Low Yellow Buffer PoolDS0370W RIO RIO-Read I/O(parm) Low Yellow Buffer PoolDS0380W SWS SWS-System Page

Updates(parm)Low Yellow Buffer Pool

DS0390W WIO WIO-Write I/O(parm) Low Yellow Buffer PoolDS0400W PWS PWS-System Pages

Written(parm)Low Yellow Buffer Pool

DS0410W GETRI Getpages Per ReadI/O(parm)

Low Yellow Buffer Pool

DS0420W SWSPW Updates Per PageWritten(parm)


DS0430W PWSWI Pages Written/WriteI/O(parm)


DS0590W MIGDS Migrated Data Sets(parm) Low Yellow Buffer PoolDS0600W RTO Recall Time-Outs(parm) Low Yellow Buffer PoolDS0610W PIO Prefetch Read I/O(parm) Low Yellow Buffer PoolDS0620W RIDUT RID Pool % Utilization Low Yellow NoneDS0630W_parm MIAPF Multi-Index Failures(parm) Low Yellow Blank

#RIDSSTOR

DS0720W LSTPF List Prefetch Req Low Yellow NoneDS0730W DESRD Destructive Read Low Yellow None


Name Description Priority Alert state ParametersDS0840W DWTX Vert-Def-Write-

Threshold(parm)Low Yellow Buffer Pool

DS0850W PFTRQ Total PrefetchRequests(parm)


DS0860W PFTIO Total Prefetch I/O(parm) Low Yellow Buffer PoolDS0870W PFTPG Total Prefetch Pgs

Read(parm)Low Yellow Buffer Pool

DS0880W PFSRQ Seq Prefetch Requests(parm) Low Yellow Buffer PoolDS0890W PFSIO Seq Prefetch I/O(parm) Low Yellow Buffer PoolDS0900W PFSPG Seq Prefetch Pgs


DS0910W PFLRQ List PrefetchRequests(parm)


DS0920W PFLIO List Prefetch I/O(parm) Low Yellow Buffer PoolDS0930W PFLPG List Prefetch Pgs


DS0940W PFDRQ Dyn PrefetchRequests(parm)


DS0950W PFDIO Dyn Prefetch I/O(parm) Low Yellow Buffer PoolDS0960W PFDPG Dyn Prefetch Pgs


DS0970W PFIOF Prefetch I/O Failures(parm) Low Yellow Buffer PoolDS0980W PRLQ Parallel Query

Requests(parm)Low Yellow Buffer Pool

DS0990W PRLQF Parallel Query ReqFails(parm)


DS1000W PRLGF Conditional GetpageFail(parm)


DS1010W PRL12 Prefetch Reduced to ½(parm) Low Yellow Buffer PoolDS1020W PRL14 Prefetch Reduced to ¼(parm) Low Yellow Buffer PoolDS1060W HPVPS Sync HP Reads(parm) Low Yellow Buffer PoolDS1070W HPVPA Async HP Reads(parm) Low Yellow Buffer PoolDS1080W MAXPF Max Concurrent PRLL

PF(parm)Low Yellow Buffer Pool

DS1090W HPWRF HP Write Failures(parm) Medium Yellow Buffer PoolDS1100W HPRDF HP Read Failures(parm) Medium Yellow Buffer PoolDS1110W SEQPG Sequential Getpage

Reqs(parm)Low Yellow Buffer Pool

DS1120W SEQIO Sequential Read I/OReqs(parm)


DS1130W WKPFZ WK File Dyn PFQty=0(parm)


DS1140W WKNBF WK File-No Bfrs(parm) Low Yellow Buffer Pool

24 Version 1.5

Name Description Priority Alert state ParametersDS1150W WKMAX WK-File-Max

Concurrent(parm)Low Yellow Buffer Pool

DS1500W_parm GRDRQ BP Read Req WithData(parm)

Low Yellow BlankBP0-BP49BP8K0-BP8K9BP16K0-BP16K9BP32K-BP32K9

DS1510W GPGWR BP Pages Written(parm) Low Yellow Buffer PoolDS1520W GCAST BP Castout Reqs(parm) Low Yellow Buffer PoolDS1530W GCTPG BP Castout Pages(parm) Low Yellow Buffer PoolDS1540W GRDIN BP Read Req-Interest(parm) Low Yellow Buffer PoolDS1550W GRDNO BP Read Req-No

Interest(parm)Low Yellow Buffer Pool

DS1560W GFAIL BP Failures(parm) Medium Yellow Buffer PoolDS1570W GOTHR BP Other Requests(parm) Low Yellow Buffer PoolDS1640W G2WRF BP CF Write Fail

2ndry(parm)Medium Yellow Buffer Pool

DW0040W_parm #GETP Getpage Requests(parm) Low Yellow Blankparm

DW0050W_parm #UPDP Update Page Requests(parm) Low Yellow Blankparm

DW0060W_parm #RDIO Read I/Os(parm) Low Yellow Blankparm

DW0070W_parm #PFRD Prefetch Reads(parm) Low Yellow Blankparm

DW0080W_parm #WRIT Write Immediates(parm) Medium Yellow Blankparm

DW0290W_parm #PFRQ Prefetch Requests(parm) Low Yellow Blankparm

DW0300W_parm #PFIO Prefetch I/Os(parm) Low Yellow Blankparm

DW0310W_parm #PFPG Prefetch Pages Read(parm) Low Yellow Blankparm

DW0320W_parm #GETF Conditional GetpageFail(parm)

Low Yellow Blankparm

DW0370W_parm #HPVS Sync Reads(parm) Low Yellow Blankparm

DW0380W_parm #HPPG HP Async Pages Read(PF)(parm)


DW0440W_parm #GSRD BP Sync Reads(parm) Low Yellow Blankparm


Name Description Priority Alert state ParametersDW0450W_parm #GSWR BP Changed PGS

Written(parm)Low Yellow Blank

parmDW0460W_parm #GSWC BP Clean PGS

Written(parm)Low Yellow Blank

parm

EDM PoolName Description Priority Alert state ParametersDZ1040S EDM Pool Full Failures Critical Red NoneDS0300W_parm EDMUT EDM % Utilization(parm) Low Yellow Blank

NOSKDS0310W_parm EDMLD Avg EDM

Requests/Load(parm)Low Yellow Blank

CTPTDBD

DS1630W EDMDS EDM Data Space % Util Low Yellow None

26 Version 1.5

LogsName Description Priority Alert state ParametersDZ0030I Log Archive Job Waiting Medium Yellow NoneDZ0510W Log Active Log Opened For Output Low Yellow NoneDZ0540W Archive Log Reads Occurring Medium Yellow NoneDZ1090S Final Active Log Dataset 75% Full Critical Red NoneDZ1100S Active Log Reduced To Single Mode High Red NoneDZ1110S BSDS Reduced To Single Mode High Red/H NoneDZ1130S No Active Log Data Sets Critical Red NoneDS0440W ARCWA Archive Log Write Allocs Low Yellow NoneDS0450W ARCRA Archive Log Read Allocs Low Yellow NoneDS0460W ARCWR Archive Log CI Writes Low Yellow NoneDS0470W LOGWT Log Buffer Waits Low Yellow NoneDS0480W_parm LOGWR Log Write Requests(parm) Low Yellow Blank

FORCENOWAIT

DS0490W_parm LOGUT Active Log %Utilization(parm)

Low Yellow BlankCURRENT

DS0500W_parm LOGRD Log Reads forBackout(parm)

Low Yellow BlankBUFFERACTIVEARCHIVE

DS0510W BSDSA BDSD Accesses Low Yellow NoneDS0520W CHKPT Number Of Checkpoints Low Yellow NoneDS1580W CKPFR Checkpoint Frequency Low Yellow NoneDS1030W ARCTC ARC Tape Vol Contention Low Yellow NoneDS1040W ARCDL ARC Read Access Delayed Low Yellow NoneDS1050_parm ARCTM ARC LK-Ahead Tape

Mounts(parm)Low Yellow Blank

FAILSUCCESS


DISTName Description Priority Alert state ParametersDS0740W_parm DDFBS DDF Bytes Sent(parm) Low Yellow Blank

parmDS0750W_parm DDFBR DDF Bytes Received(parm) Low Yellow Blank

parmDS0760W_parm DDFCQ DDF Conv Queued(parm) Low Yellow Blank

parmDS1160W CNVLM Conv Dealloc Zparm Limit Low Yellow NoneDS1170W_parm NACTC Current Inact DB

Thrds(parm)Low Yellow Blank

TYPE1TYPE2

DS1180W_parm P2CON 2-Phase Connections(parm) Low Yellow BlankCOLDWARM

DS1200W_parm P2RSY 2-Phase ResyncConnects(parm)

Low Yellow BlankFAILSUCCSS

DS1230W_parm P2RMT Remote CoordntrTotal(parm)


DS1240W_parm P2RMI Remote CoordntrIndoubts(parm)


DS1250W_parm P2RMC Remote CoordntrCommits(parm)


DS1260W_parm P2RMR Remote CoordntrRollbks(parm)


DS1650W DDFT1 Connect Term-Max Type1 Low Yellow NoneDS1660W_parm DBATQ DBATs Queued-

Maxdbat(parm)Low Yellow Blank

NEW

Documents

MainView for DB2 Release Notes - IBM Supportpublib.boulder.ibm.com/tividd/td/BSM/MainViewDB2ReleaseNotes15/e… · The MVS system console is monitored by Tivoli ... Tivoli Business