TMON for CICS/ESA Release Notes Version 1.5

Transcription

1 TMON for CICS/ESA Release Notes Version 1.5

2 TMON 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. 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 CICS... 4 SOFTWARE REQUIREMENTS... 4 OVERVIEW OF TBSM PROCESSING... 5 PROCESSING EVENTS... 5 EVENT FLOW... 6 CUSTOMIZATION... 9 CUSTOMIZING TMON FOR CICS... 9 Excluding particular TMON for CICS messages from TBSM processing... 9 CUSTOMIZING NETVIEW What This NetView Customization Does Members Used In This Customization EVENT PROCESSING SCENARIO TROUBLESHOOTING APPENDIX A. TBSM EXCEPTIONS CAUSED BY TMON FOR CICS Tivoli Business Systems Manager TMON for CICS Release Notes 3

4 Overview of TMON for CICS The Monitor for CICS/ESA (TMON for CICS) is a CICS performance monitoring system from LandMark Systems Corporation. TMON for CICS is a component of the LandMark PerformanceWorks for MVS and OS/390 product line. This document describes how to integrate TMON for CICS with Tivoli Business Systems Manager (TBSM), so that alert messages issued by TMON for CICS SmartTargets are translated into exception events for the relevant CICS objects in TBSM. Integrating TMON for CICS with TBSM involves capturing TMON for CICS SmartTarget alert messages, translating the alert messages into events understood by TBSM, then passing the events to TBSM. This process is described in detail in Processing Events on page 5. Software Requirements The Monitor for CICS/ESA Version 2.0 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 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 TMON 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 TMON 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 To allow TBSM to capture TMON for CICS SmartTarget alert messages, you need to customize TMON for CICS to use the WTO (Write to Operator) macro to direct these alert messages to the MVS system console. (You do this by assigning the alert messages a severity of A, B, C, or Z) 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 alert messages from TMON for CICS, 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 CICS Release Notes 5

6 Event Flow The following diagram shows how NetView captures WTO messages issued by TMON for CICS SmartTargets, and routes them to TBSM. CICS OS/390 NT Server monitored by TMON for CICS SmartTargets WTO messages (TMON for CICS alert messages with severity A, B, C, or Z) System console captured by NetView Automation table 1 2 Tivoli Business Systems Manager Source/390 Object Server Dataspace Object Pump PPI receiver 5 4 LU6.2 or TCP/IP SNA Server Event Server SQL Database Server Object database Propagation Server 6 uses autotask to run REXX exec 3 NetView PPI Application Server 7 PPI sender 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 TMON for CICS SmartTarget uses the WTO macro to issue an alert message to the MVS system console. (Alert messages also appear on the TMON for CICS Problem/Alert Monitor screen.) 2. The NetView automation table recognizes the TMON for CICS SmartTarget alert message ID, and passes the message to a NetView autotask that runs a REXX exec. TMON for CICS SmartTarget alert messages IDs begin with the characters TMON26. For a complete list of the alert messages captured by NetView, see Appendix A. TBSM Exceptions Caused by TMON for CICS on page The REXX exec translates the alert message into a TBSM exception event. This translation is described in the box below. Translating alert messages 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 CICS issues alert messages. However, within TBSM, the term message refers specifically to a type of TBSM event. The REXX exec translates TMON for CICS SmartTarget alert messages into TBSM exception events. The TBSM exception names consist of the TMON for CICS alert message IDs, with a SEVn_ prefix (where n is 1-3, reflecting the TMON for CICS severity level): for example, SEV2_TMON 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 CICS, see Appendix A. TBSM Exceptions Caused by TMON for CICS on page 14. After translating the alert message into a TBSM exception 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 IMS 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. Tivoli Business Systems Manager TMON for CICS Release Notes 7

8 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 appears on the Attributes tab of the property sheet for the appropriate CICS object. No automatic resolution of TMON for CICS events Some monitoring products issue a resolution message to indicate that the condition that caused an earlier exception event no longer exists. These resolution messages can be captured, and used to generate a TBSM resolution event, which removes the earlier exception event from the TBSM graphical user interface. However, TMON for CICS does not issue resolution messages. The TBSM user must manually take ownership of and resolve these exception events, as described in the TBSM User s Guide. 8 Version 1.5

