MainView for CICS Release Notes Version 1.5

Transcription

1 MainView for CICS Release Notes Version 1.5

2 MainView for CICS 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, CICS, Cross-Site, 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. MAINVIEW is a registered trademark of BMC Software, Inc. in the United States. AutoOPERATOR and BMC 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 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 MAINVIEW FOR CICS MONITORING... 4 SOFTWARE REQUIREMENTS... 4 OVERVIEW OF TBSM PROCESSING... 5 PROCESSING EVENTS... 5 EVENT FLOW... 6 CUSTOMIZATION... 9 CUSTOMIZING MAINVIEW FOR CICS... 9 CUSTOMIZING NETVIEW What This NetView Customization Does Members Used In This Customization If You Are Already Using MainView AutoOPERATOR To Capture Messages EVENT PROCESSING SCENARIOS...13 DB2 CICS INTERFACE UNAVAILABLE DB2 CICS INTERFACE BECOMES AVAILABLE AGAIN TROUBLESHOOTING APPENDIX A. TBSM EXCEPTIONS CAUSED BY MAINVIEW FOR CICS EXCEPTIONS CAUSED BY WORKLOAD MONITOR SERVICES EXCEPTIONS CAUSED BY RESOURCE MONITOR SERVICES Tivoli Business Systems Manager MainView for CICS Release Notes 3