9 Customization To integrate TMON for CICS with TBSM, you need to do some minor customization of TMON for CICS and NetView. These customization steps are described below. Customizing TMON for CICS Customizing TMON for CICS involves a single step. On the TMON for CICS Message Alerts screen (option ), add the following message alert definition: Message TMON26* Sev Z This causes TMON for CICS to direct SmartTarget alert messages to the MVS system console. Specifying a severity of Z causes TMON for CICS to send alert messages to the MVS system console, keeping the default severity level supplied with TMON for CICS. To override the default severity level of particular alert messages, specify a severity of A, B, or C (this is equivalent to 1, 2, or 3, but with the messages being sent to the MVS system console). For details on using the TMON for CICS Message Alerts screen, see the TMON for CICS Reference Manual. Excluding particular TMON for CICS messages from TBSM processing To exclude particular TMON for CICS SmartTarget alert messages from TBSM processing, add (in addition to the TMON26* definition) extra message alert definitions for the specific message codes you want to exclude. Assign these definitions a blank (or 1, 2, or 3) severity, so that TMON for CICS will not direct these messages to the MVS system console. Tivoli Business Systems Manager TMON for CICS Release Notes 9

10 Customizing NetView 1. Insert the following statement in your NetView automation table: %INCLUDE IHSCTMAT 2. Insert the following statement in the DSIOPF NetView member: %INCLUDE IHSCTMOP The IHSCTMOP member defines the autotask that the automation table uses to process TMON 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 IHSCTMAT 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 IHSCTMAT captures this message, it uses the AUTO1 NetView initalization autotask to run the IHSCTM00 REXX exec. The IHSCTM00 REXX exec starts the IHSCTMOP NetView autotask (defined in the IHSCTMOP member). Other automation table statements in IHSCTMAT use this autotask to process TMON for CICS alert messages, as described below. Captures TMON for CICS alert messages. When IHSCTMAT captures these alert messages, it uses the IHSCTMOP autotask to run the IHSCTM01 REXX exec. The IHSCTM01 REXX exec translates TMON for CICS messages into TBSM exception events, and uses the NetView PPI to send the events to TBSM. Members Used In This Customization The following table describes the members involved in this customization: Member Description Supplied in TBSM data set IHSCTM00 REXX exec that starts the IHSCTMOP autotask SGTMEXEC IHSCTM01 REXX exec that processes TMON for CICS SmartTarget alert messages SGTMEXEC IHSCTMAT IHSCTMOP Contains NetView automation table statements that run the above two REXX execs Defines the IHSCTMOP autotask that the IHSCTMAT automation table member uses to run the IHSCTM01 REXX exec SGTMSAMP SGTMSAMP Tivoli Business Systems Manager TMON for CICS Release Notes 11

12 Event Processing Scenario The following scenario assumes that you have performed the customization steps described earlier in this document. 1. A TMON for CICS SmartTarget issues the following alert message to the MVS system console: TMON26204 CIH1CICS SEV2 MAX AVG RESPONSE DATA= TARGET= where is the current measurement (in seconds) of the average response time for the CIH1CICS CICS region, and is the threshold value that has been exceeded. 2. The NetView automation table captures the message, and invokes the IHSCTM01 REXX exec. The REXX exec translates the TMON26204 message into a SEV2_TMON26204 exception event for the CIH1CICS CICS region object in TBSM. 3. The IHSCTM01 REXX exec routes the exception event to the CIH1CICS CICS region object in TBSM. 4. In the TBSM graphical user interface, a SEV2_TMON26204 exception appears on the Attributes tab of the property sheet for the CIH1CICS CICS region object. 12 Version 1.5

13 Troubleshooting For problems with TMON for CICS, see the TMON for CICS product documentation. Otherwise, see the Troubleshooting section in the TBSM CICSPlex SM Release Notes. Tivoli Business Systems Manager TMON for CICS Release Notes 13

14 Appendix A. TBSM Exceptions Caused by TMON for CICS This appendix lists the TBSM exception types that can be caused by TMON for CICS SmartTarget alert messages. The tables in this appendix contain the following columns: This column Name Description Contains this information The exception name, as displayed on the Attributes tab of the TBSM object property sheet. The exception name consists of the TMON for CICS alert message ID, with a SEVn_ prefix (where n is 1-3, reflecting the TMON for CICS severity level). The exception description, as displayed on the TBSM object type property sheet. The exception description identifies the performance indicator whose value prompted the exception. Exception events caused by TMON for CICS: Are received by the appropriate TBSM CICS region object. Have a Tivoli-supplied default priority of low. Have a Tivoli-supplied default alert state that is determined by the severity level of the original TMON for CICS alert message: TMON for CICS alert message severity (see Note) Default alert state of TBSM exception event TBSM exception event name 1 Red SEV1_TMONnnnnn 2 Yellow SEV2_TMONnnnnn 3 Green SEV3_TMONnnnnn Note: The actual severity level that you specify in TMON for CICS is A, B, C, or Z (equivalent to 1, 2, 3, or program-supplied default ). For details, see Customizing TMON for CICS on page Version 1.5

15 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. Recommendation: change the TMON for CICS severity level, not the TBSM exception alert state As described above, you can change the alert state of a SEV1_TMONnnnn exception to something other than its default value of Red. However, for consistency, we recommend that if you want to change the alert state of an exception caused by TMON for CICS, then you should use the TMON for CICS Message Alerts screen (option ) to change the severity of the original TMON for CICS alert message. Name SEVn_TMON26201 SEVn_TMON26202 SEVn_TMON26203 SEVn_TMON26204 SEVn_TMON26205 SEVn_TMON26206 SEVn_TMON26207 SEVn_TMON26208 SEVn_TMON26209 SEVn_TMON26210 SEVn_TMON26211 SEVn_TMON26212 SEVn_TMON26213 SEVn_TMON26214 SEVn_TMON26215 SEVn_TMON26216 SEVn_TMON26217 SEVn_TMON26218 SEVn_TMON26219 SEVn_TMON26220 SEVn_TMON26221 SEVn_TMON26222 SEVn_TMON26223 SEVn_TMON26224 SEVn_TMON26225 SEVn_TMON26226 SEVn_TMON26227 Description MAX ENDED TRANS MIN ENDED TRANS EVAL ENDED TRANS MAX AVG RESPONSE MIN AVG RESPONSE EVAL TASK RESPONSE MAX CPU PER MINUTE MIN CPU PER MINUTE EVAL CPU / MINUTE MAX PAGE / MINUTE MIN PAGE / MINUTE EVAL PAGE / MINUTE MAX I-O / MINUTE MIN I-O / MINUTE EVAL I-O / MINUTE MAX I-O / CPUSEC MIN I-O / CPUSEC EVAL I-O / CPUSEC MAX PGS / CPUSEC MIN PGS / CPUSEC EVAL PGS / CPUSEC MAX FC REQ / MINUTE MIN FC REQ / MINUTE EVAL FC REQ / MIN MAX FC REQ AVRESP MIN FC REQ AVRESP EVAL FC REQ AVRESP Tivoli Business Systems Manager TMON for CICS Release Notes 15

16 Name SEVn_TMON26228 SEVn_TMON26229 SEVn_TMON26230 SEVn_TMON26231 SEVn_TMON26232 SEVn_TMON26233 SEVn_TMON26234 SEVn_TMON26235 SEVn_TMON26236 SEVn_TMON26237 SEVn_TMON26238 SEVn_TMON26239 SEVn_TMON26240 SEVn_TMON26241 SEVn_TMON26242 SEVn_TMON26243 SEVn_TMON26244 SEVn_TMON26245 SEVn_TMON26300 SEVn_TMON26301 SEVn_TMON26302 SEVn_TMON26303 SEVn_TMON26304 SEVn_TMON26305 SEVn_TMON26306 SEVn_TMON26307 SEVn_TMON26308 SEVn_TMON26309 SEVn_TMON26310 SEVn_TMON26311 SEVn_TMON26312 SEVn_TMON26313 SEVn_TMON26314 SEVn_TMON26315 SEVn_TMON26316 SEVn_TMON26317 SEVn_TMON26318 SEVn_TMON26319 SEVn_TMON26320 SEVn_TMON26321 Description MAX DLI REQ / MINUT MIN DLI REQ / MINUT EVAL DLI REQ / MIN MAX DLI REQ AVRESP MIN DLI REQ AVRESP EVAL DLI REQ AVRESP MAX DB2 REQ / MINUT MIN DB2 REQ / MINUT EVAL DB2 REQ / MIN MAX DB2 REQ AVRESP MIN DB2 REQ AVRESP EVAL DB2 REQ AVRESP MAX UDB REQ / MINUT MIN UDB REQ / MINUT EVAL UDB REQ / MIN MAX UDB REQ AVRESP MIN UDB REQ AVRESP EVAL UDB REQ AVRESP MAX TERMINAL TASKS MIN TERMINAL TASKS EVAL TERMINAL TASKS MAX TERMTASK IOS MIN TERMTASK IOS EVAL TERMTASK IOS MAX TERMTASK PAGES MIN TERMTASK PAGES EVAL TERMTASK PAGES MAX TERMTASK STRG MIN TERMTASK STRG EVAL TERMTASK STRG MAX TERMTASK CPU MIN TERMTASK CPU EVAL TERMTASK CPU MAX TERMTASK DISP MIN TERMTASK DISP EVAL TERMTASK DISP MAX TERMTASK SQL TI MIN TERMTASK SQL TI EVAL TERMTASK SQL T MAX TERMTASK SQL RQ 16 Version 1.5