4 Overview of MainView for CICS Monitoring CICS is an application server from IBM that provides industrial-strength, online transaction management for mission-critical applications. MainView for CICS is a software product from BMC Software that monitors CICS performance statistics. This document describes how to integrate MainView for CICS with Tivoli Business Systems Manager (TBSM), so that messages issued by MainView for CICS are translated into events for the relevant CICS objects in TBSM. MainView for CICS provides monitors that regularly collect data about conditions in a CICS region. (These monitors are sometimes also referred to as timer-driven requests.) Each monitor collects data for a different performance statistic, such as average response time. When you start a monitor, you can define a warning threshold value for the statistic. If the statistic exceeds the warning threshold, then the monitor issues a warning message. Later, if the statistic drops below the warning threshold, then the service issues a matching resolution message. Integrating MainView for CICS with TBSM involves capturing these warning and resolution messages, translating them into events understood by TBSM, and passing them to TBSM. This process is described in detail in Processing Events on page 5. Software Requirements MainView for CICS Version with PUT0002B service 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 object discovery. This document assumes that you have already performed CICS initial discovery (either manually or, if you have CICSPlex SM installed, as described in the TBSM CICSPlex SM 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. If TBSM receives MainView for CICS events about CICS objects that have not been registered in the TBSM Object database, then TBSM automatically creates the appropriate CICS object. For more information about CICS rediscovery, see the TBSM CICSPlex SM 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 MainView for CICS 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 MainView for CICS monitors issue messages for two types of events: when a performance statistic exceeds its threshold and when a performance statistic drops below its threshold. To allow TBSM to capture these events, you need to customize MainView for CICS monitors to use the WTO (Write to Operator) macro to direct their messages to the MVS system console. The MVS system console is monitored by Tivoli NetView for OS/390 (NetView). 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 messages from MainView for CICS monitors, you need to customize the NetView automation table to capture these messages. When the automation table captures a MainView for CICS message, it runs a REXX exec that translates the message into a TBSM event, then routes it to TBSM. Tivoli Business Systems Manager MainView for CICS Release Notes 5

6 Event Flow The following diagram shows how NetView captures WTO messages issued by MainView for CICS monitors, and routes them to TBSM. CICS OS/390 NT Server monitored by MainView for CICS Data collection monitors ( timerdriven requests ) 1 Tivoli Business Systems Manager Source/390 Object Server 5 LU6.2 or TCP/IP SNA Server Event Server 6 WTO messages Dataspace SQL Database Server System console captured by NetView 2 Object Pump PPI receiver 4 Object database Automation table uses autotask to run REXX exec PPI sender 3 NetView PPI Propagation Server Application Server 7 Graphical user interface 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 MainView for CICS monitor uses the WTO macro to issue a warning message (when a performance statistic exceeds its threshold) or a resolution message (when a performance statistic drops below its threshold) to the MVS system console. These message IDs have the following formats, depending on the particular MainView for CICS monitor (as described in the MainView for CICS Online Services Reference Manual): Message ID FTnnn0W FTnnn1I FTnnnW FTnnnI FTnnnx FTnnnZ Description Warning message Matching resolution message DB2/IMS not attached warning message (nnn: 517) (nnn: 518) MainView for CICS resource monitors Matching resolution message Warning message (x indicates the severity: I for informational, W for warning, S for severe) Matching resolution message where nnn is a three-digit number that identifies the monitor that issued the message. 2. The NetView automation table recognizes the message ID, and passes the message to a NetView autotask that runs a REXX exec. For a list of the MainView for CICS messages captured by NetView, see Appendix A. TBSM Exceptions Caused by MainView for CICS on page The REXX exec translates the MainView for CICS warning or information message into a TBSM exception or resolution event. This translation is described in the box below. Translating warning and resolution 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 events reflect 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, 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. Note: Outside of TBSM, message is often used as a general descriptive term; for example, MainView for CICS monitors issue warning 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 CICS warning messages are translated into TBSM exception events. The REXX exec translates MainView for CICS warning messages into TBSM exception events, and resolution messages into resolution events for those exceptions. The TBSM exception names are the same as the MainView for CICS warning message IDs, without the W (or, sometimes, S or I ) suffix. For example, warning message FT1020W becomes TBSM exception FT1020, and the matching resolution message FT1021I becomes a resolution event that removes the exception. (Some exceptions are given a new single-letter suffix to make their names unique. For example: FT1050A, FT1050B, FT1050C etc.) Tivoli Business Systems Manager MainView for CICS Release Notes 7

8 Exception alert state and priority Exceptions have an alert state and a priority. In TBSM, there are tables listing the exceptions that each object type can receive, and the alert state and priority of those exceptions. You can either use the Tivoli-supplied default values for alert state and priority, or you can modify these tables 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 CICS warning messages, and the TBSM objects that can receive these exceptions, see Appendix A. TBSM Exceptions Caused by MainView for CICS on page 15. After translating the MainView for CICS warning or resolution message into a TBSM exception or resolution event, the REXX exec uses the NetView program-to-program interface (PPI) to send the event 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, 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. 6. The TBSM Event Server updates the appropriate CICS 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. 7. The TBSM Application Server forwards the event to the TBSM graphical user interface (on a Windows NT workstation). 8. Finally, on the TBSM graphical user interface, an exception either appears on the Attributes tab of the property sheet for the appropriate CICS object (if it was a warning message) or is removed (if it was a resolution message). 8 Version 1.5

9 Customization To integrate MainView for CICS with TBSM, you need to do some minor customization of MainView for CICS and NetView. These customization steps are described below. Customizing MainView for CICS 1. Customize your MainView for CICS monitors to direct their messages to the MVS system console. To do this, you need to specify the keyword WMSG with the value WTO (WMSG=WTO) when you start the monitor. For details on specifying keywords when starting monitors, see the MainView for CICS Online Services Reference Manual. 2. Use the IHSCMVX1 member (supplied in the SGTMSAMP TBSM data set) to create an SMLXIT journal log user exit routine. For detailed instructions, see the comment header in the IHSCMVX1 member. This step is necessary because, even if you specify WMSG=WTO (as described in the previous step), not all messages issued by MainView for CICS monitors are directed to the MVS system console. For more information about SMLXIT, see the MainView Administration Guide. 3. Ensure that, in the MainView BBIJNTxx and BBIISPxx members, you have specified TARGET parameter values for CICS that match your CICS job names. This step is necessary because the messages issued by MainView for CICS monitors use the TARGET parameter to identify which CICS region they refer to, whereas TBSM identifies CICS regions by their job name. For details on specifying the TARGET parameter, see the step Define BBI-SS PAS Suffixes and Target System Parameters under the heading Customizing the MainView Environment in the MainView Implementation Guide. Tivoli Business Systems Manager MainView for CICS Release Notes 9

10 Customizing NetView 1. Insert the following statement in your NetView automation table: %INCLUDE IHSCMVAT The IHSCMVAT member contains automation table statements that: Start an autotask when NetView initializes. Use the autotask to run a REXX exec that processes MainView for CICS messages. 2. Insert the following statement in the DSIOPF NetView member: %INCLUDE IHSCMVOP The IHSCMVOP member defines the IHSCMVOP autotask that the automation table uses to process MainView for CICS messages. 3. If you have not already done so, concatenate the following TBSM data sets to the DD statements in your NetView start procedure: Concatenate this TBSM data set SGTMEXEC SGTMSAMP To this NetView DD statement DSICLD DSIPARM This allows NetView to find the various members used in this customization. 4. If you have not already done so, set up the NetView program-to-program interface (PPI). For details, see the Tivoli NetView for OS/390 Installation and Administration Guide and the CNMSJ010 NetView sample JCL member. To enable the TBSM Object Pump PPI receiver, specify PPI=YES in the pump configuration member. To confirm that the TBSM Object Pump PPI interface is enabled, issue the DISPPI NetView command and confirm that NETVAOP is active. 10 Version 1.5

11 What This NetView Customization Does The IHSCMVAT automation table member: Captures the following NetView initialization message (indicating that the DSILOG network log task has started): DSI530I 'DSILOG ' : 'DST' IS READY AND WAITING FOR WORK When IHSCMVAT captures this message, it uses the AUTO1 NetView initialization autotask to run the IHSCMVIN REXX exec. The IHSCMVIN REXX exec starts the IHSCMVOP NetView autotask. Other automation table statements in IHSCMVAT use this autotask to process MainView for CICS messages, as described below. Captures MainView for CICS messages. When IHSCMVAT captures these messages, it uses the IHSCMVOP autotask to run the IHSCMV01 REXX exec. The IHSCMV01 REXX exec translates these messages into TBSM events, and routes them to TBSM. Members Used In This Customization The following table describes the members used in this customization: Member Description Supplied in TBSM data set IHSCMVAT Contains NetView automation table statements that run the two REXX execs described below SGTMSAMP IHSCMVIN REXX exec that starts the IHSCMVOP autotask SGTMEXEC IHSCMV01 REXX exec that processes MainView for CICS messages SGTMEXEC IHSCMVOP Defines the IHSCMVOP autotask that the IHSCMVAT automation table member uses to run the IHSCMV01 REXX exec described above SGTMSAMP Tivoli Business Systems Manager MainView for CICS Release Notes 11

12 If You Are Already Using MainView AutoOPERATOR To Capture Messages Instead of using NetView, you can also use the MainView AutoOPERATOR product to capture MainView for CICS Resource Monitor and Workload Monitor messages, then use the TBSM GTMEDIAO REXX exec to route them to TBSM. If you use MainView AutoOPERATOR to do this, then you may wish to edit the NetView automation table statements in IHSCMVAT, 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 FT1120W warning message and its matching FT1121I resolution message, remove the following line from IHSCMVAT (indicated by a strikethrough): IF(MSGID = 'FT1110'. MSGID = 'FT1111'. MSGID = 'FT1120'. MSGID = 'FT1121'. MSGID = 'FT1130'. MSGID = 'FT1131'. MSGID = 'FT1140'. MSGID = 'FT1141'. MSGID = 'FT1150'. MSGID = 'FT1151'. MSGID = 'FT1160'. MSGID = 'FT1161'. MSGID = 'FT1170'. MSGID = 'FT1171'. MSGID = 'FT1180'. MSGID = 'FT1181'. MSGID = 'FT1190'. MSGID = 'FT1191'. MSGID = 'FT1200'. MSGID = 'FT1201' For a list of the message IDs captured by the NetView automation table, and the MainView for CICS Resource Monitor and Workload Monitor services that issue those messages, see Appendix A. TBSM Exceptions Caused by MainView for CICS on page 15. For information about coding NetView automation table statements, see the Tivoli NetView for OS/390 Automation Guide, SC For information about using the GTMEDIAO REXX exec to route messages to TBSM, see the TBSM Installation and Customization Guide. 12 Version 1.5

13 Event Processing Scenarios The following two scenarios assume that you have performed the customization steps described earlier in this document. DB2 CICS Interface Unavailable 1. MainView for CICS detects that the DB2 CICS interface is unavailable for the C1H1CICS region, and issues the following WTO message: FT517W DB2 INTERFACE UNAVAILABLE FOR DB2 ID (DB6B),TGT=CIH1CICS 2. The NetView automation table captures the message, and invokes the REXX exec that translates the FT517W message into an FT517 exception event for the CIH1CICS CICS region object in TBSM. (The name of the exception event is the same as the warning message ID, without the W suffix.) 3. The REXX exec routes the exception event to the CIH1CICS CICS region object in TBSM. 4. In the TBSM graphical user interface, an FT517 exception appears on the Attributes tab of the property sheet for the CIH1CICS CICS region object. DB2 CICS Interface Becomes Available Again 1. Later, when MainView for CICS detects that the DB2 CICS interface for the C1H1CICS CICS region has become available again, it issues the following WTO message: FT517I DB2 INTERFACE AVAILABLE FOR DB2 ID (DB6B),TGT=CIH1CICS 2. The NetView automation table captures the message, and invokes the REXX exec that translates the FT517I message into a resolution event for the earlier FT517 exception. 3. The REXX exec routes the resolution event to the CIH1CICS CICS region object in TBSM. 4. In the TBSM graphical user interface, the FT517 exception disappears from the Attributes tab of the property sheet for the CIH1CICS CICS region object. Tivoli Business Systems Manager MainView for CICS Release Notes 13

14 Troubleshooting For problems with MainView for CICS, see the MainView for CICS product documentation. Otherwise, see the Troubleshooting section in the TBSM CICSPlex SM Release Notes. 14 Version 1.5

15 Appendix A. TBSM Exceptions Caused by MainView for CICS This appendix lists the TBSM exception types that can be caused by warning messages from MainView for CICS monitors, and the TBSM objects that receive these exceptions. The tables in this appendix contain the following columns: This column Name Description Priority Alert state Object type Contains this information The exception name, as displayed on the Attributes tab of the TBSM object property sheet. The exception name consists of the MainView for CICS message ID, without the W (or S, or I ) suffix. The exception description, as displayed on the TBSM object type property sheet. The exception description consists of the name of the MainView for CICS monitor that issued the warning message, followed by the title of the performance statistic being monitored. 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. The TBSM object type that can receive the exception (CICS region or transaction). 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. You can change the priority and alert state of exceptions for each object type; the same exception name can have a different priority and alert state for different object types. However, the Tivoli-supplied default priority and alert state for each exception are the same for all of the object types that can receive the exception. Tivoli Business Systems Manager MainView for CICS Release Notes 15

16 Exceptions Caused By Workload Monitor Services Name Description Priority Alert state Object type average execution time Low Yellow CICS region average dispatch queue time Low Yellow CICS region - # of current level exception Low Yellow CICS region - # of program interrupts Low Yellow CICS region - # of current problems in CICS Medium Yellow CICS region FT1120 FT1130 # of current problems in CICS - # of current problems in CICS - # of current problems in CICS monitor data Medium Yellow CICS region Medium Yellow CICS region Low Yellow CICS region - average response time Low Yellow CICS region - # of storage violation Low Yellow CICS region FT1040 #PROC - # of transaction processed Low Yellow CICS region Exceptions Caused By Resource Monitor Services Name Description Priority Alert state Object type - %of maximum tasks Low Yellow CICS region - DB2 not attached Medium Yellow CICS region - % used of CICS TD DFHINTRA Low Yellow CICS region - % used of CICS e-private Low Yellow CICS region - % used of CIC main temp storage Low Yellow CICS region - % used of CICS private storage Low Yellow CICS region FT046 FT544 - % CPU used attributable to CICS - % CPU usage attributable to CICS user current CICS auxiliary temp buffer storage Low Yellow CICS region Low Yellow CICS region Low Yellow CICS region IMS not attached Medium Yellow CICS region - % of TD buffers in use Low Yellow CICS region - current TD buffer waits Low Yellow CICS region - % of TD strings in use Low Yellow CICS region current TD string waits Low Yellow CICS region records in Q for destination id Low Yellow CICS region records in queue exceed trigger Low Yellow CICS region - % of TS buffers in use Low Yellow CICS region current TS buffer waits Low Yellow CICS region 16 Version 1.5

17 Name Description Priority Alert state Object type FT541 storage above 16 Mb used by current storage below 16 Mb used by current tasks Low Yellow CICS transaction Low Yellow CICS transaction - % of CPU used by current tasks Low Yellow CICS transaction - # of dbs calls by current tasks Low Yellow CICS transaction - # of files used by current tasks Low Yellow CICS transaction current total storage used by active tasks Low Yellow CICS transaction - % of TS strings in use Low Yellow CICS region current TS string waits Low Yellow CICS region FT1050A #DSAV current DSA pages available Low Yellow CICS region FT1050B #DSIZ total DSA size Low Yellow CICS region FT1050C #DSTO current DSA available Low Yellow CICS region FT1050D #ESAV current EDSA pages available Low Yellow CICS region FT1050E #ESIZ total EDSA size Low Yellow CICS region FT1050F #ESTO current EDSA available Low Yellow CICS region FT1110B CSUT - % of CSA storage in use Low Yellow CICS region FT10501 FT10502 FT10503 FT10504 FT10505 FT10506 FT10507 FT10508 DSUT - % of DSA in use Low Yellow CICS region FT1110C ECSUT - % of ECSA storage in use Low Yellow CICS region FT1200 ENQC enqueue conflict Low Yellow CICS region FT1210 ENQW task waiting on enqueue Low Yellow CICS region FT1180 GBLO largest oscor below 16Mb Low Yellow CICS region FT1190 GBLQ largest lsqa below 16 Mb Low Yellow CICS region FT1170 IAID - # of automatic init descriptor Low Yellow CICS region FT1100A IDCT - # of CICS storage dumps per interval Low Yellow CICS region FT1160 IICE - # of interval control element Low Yellow CICS region FT1220 JRNR journals waiting reply Low Yellow CICS region FT1110D LSRL - % of LSR lookaside Low Yellow CICS region FT1110E LSRS - % of LSR strings used Low Yellow CICS region FT1110F LSRW current LSR string waits Low Yellow CICS region FT1070 MXTC current % of max tasks Low Yellow CICS region FT1110G PGMS program storage size Low Yellow CICS region FT1100B SDCT - # of CICS storage dumps Low Yellow CICS region Tivoli Business Systems Manager MainView for CICS Release Notes 17

18 Name Description Priority Alert state Object type FT1110H TSTE temp storage size Low Yellow CICS region FT1080 AMST max active tasks Low Yellow CICS region 18 Version 1.5