17 Name SEVn_TMON26322 SEVn_TMON26323 SEVn_TMON26324 SEVn_TMON26325 SEVn_TMON26326 SEVn_TMON26327 SEVn_TMON26328 SEVn_TMON26329 SEVn_TMON26330 SEVn_TMON26331 SEVn_TMON26332 SEVn_TMON26333 SEVn_TMON26334 SEVn_TMON26335 SEVn_TMON26336 SEVn_TMON26337 SEVn_TMON26338 SEVn_TMON26339 SEVn_TMON26340 SEVn_TMON26341 SEVn_TMON26400 SEVn_TMON26401 SEVn_TMON26402 SEVn_TMON26403 SEVn_TMON26404 SEVn_TMON26405 SEVn_TMON26406 SEVn_TMON26407 SEVn_TMON26408 SEVn_TMON26409 SEVn_TMON26410 SEVn_TMON26411 SEVn_TMON26412 SEVn_TMON26413 SEVn_TMON26414 SEVn_TMON26415 SEVn_TMON26416 SEVn_TMON26417 SEVn_TMON26418 SEVn_TMON26419 Description MIN TERMTASK SQL RQ EVAL TERMTASK SQL R MAX TERMTASK DLI TI MIN TERMTASK DLI TI EVAL TERMTASK DLI T MAX TERMTASK DLI RQ MIN TERMTASK DLI RQ EVAL TERMTASK DLI R MAX TERMTASK UDB TI MIN TERMTASK UDB TI EVAL TERMTASK UDB T MAX TERMTASK UDB RQ MIN TERMTASK UDB RQ EVAL TERMTASK UDB R MAX TERMTASK FC TIM MIN TERMTASK FC TIM EVAL TERMTASK FC TI MAX TERMTASK FC REQ MIN TERMTASK FC REQ EVAL TERMTASK FC RQ MAX NON-TERM TASKS MIN NON-TERM TASKS EVAL NON-TERM TASKS MAX NON-TERM IOS MIN NON-TERM IOS EVAL NON-TERM IOS MAX NON-TERM PAGES MIN NON-TERM PAGES EVAL NON-TERM PAGES MAX NON-TERM STRG MIN NON-TERM STRG EVAL NON-TERM STRG MAX NON-TERM CPU MIN NON-TERM CPU EVAL NON-TERM CPU MAX NON-TERM DISP MIN NON-TERM DISP EVAL NON-TERM DISP MAX NON-TERM SQL TI MIN NON-TERM SQL TI Tivoli Business Systems Manager TMON for CICS Release Notes 17

18 Name SEVn_TMON26420 SEVn_TMON26421 SEVn_TMON26422 SEVn_TMON26423 SEVn_TMON26424 SEVn_TMON26425 SEVn_TMON26426 SEVn_TMON26427 SEVn_TMON26428 SEVn_TMON26429 SEVn_TMON26430 SEVn_TMON26431 SEVn_TMON26432 SEVn_TMON26433 SEVn_TMON26434 SEVn_TMON26435 SEVn_TMON26436 SEVn_TMON26437 SEVn_TMON26438 SEVn_TMON26439 SEVn_TMON26440 SEVn_TMON26441 Description EVAL NON-TERM SQL T MAX NON-TERM SQL RQ MIN NON-TERM SQL RQ EVAL NON-TERM SQL R MAX NON-TERM DLI TI MIN NON-TERM DLI TI EVAL NON-TERM DLI T MAX NON-TERM DLI RQ MIN NON-TERM DLI RQ EVAL NON-TERM DLI R MAX NON-TERM UDB TI MIN NON-TERM UDB TI EVAL NON-TERM UDB T MAX NON-TERM UDB RQ MIN NON-TERM UDB RQ EVAL NON-TERM UDB R MAX NON-TERM FC TIM MIN NON-TERM FC TIM EVAL NON-TERM FC TI MAX NON-TERM FC REQ MIN NON-TERM FC REQ EVAL NON-TERM FC RQ 18 Version 1.5