Response Time Analysis (RTA) Reference...

Response Time Analysis (RTA)Reference ManualOMEGAMON II® for IMS

Version 510

GC32-9269-00

March 2002

Candle Corporation201 North Douglas Street

El Segundo, California 90245-9796

2 OMEGAMON II for IMS Response Time Analysis (RTA) Reference Manual V510

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/PERFORMER, AF/REMOTE, Availability Command Center, Candle, Candle Command Center, Candle Direct logo, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management Workstation, Candle Technologies, CL/CONFERENCE, CL/SUPERSESSION, CommandWatch, CT, CT/Data Server, CT/DS, DELTAMON, eBA, eBA*ServiceMonitor, eBA*ServiceNetwork, eBusiness Institute, ETEWatch, IntelliWatch, IntelliWatch Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON/e, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAVIEW, OMEGAVIEW II, PQEdit, Solutions for Networked Applications, Solutions for Networked Businesses, and Transplex.Trademarks and service marks of Candle Corporation: Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED FACILITIES, Availability Management Systems, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle CommandPro, Candle CIRCUIT, Candle eDelivery, CandleLight, CandleNet, CandleNet 2000, CandleNet Command Center, CandleNet eBP, CandleNet eBP Access, CandleNet eBP Administrator, CandleNet eBP Broker Access, CandleNet eBP Configuration, CandleNet eBP Connector, CandleNet eBP File Transfer, CandleNet eBP Host Connect, CandleNet eBP Object Access, CandleNet eBP Object Browser, CandleNet eBP Secure Access, CandleNet eBP Service Directory, CandleNet eBP Universal Connector, CandleNet eBP Workflow Access, CandleNet eBusiness Assurance, CandleNet eBusiness Exchange, CandleNet eBusiness Platform, CandleNet eBusiness Platform Administrator, CandleNet eBusiness Platform Connector, CandleNet eBusiness Platform Connectors, CandleNet eBusiness Platform Powered by Roma Technology, CandleNet eBusiness Platform Service Directory, CandleNet Portal, CCC, CCP, CEBA, CECS, CICAT, CL/ENGINE, CL/GATEWAY, CL/TECHNOLOGY, CMS, CMW, Command & Control, Connect-Notes, Connect-Two, CSA ANALYZER, CT/ALS, CT/Application Logic Services, CT/DCS, CT/Distributed Computing Services, CT/Engine, CT/Implementation Services, CT/IX, CT/Workbench, CT/Workstation Server, CT/WS, !DB Logo, !DB/DASD, !DB/EXPLAIN, !DB/MIGRATOR, !DB/QUICKCHANGE, !DB/QUICKCOMPARE, !DB/SMU, !DB/Tools, !DB/WORKBENCH, Design Network, DEXAN, e2e, eBAA, eBAAuditor, eBAN, eBANetwork, eBAAPractice, eBP, eBusiness Assurance, eBusiness Assurance Network, eBusiness at the speed of light, eBusiness at the speed of light logo, eBusiness Exchange, eBusiness Institute, eBX, End-to-End, ENTERPRISE, Enterprise Candle Command Center, Enterprise Candle Management Workstation, Enterprise Reporter Plus, EPILOG, ER+, ERPNet, ESRA, ETEWatch Customizer, HostBridge, InterFlow, Candle InterFlow, Lava Console, MessageMate, Messaging Mastered, Millennium Management Blueprint, MMNA, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, NetGlue, NetGlue Extra, NetMirror, NetScheduler, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager, OMEGAMON Management Center, OSM, PC COMPANION, Performance Pac, PowerQ, PQConfiguration, PQScope, Response Time Network, Roma, Roma Application Manager, Roma Broker, Roma BSP, Roma Connector, Roma Developer, Roma FS/A, Roma FS/Access, RomaNet, Roma Network, Roma Object Access, Roma Secure, Roma WF/Access, Roma Workflow Access, RTA, RTN, SentinelManager, Somerset, Somerset Systems, Status Monitor, The Millennium Alliance, The Millennium Alliance logo, The Millennium Management Network Alliance, TMA2000, Tracer, Unified Directory Services, Volcano and ZCopy.Trademarks and registered trademarks of other companies: AIX, DB2, MQSeries and WebSphere are registered trademarks of International Business Machines Corporation. SAP is a registered trademark and R/3 is a trademark of SAP AG. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company Ltd. HP-UX is a trademark of Hewlett-Packard Company. SunOS is a trademark of Sun Microsystems, Inc. All other company and product names used herein are trademarks or registered trademarks of their respective companies.

Copyright © March 2002, Candle Corporation, a California corporation. All rights reserved. International rights secured.

Threaded Environment for AS/400, Patent No. 5,504,898; Data Server with Data Probes Employing Predicate Tests in Rule Statements (Event Driven Sampling), Patent No. 5,615,359; MVS/ESA Message Transport System Using the XCF Coupling Facility, Patent No. 5,754,856; Intelligent Remote Agent for Computer Performance Monitoring, Patent No. 5,781,703; Data Server with Event Driven Sampling, Patent No. 5,809,238; Threaded Environment for Computer Systems Without Native Threading Support, Patent No. 5,835,763; Object Procedure Messaging Facility, Patent No. 5,848,234; End-to-End Response Time Measurement for Computer Programs, Patent No. 5,991,705; Communications on a Network, Patent Pending; Improved Message Queuing Based Network Computing Architecture, Patent Pending; User Interface for System Management Applications, Patent Pending.

NOTICE: This documentation is provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions set forth in the applicable license agreement and/or the applicable government rights clause.This documentation contains confidential, proprietary information of Candle Corporation that is licensed for your internal use only. Any unauthorized use, duplication, or disclosure is unlawful.

Contents 3

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Application Trace Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16New OMEGAMON II Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Documentation Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19How RTA Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20What RTA Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Tracking Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Automatic Response Time Threshold Monitoring (ARSP) . . . . . . . . . . . . . . . . . . . . . . .26Response Time Monitor (RTM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Analysis by Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28RTA Input Technique. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29RTA Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Chapter 2. RTA Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33RTA Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Time Intervals (ICTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Moving Time Slots (ISET) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Chapter 3. End-to-End Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41How ETE Calculates Response Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42How ETE Measures Response Times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Displaying End-to-End Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Chapter 4. RTA Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Automatic Response Time Threshold Monitoring Facility (ARSP) . . . . . . . . . . . . . . . . .48

Chapter 5. RTA Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Time Interval Analysis (IRSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Time Slot Analysis (SRSP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Moving Time Slot Analysis (GRSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Response Time Monitor (RTM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Contents


Appendix A. Guide to Candle Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84Customer Support Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

List of Figures 5

FIGURE 1. Components of IMS Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22FIGURE 2. RTA Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30FIGURE 3. GRAPH Menu Option Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31FIGURE 4. IRTA Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34FIGURE 5. ICTL Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36FIGURE 6. ISET Command Format—Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38FIGURE 7. ISET Command Format—Group Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39FIGURE 8. Use of SCALE Parameter with ISET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40FIGURE 9. Use of WINDOW Parameter with ISET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

FIGURE 10. Calculating Response Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42FIGURE 11. NETW Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45FIGURE 12. End-to-End Response Time by VTAM Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46FIGURE 13. End-to-End Response Time by IMS Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46FIGURE 14. Commands to Set Up Transactions for ARSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49FIGURE 15. IRSP (Time Interval) Display Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53FIGURE 16. Time and CNT Minor Commands Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54FIGURE 17. Time Interval Response Analysis for All Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54FIGURE 18. Time Interval Response Analysis for a Transaction Group . . . . . . . . . . . . . . . . . . . . . .56FIGURE 19. Time Interval Analysis for All Items in Group PARTS . . . . . . . . . . . . . . . . . . . . . . . . . .56FIGURE 20. Average Response Time Analysis for a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57FIGURE 21. All Six Response Types Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57FIGURE 22. Transaction Counts Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58FIGURE 23. SRSP (Time Slot) Display Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59FIGURE 24. Time and CNT Minor Commands Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60FIGURE 25. Time Slot Response Analysis for All Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60FIGURE 26. Time Slot Response Analysis for All Items within a Group . . . . . . . . . . . . . . . . . . . . . . .61FIGURE 27. Scrolling Time Slot Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61FIGURE 28. Average Time Slot Response Analysis for a Group (Slot 5–8) . . . . . . . . . . . . . . . . . . . .62FIGURE 29. Average Time Slot Response Analysis for a Group (Slot 1–4) . . . . . . . . . . . . . . . . . . . .62FIGURE 30. Time Slot Analysis for All Six Response Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63FIGURE 31. Time Slot Response Analysis with Transaction Counts. . . . . . . . . . . . . . . . . . . . . . . . . .63FIGURE 32. GRSP (Moving Time Slot) Display Command Format . . . . . . . . . . . . . . . . . . . . . . . . .64FIGURE 33. TIME Minor Commands Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65FIGURE 34. Moving Time Slot Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66FIGURE 35. Moving Time Slot Response Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69FIGURE 36. Moving Time Slot Response Display with Scrolling . . . . . . . . . . . . . . . . . . . . . . . . . . . .69FIGURE 37. Graphical Display Showing all Six Response Types . . . . . . . . . . . . . . . . . . . . . . . . . . . .70FIGURE 38. Single Group Item Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71FIGURE 39. RMON Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72FIGURE 40. Typical RMON Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

List of Figures


FIGURE 41. XMON Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74FIGURE 42. Typical XMON Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75FIGURE 43. TMON Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76FIGURE 44. Typical TMON Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

List of Tables 7

Table 1. OMEGAMON II for IMS Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Table 2. Symbols in Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Table 3. RTA Default Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

List of Tables

Preface 9

Preface

IntroductionOMEGAMON II® for IMS (hereafter referred to simply asOMEGAMON II) is a software performance monitor for IMS systems.

This manual contains reference information about the response time analysis component (RTA) of OMEGAMON II. This manual is intended for users who are familiar with performance monitoring software and assumes you are familiar with OMEGAMON II, and know how to use its menus and commands.

In this manual, you will find information on the following topics:

n understanding how RTA works and what it measures

n controlling RTA data collection

n accessing RTA through the OMEGAMON II menu interface and the command interface

n displaying End-to-End Response Time Feature™ data

n invoking RTA exception analysis; the feature that issues a warning when average response time exceeds critical thresholds

n displaying RTA response time information

This manual does not include information about RTA data displayed in OMEGAMON II’s CUA™ interface. For information about all data displayed in the CUA Interface, see the OMEGAMON II for IMS User.

The RTA (Response Time Analysis) component gathers information constantly through an IMS hook about response time in which IMS is enabled.

Note that RTA uses commands to display the results.

P

About This Book


About This Book

Documentation set informationThe documentation listed in the following table is available for the Candle IMS Products. To order additional product manuals, contact your Candle Support Services representative

Table 1. OMEGAMON II for IMS Documentation Set

Document Number

Document Name Description

ET53-5586 End-to-End Response Time Feature (ETE) Reference Manual

Provides reference information about ETE commands, error messages, return codes, and sense codes.

IC51-6057 Installing Candle Products on MVS

Provides installation instructions and other installation considerations.

I251-5610 OMEGAMON II for IMS and OMEGAMON II for DBCTL Configuration and Customization Guide

Explains how to configure and customize OMEGAMON II and its user interfaces and components.

I253-6332 OMEGAMON II for IMS Realtime Commands Reference Manual

Describes in detail all of the features of the OMEGAMON II command interface.

I253-6333 OMEGAMON II for IMS Bottleneck Analysis Reference Manual

Provides reference information and descriptions of the features of the bottleneck analysis component.

I253-6336 OMEGAMON II for IMS Historical Component (EPILOG) Reference Manual

Provides a comprehensive description of the features of the historical component (EPILOG).

I254-6334 OMEGAMON II for IMS User’s Guide

Teaches the basics of using OMEGAMON II for IMS to manage realtime IMS environments.

I254-6335 OMEGAMON II for IMS Historical Component (EPILOG) User’s Guide

Teaches you, step-by-step, how to operate the historical component (EPILOG) reporter after installation.

I254-6337 OMEGAMON II for IMS Response Time Analysis (RTA) Reference Manual

Provides reference information and descriptions of the features of the response time analysis (RTA) component.

Preface 11

About This Book

Where to look for more informationFor more information related to this product, please see the

n technical documentation CD-ROM that came with your product

n technical documentation information available on the Candle Web site at www.candle.com

n online help provided with this and the other related products.

We would like to hear from youCandle welcomes your comments and suggestions for changes or additions to the documentation set. A user comment form, located at the back of each manual, provides simple instructions for communicating with the Candle Information Development department.

You can also send email to [email protected]. Please include “OMEGAMON II® for IMS Response Time Analysis (RTA) Reference Manual” in the subject line.

I299-6303 OMEGAMON II for IMS and OMEGAMON II for DBCTL Application Trace Facility

Provides user and reference information about the features of the Application Trace Facility (ATF) component.

I299-6338 OMEGAMON II for IMS and OMEGAMON II for DBCTL Transaction Reporting Facility

Provides user and reference information about the features of the Transaction Reporting Facility (TRF) component.

I299-6339 OMEGAMON II for IMS and OMEGAMON II for DBCTL IMS Console Facility

Provides a comprehensive description of the features of the IMS Console Facility (ICF) component.

W052-6238, W052-6239, W052-6240,W052-6356,W052-6357

Candle Products Messages Manual, Vol. 1 through 5

Provides reference summary information for all Candle product messages.

Table 1. OMEGAMON II for IMS Documentation Set

Document Number

Document Name Description

Adobe Portable Document Format



Printing this bookCandle supplies documentation in the Adobe Portable Document Format (PDF). The Adobe Acrobat Reader will print PDF documents with the fonts, formatting, and graphics in the original document. To print a Candle document, do the following:

1. Specify the print options for your system. From the Acrobat Reader Menu bar, select File > Page Setup… and make your selections. A setting of 300 dpi is highly recommended as is duplex printing if your printer supports this option.

2. To start printing, select File > Print... on the Acrobat Reader Menu bar.

3. On the Print pop-up, select one of the Print Range options forn Alln Current pagen Pages from: [ ] to: [ ]

4. (Optional). Select the Shrink to Fit option if you need to fit oversize pages to the paper size currently loaded on your printer.

Printing problems?The print quality of your output is ultimately determined by your printer. Sometimes printing problems can occur. If you experience printing problems, potential areas to check are:n settings for your printer and printer driver. (The dpi settings for both your

driver and printer should be the same. A setting of 300 dpi is recommended.)

n the printer driver you are using. (You may need a different printer driver or the Universal Printer driver from Adobe. This free printer driver is available at www.adobe.com.)

n the halftone/graphics color adjustment for printing color on black and white printers (check the printer properties under Start > Settings > Printer). For more information, see the online help for the Acrobat Reader.

n the amount of available memory in your printer. (Insufficient memory can cause a document or graphics to fail to print.)

For additional information on printing problems, refer to the documentation for your printer or contact your printer manufacturer.

Contacting AdobeIf additional information is needed about Adobe Acrobat Reader or printing problems, see the Readme.pdf file that ships with Adobe Acrobat Reader or contact Adobe at www.adobe.com.

Documentation Conventions

Introduction

http://www.adobe.com



Preface 13


Candle documentation adheres to accepted typographical conventions for command syntax. Conventions specific to Candle documentation are discussed in the following sections.

Panels and figures

The panels and figures in this document are representations. Actual product panels may differ.

Revision bars

Revision bars (|) may appear in the left margin to identify new or updated material.

Variables and literals

In examples of command syntax, uppercase letters are actual values (literals) that the user should type; lowercase letters are used for variables that represent data supplied by the user. Default values are underscored.

LOGON APPLID (cccccccc)

In the above example, you type LOGON APPLID followed by an application identifier (represented by cccccccc) within parentheses.

In ordinary text, variable names appear in italics.

Symbols

The following symbols may appear in command syntax:

Table 2. Symbols in Command Syntax

Symbol Usage

| The “or” symbol is used to denote a choice. Either the argument on the left or the argument on the right may be used. Example:

YES | NOIn this example, YES or NO may be specified.

[ ] Denotes optional arguments. Those arguments not enclosed in square brackets are required. Example:

APPLDEST DEST [ALTDEST]In this example, DEST is a required argument and ALTDEST is optional.

{ } Some documents use braces to denote required arguments, or to group arguments for clarity. Example:

COMPARE {workload} -REPORT={SUMMARY | HISTOGRAM}

The workload variable is required. The REPORT keyword must be specified with a value of SUMMARY or HISTOGRAM.

_ Default values are underscored. Example:

COPY infile outfile - [COMPRESS={YES | NO}]In this example, the COMPRESS keyword is optional. If specified, the only valid values are YES or NO. If omitted, the default is YES.

What’s New 15

What’s New

Chapter overviewVersion 510 of OMEGAMON II for IMS and OMEGAMON II for DBCTL significantly enhanced the Application Trace Facility. This version also provides several new functions, which broaden the overall functionality of OMEGAMON II for IMS and OMEGAMON II for DBCTL.

Chapter contentsApplication Trace Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16New OMEGAMON II Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Documentation Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

W

Application Trace Facility


Application Trace FacilityApplication Trace Facility (ATF) is a monitoring agent in OMEGAMON II for IMS and OMEGAMON II for DBCTL. In Version 510, ATF was significantly enhanced so that:

n Multiple ATF OMEGAMON Classic address space sessions can monitor the same IMS

n The IMS Monitor can run concurrently with these ATF sessions

n All environments for IMS, IMS DB/DC, IMS DC and IMS DBCTL are supported

n A site has external control of its operations

n IMS Version 7 DC Monitor is supported

n Concurrent Online TRF display and ATF display functions are supported

In the previous Version 500, ATF had a DETAIL parameter that could be set to LOW or HIGH. In Version 510, this parameter was removed and the function was separated to display this information on separate sets of panels:

n What used to be DETAIL=LOW in ATF V500 is now the Online TRF Display

n What used to be DETAIL=HIGH in ATF V500 is now new ATF panels

The changes made to ATF in this release are explained in detail in the for OMEGAMON II for IMS and OMEGAMON II for DBCTL Application Trace Facility Manual, Version 510. ATF’s online help has been upgraded to reflect these new features.

What’s New 17

New OMEGAMON II Functions

New OMEGAMON II FunctionsSeveral new functions were added to OMEGAMON II for IMS and OMEGAMON II for DBCTL. These functions are:

n Expanded generic IMS command support

n Enhanced VSAM buffer pool statistics

n Enhanced fast path buffer pool statistics

n Enhanced fast path statistics

n Enhanced operator assistance for fast path areas

n Additional data and sorting on IMS Message region fields

Documentation Changes


Documentation Changes

Online documentationWith version 510, Candle Corporation has moved OMEGAMON II for IMS manuals from IBM BookMaster to Adobe FrameMaker. This move was made to better enable us to address our customers’ needs by providing tools that enhance productivity.

One of the results of the move is that it is no longer possible to create BookManager versions of the OMEGAMON II for IMS manuals. However, the manuals remain available online in the Adobe PDF version on CD-ROM and are also available on the Candle Corporation website at www. Candle.com.

The documentation CD being provided with this release has robust and easy-to-use search capabilities. You can search for information in multiple volumes, multiple versions, and across products. The CD also provides easy setup of search indexes with a single click of the mouse.

If you want to order printed copies of the documentation, please contact your Candle Support Services representative.

Overview 19

Overview

Chapter overviewThe response time analysis component (RTA) of OMEGAMON II extends the capabilities of OMEGAMON II to include realtime tabular and graphic displays of transaction response times.

This document describes RTA; it mentions other OMEGAMON II components only when it is necessary to understand the interdependencies between them.

Note: RTA data is not available if you are running in a Database Control (DBCTL)-only environment. DBCTL systems do not have Data Communications (DC) support; therefore, there are neither transactions nor message queues. However, RTA will measure transaction response time in an IMS DB/DC system with DBCTL generated.

Since RTA is an event-driven collector and DEXAN is a sample-driven collector, the response time data values should not be directly compared to the degradation data values. To start RTA automatically when you start OMEGAMON II, follow the CICAT installation procedures in the OMEGAMON II for IMS and OMEGAMON II for DBCTL Configuration and Customization Guide. In the section on “Preparing the Startup Files”, specify “Autostart RTM Components” on the “Specify RTM Configuration Values” panel.

Chapter contentsHow RTA Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20What RTA Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Tracking Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Time interval analysis (IRSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Selected time slot analysis (SRSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Moving time slot analysis (GRSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Automatic Response Time Threshold Monitoring (ARSP) . . . . . . . . . . . . . 26Response Time Monitor (RTM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Analysis by Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28RTA Input Technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29RTA Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

1

How RTA Works


How RTA Works

IntroductionRTA captures detailed response time data from IMS. It analyzes this response time data and creates response time detail data for all transactions, including Fast Path transactions. RTA then places the detail data in summary buckets and reports it in user-specified groups. The OMEGAMON II for IMS Realtime Commands Reference Manual describes how to specify these groups. You can also analyze response times for transactions which are processed by message-driven BMP applications.

IRTA commandThe IRTA command does not modify the RMON command. These options have been added to the IRTA command:

n BMPXON: This excludes all BMP data from generated reports. Note that this is the default.

n BMPOFF or NMSXOFF: This includes all BMP data in generated reports.

n NMSXON: This includes all message-driven BMP data in the generated reports, while excluding all other BMP data.

Note: If more than one of these options is coded, the first one becomes active. The system ignores the others.

Overview 21

What RTA Measures

What RTA Measures

IntroductionRTA measures queuing and service times within IMS and end-to-end response time. Response time within IMS is the time it takes IMS to acknowledge an input message from the teleprocessing network and initiate a response. End-to-end response time is measured as the time from when a user presses Enter until a response appears on the screen. The End-to-End Response Time Feature feature is described in “End-to-End Response Time” on page 41. This chapter and “RTA Data Collection” on page 33 focus on response time within IMS.

StagesA typical IMS transaction proceeds through the following stages:

1. The communications network receives the input message text from a node (terminals, for example).

2. The message queue stores the message for subsequent processing until all necessary resources are available to process the transaction.

3. Other messages may be added to the input message queue during the processing of transactions by application programs.

4. When resources are available, an application program is scheduled to process the messages for this transaction. The application program issues a DL/I message Get Unique (GU) call using the I/O PCB to receive the input message text from the message queue.

5. During application processing, output messages are prepared for various system destinations. Some of these are directed to other transactions within the system. These go to the input message queue (item 3 above). The remainder go to communications destinations (for example, terminals) within the network. The message queue also stores these output messages.

6. After the application program completely processes the transaction, IMS takes the output messages from the message queues for delivery to final destinations. Output queue times can be lengthy if the network or user is not immediately ready for the message.

7. Some time later, the user, system device (printer), or another system receives these messages.

8. Finally, IMS purges the output message from the system.Figure 1 on page 22 shows the components of response time for typical IMS transaction as described above. RTA also supports miscellaneous variation of these components.

What RTA Measures


FIGURE 1. Components of IMS Response Time

RTA response time componentsThe RTA response time components are as follows:

Input Queue Time (I) Time an input message sent by a communications input device (terminal) spent on the input queue before delivery to an application program (from stage 2 to 4). This includes queue time, scheduling, program load, and program initialization.

Program Input Queue Time (PI)

Time an input message, that did not initiate from a terminal (for example, program to program switch or MSC link), spent on the input queue before delivery to an application program (from stage 3 to 4). This includes queue time, scheduling, program load, and program initialization. PI is not a subset of I.

Processing Time (P) Time during which an application program processes the message. This begins with the program message Get Unique, and ends with another Get Unique, program termination, sync point, application program abend, or a cancellation of the message.

+------------------+ | | 1 Comm. 2 Comm. 3 Pgm. 4 Appl. |5 Appl. 6 Output 7 Output 8 Output Msg. Msg. Msg. Deqs | Enqs. Read From Recd. Msg. Arrival Queued Queued Msgs(GU) | Output Queue By User Purged | (ISRT)|---------|--------|--------|----------|----------|----------|---------|--------| | | |<--------------->| Input Queue Time (I) |<------>| Program Input Queue Time (PI) |<-------->| Processing Time (P) |<--------------------------->| Response Time 0 (R0) (Application) |<------------------>| |<--------->| Output Queue Time (O) |<--------------------------------------->| Response Time 1 (R1) (Host) |<------------------------------>|

Overview 23

What RTA Measures

The abbreviations in parentheses (I, PI, P, R0, O, and R1) are used to select the type of response time component for analysis within the IRSP, SRSP, GRSP, and ISET commands which “RTA Data Collection” on page 33 describes.

Response Time 0 (R0) Internal systems application response time for the transaction. It is the sum of I (or PI) and P (from stage 2 to 5).

Output Queue Time (O) Amount of time an output message spent waiting on the output message queue. This begins with output message insert and ends with a communications Get Unique.

Response Time 1 (R1) Total host response time for the transaction. It is the sum of Input Queue Time (or Program Input Queue Time), Processing Time, and Output Queue Time. Response Time 1 is usually greater than Response Time 0. However, R1 response times are not recorded for a transaction if it does not have an Output Queue Time component. Transactions with express output messages (messages that are issued before Sync Point) can have a Response Time 1 value which is less than the Response Time 0 value, since such transactions issue a response before transaction completion. R1 times are not produced for non-recoverable inquiry transactions because the LTERM ID of the originating terminal is not available. These are defined as INQUIRY= (YES,NORECOV) on the TRANSACT macro (from stage 2 to 6).

RTA does not produce R1 times for transactions returning a message to a terminal other than the originator.

Tracking Response Time



IntroductionRTA breaks response time down in the following ways:

n Time interval analysis (IRSP)

n Selected time slot analysis (SRSP)

n Moving time slot analysis (GRSP)

RTA displays the response time of transactions as they occur, rather than hours later as through postprocessing programs. This provides you with real time feedback on the effects of tuning measures, system modifications, and changing workloads.

Time interval analysis (IRSP)The conventional way to analyze response time is background reporting, hours after the problem occurred. This background method makes it difficult to identify the IMS resources associated with response time degradation. Furthermore, if you cannot correct problems in real time, response time continues to be poor during the online period.

Time interval analysis shows short-term response time problems as they happen. You can investigate these further in real time with the realtime performance (OMEGAMON®) and bottleneck analysis (DEXAN) components of OMEGAMON II. The IMS performance analysts can then search among many possible causes for poor response time. Once the cause is determined, OMEGAMON II features can be used to correct the problem immediately.

The RTA short-term analysis presents response times over three distinct short-term intervals. For example, you can display the response time for 5, 10, and 30 minute intervals. You can vary the duration of the short-term intervals. The second interval must always be a multiple of the first, and the third must be a multiple of the second. RTA selects time interval displays by groups or group items. A minor command, TIME, selects which response component (for example, processing time) to display. RTA presents this data in a table.

Overview 25


Selected time slot analysis (SRSP)Time slot analysis lets you monitor response time from a long-term perspective. RTA retains response time data for selected time slots during the day and displays it upon request. RTA can monitor up to 48 different time slots during the day. For example, to display the response time of a transaction between 6:00 AM and 9:00 AM, you can set up a time slot to cover this period. Later in the day, you can use the SRSP command to view the response time data that was captured for the 6:00 AM–9:00 AM slot. Time slots cannot overlap, but you can leave gaps during the day for low volume periods if you wish. RTA presents this data in a table.

Moving time slot analysis (GRSP)The moving time slot analysis presents a graphic display of short-term (the last 10 minutes) response time data. Two kinds of items display:

n fixed items, the critical groups or group items which you want to monitor continually

n dynamic items, monitored only when the items exceed their response time thresholds

You can also use graphic displays to identify whether the principal cause for response time delay is input queueing, processing, or output queuing. The response display shows the current minute and the prior nine minutes. Each minute prior to the current minute results shift to the left. At the top of each graphical partition, RTA shows the response time numerically for the past minute. Asterisks automatically appear under any item which exceeds thresholds you define.

Automatic Response Time Threshold Monitoring (ARSP)


Automatic Response Time Threshold Monitoring (ARSP)

PurposeThe ARSP analysis is part of the IM (IMS internal) group of OMEGAMON II exceptions. ARSP continually monitors response time (I, PI, P, R0, O, R1) against critical installation thresholds and generates a warning message to the terminal indicating the problem. This integrates the power of exception analysis with RTA. You can also use ARSP with the exception logging facility (XLF) and the automatic screen facility (ASF), to automatically call screens containing IMS and MVS commands which correct the situation automatically.

Overview 27

Response Time Monitor (RTM)


PurposeThe response time monitor (RTM) lets you monitor all transactions in IMS, regardless of the group definitions. It reports transactions and logical terminals with the poorest response time.

RTM identifies the transactions and terminals you probably want to include in group definitions.

RTM analyzes transactions and terminals with the poorest response times during short-term intervals and displays the information in a table. There are several parameters you can adjust to specify the number of transactions you want to display on a screen, the time interval, and what type of monitoring you want (fixed or moving window). For example, you can request that RTA display the 20 transactions with the poorest response time within a continually moving 10-minute interval.

Since RTM is independent of group definitions, changes to these do not affect RTM operation. (In order to update groups, you need to turn RTA collection off with the IRTA OFF command, as “RTA Data Collection” on page 33 describes.

RTM functionsRTM has two functions:

n data collection and analysis (activated by the RMON command, as “Response Time Monitor (RTM)” on page 72 describes)

n data display (activated by the XMON command for transactions, and the TMON command for logical terminals, as “Response Time Monitor (RTM)” on page 72 describes)

You must start data collection and analysis before the display commands are operational.

Analysis by Groups


Analysis by Groups

IntroductionTime intervals and time slots provide a method of tracking response time dynamically. You can also assign specific transaction sets to groups. These may be critical transactions, PSBs, transaction classes, or CNTs (terminals). This technique can be used to track response time by application, or to monitor transactions that may have had performance problems in the past. RTA shares the group definition concept with the OMEGAMON and DEXAN components of OMEGAMON II. See the OMEGAMON II for IMS. Realtime Commands Reference Manual for details on using group selection.

What is a group?A group is either a transaction, a logical terminal, or a node related group. A transaction group contains transactions and PSBs only. A logical terminal group contains logical terminals (Lterms) only. A node group contains nodes only. Group types cannot be mixed. For example, you cannot define a node in a group that already has transactions defined.

Groups for RTA monitoringThere are two special groups for RTA monitoring: SYSTEM and OTHER. SYSTEM is a composite of response time for all transactions. OTHER is a composite of response time for transactions not being monitored within any specific group. For brevity, SYSTEM and OTHER do not appear in this document’s examples. However, they will appear in actual displays.

Overview 29

RTA Input Technique

RTA Input Technique

Processing recordsRTA receives its input from IMS log records. To gain controlled access to these records, RTA dynamically alters the call address of the IMS physical logging routine. RTA scans the physical log buffers within the RTA address space in parallel with the IMS physical logging routine. If any error occurs, RTA recovers and restores the address of the IMS physical logging routine so that the RTA routine will not be called again. After recovery, processing resumes within the IMS physical logging routine.

RTA Menus


RTA Menus

Accessing RTAYou can access RTA through the OMEGAMON II menu interface. To do so, select option R, RESPONSE TIME, from the OMEGAMON II Main Menu. Figure 2 on page 30 shows the RTA Menu.

FIGURE 2. RTA Menu

The options on the menu allow you to choose from one of the ways RTA groups response time information. For example, option B, GRAPH, provides a graphical display of response time data. Figure 3 on page 31 displays the GRAPH menu option screen.

________________ ZRTI VTM OIDIRIEI /C IMSA 3/6/02 15:28:54 B > Help PF1 Exit PF3 > Enter a selection letter on the top line. ================================================================================ > Response Time Menu _ A PROBLEMS ........... Transactions and LTERMs with longest response times _ B GRAPH .............. 10-minute historical graph _ C TIME OF DAY ........ Response time by time-of-day slots _ D INTERVALS .......... Response time by recent time intervals _ E CONTROL ............ Start/stop RTA and control data collection _ F OPTIONS ............ Display time slot and group definitions _ G END-TO-END ......... End-to-end response time ================================================================================

Overview 31

RTA Menus

FIGURE 3. GRAPH Menu Option Screen

For detailed information about the RTA displays refer to “RTA Displays” on page 51.

You can also change the way RTA collects data and set RTA exceptions through the OMEGAMON II menu system. “RTA Data Collection” on page 33 explains in detail how to control RTA monitoring. RTA exceptions are discussed in “RTA Exceptions” on page 47.

________________ ZRGRAF VTM OIDIRIEI /C IMSA 2/26/02 15:29:15 B > Help PF1 Back PF3 Up PF7 Down PF8 ================================================================================ > 10-Minute Historical Graph > To display response time information about a specific group, type the group > number directly after GRSP below and press ENTER. > To display information about all of the response time components, type AL > directly after TIME and press ENTER. GRSP >> Transaction Group totals display << time | BILLING | PARTS | MAIL |>SHIPPING<|>INVOICE <|>SYSTEM <|+ | 0.8 | 0.4 | 0.0 | 0.0 | 0.6 | 0.4 |+ |==========+==========+==========+==========+==========+==========++ 1.0| | | | | | |+ .9| | | | |----------| |+ s .8| *| | | | | |+ e .7|---------+| | | | | |+ c .6| *| * | | | *| * |+ o .5| * *| * |-----+----| | * * *| ** * |+ n .4| * *|--+-++---+| * | * | * * *|-++----+-+|+ d .3| ** *| ***** *| * ** | ** |** **** *|**** ***|+ s .2| ** **| ****** **| ** ** * |-++---+---|******* **|***** ****|+ .1| *****|**********|********* |*** ** |**********|**********|+ +----------+----------+----------+----------+----------+----------++ ***** ***** ***** ***** *****+ min -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 ================================================================================

RTA Menus


RTA Data Collection 33

RTA Data Collection

Chapter overviewThe standard installation procedure starts RTA automatically when OMEGAMON II. starts. You can also use the IRTA command within OMEGAMON II. to control RTA monitoring. When RTA starts, it automatically activates data collection. RTA displays response time information when you enter the associated major and minor commands. To modify its data collection parameters, you need to deactivate RTA. Afterwards, reactivate RTA to start data collection with the modified data collection parameters. Figure 4 on page 34 shows the format of the IRTA command.

Chapter contentsRTA Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Time Intervals (ICTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Moving Time Slots (ISET) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

2

RTA Command


RTA Command

RTA optionsThe IRTA command does not modify the RMON command. The following have been added as options to the IRTA command:

n BMPXON: This excludes all BMP data from generated reports. Note that this is the default.

n BMPOFF or NMSXOFF: These include all BMP data in generated reports.

n NMXSON: This includes message-driven BMP data in generated reports while excluding all other BMP data.

Note: If more than one of these options is coded, the first one will become active. The system ignores others.

FIGURE 4. IRTA Command Format

RTA default parametersThe $OIRTA macro in the KOIGBL module contains the default parameters for RTA data collection. Table 3: RTA Default Parameters on page 35 shows the default parameters.

>Help PF1 Back PF3 Up PF7 Down PF8================================================================== Start/Stop RTA and Control Data Collection >To control RTA data collection, select an action and remove the >>preceding IRTA below the description of that action. >Start RTA data collection:>IRTA START>>Stop RTA collection and delete the RTA collector>and buckets from the system:>IRTA STOP>>Clear RTA data collection buckets:>IRTA RESET================================================================


RTA Command

When you first use RTA, we recommend that you start with the default parameters. After gaining some experience, you will be in a better position to modify the defaults to match your requirements.

To change the default parameters, change the $OIRTA macro of the global data area module KOIGBL. (The Configuration and Customization Guide describes how to do this.) You can also change the parameters interactively (except the time slots) for the duration of your session. “Time Intervals (ICTL)” on page 36 and “Moving Time Slots (ISET)” on page 38 describe how to do this.

Table 3. RTA Default Parameters

Parameter Default Range

Time Intervals 15,30,60 1-999 minutes

Moving Time Slots Scale 2 seconds 1-999 seconds

Moving Time Slots Window

10 minutes 1-10 minutes

Time Slots (up to 48 permitted)

0000-0800

0800-0900

0900-1000

1000-1030

1030-1100

1100-1130

1130-1200

1200-1300

1300-1400

1400-1430

1430-1500

1500-1530

1530-1600

1600-1700

1700-1800

1800-1900

1900-2000

2000-2400

0-2400

Time Intervals (ICTL)



ICTL commandYou can change the default time intervals interactively when the data collector is not active. To do this, first stop the data collector with the IRTA OFF command. Then issue the ICTL immediate command, which has the following format:

FIGURE 5. ICTL Command Format

The second argument must be a multiple of the first, and the third argument must be a multiple of the second. If you omit any argument, ICTL uses its current value.

Below are some typical uses of the ICTL command.

n To display the current time intervals, enter:

ICTL?

RTA responds:

ICTL? 005,015,060

RTA redisplays the question mark (?). To actually update the interval values, remove the question mark.

n To change the time intervals, enter:

ICTL 10,20,60

RTA responds:

>ICTL 010,020,060

+ >> processing complete <<

RTA places a comment symbol (>:) in column 1 in front of the ICTL command to prevent re-execution if it changes the interval values.

ICTLa x,y,z - time intervals | | | %-> - up to three arguments specified in minutes | | %---> ? - show current values



If the RTA data collector is active, RTA displays an error message and ignores the ICTL command. If the input values are invalid, RTA displays an error message. For example:

ICTL 005,015,055

+ >> 055 is not a multiple of 015 -- error <<

ICTL 1,2,3000

+ *

+ >> input greater than 999 in column marked above <<

ICTL

+ >> enter new time intervals above <<

To correct the erroneous entry, type the correct value on the screen and press ENTER (if in a non-dedicated mode). When you finish changing the parameters, restart the data collector with the IRTA ON command.

The ICTL command controls the parameters the IRSP display command uses. To see how IRSP works, see “Time Interval Analysis (IRSP)” on page 53. The first time interval also controls the ARSP exception. For reasons of data significance, this exception analyzes data from the second half of the interval. See “RTA Displays” on page 51 for details.

Moving Time Slots (ISET)



ISET commandYou can change the default moving time slots scale and window interactively, even when the data collector is active. To do this, issue the ISET immediate command. If you want to change defaults of a group, refer to Figure 6 on page 38. If you want to change the defaults of a group item, refer to Figure 7 on page 39. When you change the defaults for a group item, you affect the item in all groups in which it appears.

FIGURE 6. ISET Command Format—Groups

xISETyy GRP=xxxxxxxx NAME=xxxxxxxx THRESH=nnnn FIX=YES/NO EXPTHR=nnnn| | | | | | || | | | | | %-> set critical| | | | | | threshold for| | | | | | average response| | | | | | time as the ARSP| | | | | | exception displays| | | | | | (0-9999 tenths of| | | | | | a second)| | | | | || | | | | %-> set group as fixed| | | | | for display or not| | | | || | | | %-> set threshold for dynamic display| | | | transactions (0-9999 tenths of| | | | seconds). If nnnn=0, this group| | | | is not eligible for dynamic| | | | display.| | | || | | %-> new name for group. Can include| | | blanks but must be enclosed in| | | single quotes.| | || | %-> group name (1&ndash.8 characters enclosed in single quotes)| | or group number| || %-------> response type: I - Input Queue Time| PI - Program Input Queue Time| P - Processing Time| O - Output Queue Time| R0 - Response Time 0| R1 - Response Time 1| AL - all of the above response types|%------> L - list current parameter values



FIGURE 7. ISET Command Format—Group Items

The ISET command controls parameters which RTA uses with the GRSP display commands and the ARSP exception. To see how GRSP works, see “Moving Time Slot Analysis (GRSP)” on page 64. To see how ARSP works, see “RTA Exceptions” on page 47.

You can optionally specify a SCALE value with ISET, which is the number of seconds of response time translated into the vertical axis of the time graph GRSP displays. RTA divides the graph into ten points, each 1/10 of the scale height.

xISETyy item=xxxxxxxx THRESH=nnnn FIX=YES/NO EXPTHR=nnnn| | | | | || | | | | %-> set critical threshold| | | | | for average response| | | | | time as the ARSP| | | | | exception displays| | | | | (0-9999 tenths of| | | | | a second)| | | | || | | | %-> set group as fixed| | | | for display or not| | | || | | %-> set threshold for dynamic display| | | transactions (0-9999 tenths of| | | seconds). If nnnn=0, this group| | | is not eligible for dynamic| | | display.| | || | %-> TRAN=xxxxxxxx (transaction name)| | TERM=xxxxxxxx (LTERM name)| | PSB=xxxxxxxx (PSB name)| | CLASS=nnn (transaction class)| || %-------> response type: I - Input Queue Time| PI - Program Input Queue Time| P - Processing Time| O - Output Queue Time| R0 - Response Time 0| R1 - Response Time 1| AL - All of the above response types|%------> L - list current parameter values D - mark group item ineligible for display (sets FIX=NO and THRESH=000)



FIGURE 8. Use of SCALE Parameter with ISET

You can also optionally specify a WINDOW value with ISET. The WINDOW value controls the display of dynamic transactions that exceed their threshold value. The value nn refers to the last 1-10 minutes that RTA uses to check if the transaction exceeded its threshold. WINDOW=1 shows those dynamic transactions whose response exceeded their threshold during the current minute (numbered zero on the display). WINDOW=10 shows those dynamic transactions which have exceeded their threshold during any one of the last 10 minutes.

FIGURE 9. Use of WINDOW Parameter with ISET

You must enter the SCALE and WINDOW parameters separately.

xISETyy SCALE=nnn <set display scale (1-999 seconds)>| || %-------> response type: I - Input Queue Time| PI - Program Input Queue Time| P - Processing Time| O - Output Queue Time| R0 - Response Time 0| R1 - Response Time 1| AL - All of the above response types|%------> L - list current parameter values

xISETyy WINDOW=nn <set window for dynamic transaction| | threshold having been exceeded (1-10 minutes)>| || +-------> response type: I - Input Queue Time| PI - Program Input Queue Time| P - Processing Time| O - Output Queue Time| R0 - Response Time 0| R1 - Response Time 1| AL - All of the above response types|+------> L - list current parameter values

End-to-End Response Time 41

End-to-End Response Time

Chapter overviewThe RTA End-to-End Response Time (ETE) feature helps you identify whether a response problem lies within a network or the host system by tracking End-to-End Response Time Feature.

Chapter contentsHow ETE Calculates Response Times. . . . . . . . . . . . . . . . . . . . . . . . . . . . 42How ETE Measures Response Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Displaying End-to-End Response Time. . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3

How ETE Calculates Response Times



What is measured?End-to-end response time is the amount of time between pressing a key (ENTER, PF1 through PF24, PA1, PA2, PA3, or CLEAR) and receiving a response at your terminal. If you started a stopwatch when you pressed ENTER, and you then stopped the watch when the terminal received the application’s first response to your request, the stopwatch time would be the End-to-End Response Time Feature of that request.

From its position inside VTAM®, ETE can measure the time between SNA events. The stopwatch starts when the request flows through VTAM toward the application. It stops when VTAM receives the definite response from the terminal controller. Only one portion of End-to-End Response Time Feature cannot be captured directly and must be estimated; it is the time before the user’s request reaches VTAM, (t1 minus t0) in Figure 10 on page 42.

FIGURE 10. Calculating Response Times



In most cases, the time a request takes to flow from the terminal to VTAM (t1 minus t0) approximately equals the amount of time the definite response takes to flow from the controller to VTAM (t6 minus t5). This is true because all definite responses and most requests contain little data. Therefore, ETE calculates End-to-End Response Time Feature as (t6 minus t1).

How ETE Measures Response Times


How ETE Measures Response Times

IntroductionTo measure End-to-End Response Time Feature, RTA places a data collection component inside one of the ACF/VTAM™ SNA layers. In this location the monitor can time all SNA traffic handled through VTAM.

ProtocolsRTA captures End-to-End Response Time Feature for applications that use either of the following protocols.

The ETE feature is subject to the following restrictions:

n It requires VTAM Version 3.

n It will only monitor VTAM SNA devices.

n It will provide the most meaningful results if IMS terminals are placed in response mode.

Definite response The application asks the terminal controller to respond to transmitted data by indicating whether or not the transmission was successful. The application must then wait for the controller’s response before continuing. Because the controller responds to all transmissions, End-to-End Response Time Feature is relatively easy to monitor under the definite response protocol.

Exception response The application asks the controller to respond only if an error occurs during transmission of data to the terminal. Because End-to-End Response Time Feature can be measured only for transactions that require a response from the controller, the response time monitor must turn on definite response for applications that use the exception response protocol. Once it has measured the response time, the monitor discards the definite response before it flows to the application. Thus, the application never sees the definite response and is not even aware that a definite response has been elicited.


Displaying End-to-End Response Time


NETW commandThe NETW command enables you to display End-to-End Response Time Feature for a node or group, broken down by host and network times.

The format of the NETW command is shown in Figure 11 on page 45.

FIGURE 11. NETW Command Format

The result of this command is a graph of network and host response times, grouped by resource name. End-to-end response time is displayed as a combined value of network and host response times. The display also includes a count of message events between the node and IMS. A message event represents a flow of data from VTAM to the node or from the node to VTAM. This count of message events will most likely exceed the actual number of transactions entered from a node. The message count is useful in determining if the host and network response times are based on a small or large amount of message traffic.

The following are some examples of NETW commands:

NETW NODE Displays all nodes, beginning with the first node in the collection buckets.

NETW GROUP=PAYROLL Displays End-to-End Response Time Feature information for the PAYROLL group.

NETW2 NODE=L610A11 Displays two nodes: L610A11 and the node that follows it in the collection buckets.

NETW5 GROUP Displays five groups, beginning with the first group in the collection buckets.

NETW3 NODE=L610* Displays the first three nodes beginning with L610. If there are only two nodes that begin with L610, only those two will display. Figure 12 on page 46 shows an example of displaying End-to-End Response Time Feature by VTAM node.

NETWnn NODE=cccc GROUP=cccc | | | | | %-> specifies a NODE only group for which | | to display &ETE. information | | | %-> specifies a VTAM node for which to | display &ETE. information | %-> number of entries to display. If this number is omitted, all entries are displayed



FIGURE 12. End-to-End Response Time by VTAM Node

In this example, the first 12 nodes beginning with L610 are displayed. Host times are represented by H; network times are represented by +. End-to-end response times are calculated by adding host and network times for each node.

Figure 13 on page 46 shows an example of displaying End-to-End Response Time Feature by IMS groups.

FIGURE 13. End-to-End Response Time by IMS Groups

In this example, all groups in the collection buckets are displayed. Host times are represented by H; network times are represented by +. End-to-end response times are calculated by adding host and network times for each group.

________________ NETW VTX LOG OIDIRIEI /C I51A 01/02/97 7:24:28 42 B=============================================================================== NETW12 NODE=L610*+ Resp. Time Event ETE -----End-to-End Response----+ NODE HOST NET Count Time 0s---2----4----6----8----10+ L610A18 1.0s 4.0s 100 5.0s|HHH++++++++++ |+ L610A83 .8s 4.2s 1542 5.0s|HH+++++++++++ |+ L610A84 1.8s 2.2s 817 4.0s|HHHH++++++ |+ L610A85 .8s 5.2s 20 6.0s|HH+++++++++++++ |+ L610B10 .2s 1.8s 19927 2.0s|H++++ |+ L610B83 .8s 1.2s 392 2.0s|HH+++ |+ L610B84 .8s 1.4s 1019 2.2s|HH++++ |+ L610B85 .2s 2.0s 209 2.2s|H+++++ |+ L610C18 1.8s 6.0s 285 7.8s|HHHH+++++++++++++++ |+ L610C83 .8s 7.2s 347 8.0s|HH++++++++++++++++++ |+ L610C84 1.0s 6.8s 1487 7.8s|HHH++++++++++++++++ |+ L610C85 1.8s 5.6s 21 7.4s|HHHH++++++++++++++ |+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+ Avg. End-to-End Response Time 5.0s (Elapsed time= 1:05 MN)

________________ NETW VTX LOG OIDIRIEI /C I51A 01/02/97 7:25:06 42 B=============================================================================== NETW GROUP+ Resp. Time Event ETE -----End-to-End Response----+ Group HOST NET Count Time 0----2----4----6----8----10+ BOSTON 1.0s 4.0s 287 5.0s|HHH++++++++++ |+ CHICAGO .8s 2.2s 1297 3.0s|HH+++++ |+ DALLAS 1.8s 8.0s 837 9.8s|HHHH++++++++++++++++++++ |+ DENVER .2s 2.0s 20982 2.2s|H+++++ |+ PHOENIX .8s 1.6s 45 2.4s|HH+++++ |+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+ Avg. End-to-End Response Time 4.5s (Elapsed time= 2:23 HR)

RTA Exceptions 47

RTA Exceptions

Chapter overviewThe automatic response time threshold monitoring facility (ARSP) integrates OMEGAMON II’s exception analysis feature with RTA. The ARSP exception is part of the IM (IMS Internal) group of exceptions.

Chapter contentsAutomatic Response Time Threshold Monitoring Facility (ARSP) . . . . . . . 48

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4

Automatic Response Time Threshold Monitoring Facility (ARSP)



IntroductionThe ARSP analysis issues a warning when average response time exceeds critical installation thresholds. ARSP can display a maximum of 25 exception messages per screen; therefore, you may want to be somewhat selective about the items whose response times you monitor. The purpose of ARSP is to immediately notify operators when IMS exceeds critical thresholds, and it frees them from the need to continually monitor an RTA display terminal.

ProcessingARSP requires the following:

n RTA must be active and collecting data (IRTA ON command).

n Exception analysis must be active.

ARSP analyzes average response time data within the first time interval the ICTL immediate command defines. In order to collect a significant amount of data, ARSP waits until the second half of the interval before it analyzes any data. See “Time Intervals (ICTL)” on page 36 for details on how to alter the first time interval.

ARSP examines response time components of groups or group items (transactions, logical terminals, PSBs, and classes). For more information about how to assign groups, see the OMEGAMON II for IMS Realtime Commands Reference Manual.

ARSP analyzes each response time component (I, PI, P, R0, O, R1) against a threshold, independent of the other components. You specify the response time component with the ISET command. “Moving Time Slots (ISET)” on page 38 describes the ISET command.

End-to-end response time is not monitored by the ARSP exception.

You can define the ARSP exception threshold permanently with the EXPTHR=nnnn parameter of the $OIGROUP macro in the KOIGBL module, where nnnn = 1–9999 is response time in tenths of a second. (See the OMEGAMON II for IMS and OMEGAMON II for DBCTL Configuration and Customization Guide for more information about the $OIGROUP macro.) Or you can change this threshold dynamically with the EXPTHR=nnnn parameter of the ISET command. See “Moving Time Slots (ISET)” on page 38 for details.

Figure 14 on page 49 shows how to set up transactions so that they can appear in the ARSP exception analysis. First make sure that RTA is off (IRTA OFF).

RTA Exceptions 49


FIGURE 14. Commands to Set Up Transactions for ARSP

The IRTA command does not modify the RMON command. The following have been added as options to the IRTA command:

n BMPXON: This excludes all BMP data from generated reports. Note that is the default.

n BMPOFF or NMSXOFF: These include all BMP data in generated reports.

n NMSXON: This includes message-driven BNP data in generated reports while excluding all other BMP data.

Note: If more than one of these options is coded, the first one becomes active. The system ignores the others.

This example assigns transaction PART to group 1 with the SETG command. OMEGAMON II inserts an L when the assignment is complete. (If you do not want the group to be eligible for dynamic display, set the thresholds to zero.)

In this example, the ISET command assigns a threshold of 10 tenths of a second (or 1 second) to each response time component of transaction PART with the EXPTHR parameter and the AL suffix. RTA inserts an L when the assignment is complete.

Next the IRTA ON command activates RTA. RTA could not accept the group assignment (SETG) while it was active. The first line of the XIMS display is the ARSP analysis. It indicates that transaction PART has been waiting in the input queue for 2.8 seconds (average). All other response time components were under the threshold of 1 second and consequently do not appear. ARSP waits until the second half of the first time interval (set with ICTL) to display so that it can gather a significant amount of data.

>Help PF1 Back PF3 Up PF7 Down PF8 Zoom PF11>>For an explanation of an exception, place the cursor on the exceptionname and press PF11.> ================================================================================ LXIMS OMEGAMON Exception Analysis + Average INPUT QUEUE TIME for TRANS PART is 2.8 secs. + Message Dequeue rate = 2.13/second (Low) + Message Format Services Pool utilization = 100.00% + Message Format Services Pool: Largest free block = 0 bytes + Control Region: I/O Rate = 50.00/second (High) =======================================================================

RTA Displays 51

RTA Displays

Chapter overviewThis chapter describes the commands you can use to display the information gathered after you have issued the IRTA command to begin data collection. “RTA Data Collection” on page 33 explains how to start and control data collection.

Response time information is grouped in these ways:

Chapter contentsTime Interval Analysis (IRSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

All groups plus averages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Transaction group analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Group averages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Response type AL option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Transaction counts (CNT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Time Slot Analysis (SRSP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59All groups plus averages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60All items within a group plus averages . . . . . . . . . . . . . . . . . . . . . . . . 61Transaction group averages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Response type AL option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Transaction counts (CNT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Moving Time Slot Analysis (GRSP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Moving time slot examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Response type AL option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

time interval Displays response time information for three user-defined intervals.

time slot Displays response time data for a specified period (for example, 9:00 AM to 10:00 AM).

moving time slot Provides a graphical display of response time data.

response time monitor Displays transactions or terminals with the worst response time.

5


Response Time Monitor (RTM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Data analysis (RMON) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Data display for transactions (XMON). . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Data display for terminals (TMON) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

RTA Displays 53

Time Interval Analysis (IRSP)


IRSP commandThe IRSP command displays the time interval analysis. To control the intervals RTA displays, use the ICTL command as “Time Intervals (ICTL)” on page 36 describes. With IRSP you can display totals for all groups, all items within a specific group, or totals for a single group item.

FIGURE 15. IRSP (Time Interval) Display Command Format

To select specific groups for display, either enter the group number in the command argument field (nn in the example above), or use the GRP= keyword to specify the group’s number or name.

The minor command TIME displays response time information. The minor command CNT displays transaction count information. Figure 16 on page 54 shows the format of the TIME and CNT commands.

IRSPnn xxxxxxxx | | | %----> xxxxxxxx is either a group or group item, not both. | | GRP=group - Name or number of group to display. If you omit both | xxxxxxxx and nn, RTA displays all groups. | | group item - Group item for which data is to display. Specify | items as follows&gml. | TRAN=xxxxxxxx (transaction name) | TERM=xxxxxxxx (LTERM name) | PSB=xxxxxxxx (PSB name) | CLASS=nnn (transaction class) | | %-> nn - group number to display



FIGURE 16. Time and CNT Minor Commands Format

The following sections contain examples of time interval analysis.

All groups plus averagesTo display response times for all groups plus averages for each time interval, enter the following commands:

IRSP

TIMER1

These commands result in a display like this:

FIGURE 17. Time Interval Response Analysis for All Groups

xTIMEzzxCNTb&$BS./zz | || %-> response type: I - Input Queue Time| PI - Program Input Queue Time| P - Processing Time| O - Output Queue Time| R0 - Response Time 0| R1 - Response Time 1 (default display)| AL - All six response types listed above|%------> scrolling/average selection character&gml. (blank) display all groups/items and average A display averages only 0-9 scrolling value 0 - show 1st 10 groups/items 1 - show 2nd 10 groups/items . . 9 - show 10th 10 groups/items

(a) (b) IRSP | ID | (00:05) 00:04:50 | (00:15) 00:14:50 | (01:00) 00:44:50 | TIMER1|G=PARTS | 2.3 | 2.0 | 2.2 |+ |G=BILLING | 3.2 | 3.0 | 3.0 |+ |G=MAIL | 0.7 | 0.5 | 0.6 |+ | AVERAGES| 1.8 | 1.5 | 1.6 |+ | OTHER | 0.4 | 0.3 | 0.7 |+ | SYSTEM | 2.9 | 2.2 | 2.5 |:figcap.Time Interval Response Analysis for All Groups

RTA Displays 55


The first line of this display gives you the following information: (a) the interval length (number in parentheses—5 minutes) and (b) the current place in the interval (4 minutes, 50 seconds).

IRSP signifies the type of item it displays by the G= value in the ID column. When IRSP displays transaction groups, as in the example above, it precedes the group’s name with the characters G=.

When IRSP displays items within a specified transaction group, as in Figure 18 on page 56, it identifies the item type with one of the following characters:

The last three lines of the display show the following information:

The OTHER and SYSTEM totals display only when you request response times for all groups, by omitting the group number or GRP= keyword from IRSP.

Transaction group analysisTo display processing response times for the individual items in group 01 issue the following commands:

IRSP01

TIMEP


C= Transaction class

L= Logical terminal name (LTERM)

P= PSB name

T= Transaction name

AVERAGES Average response time for all transactions contained in the groups listed above.

OTHER Average response time for transactions which are not defined in any transaction group.

SYSTEM Average response time for all IMS transactions in the system.



FIGURE 18. Time Interval Response Analysis for a Transaction Group

In this example, group 01 includes transaction PART and transaction pattern PA*. The blanks in the five-minute interval mean that no response time components of this type in this group occurred in the last 36 seconds.

If you choose the group by name rather than by number, RTA generates an extra line with IRSP and the group name. The display of the group items begins on the following line. Figure 19 on page 56 shows a typical display in response to an IRSP command by group name.

FIGURE 19. Time Interval Analysis for All Items in Group PARTS

Note: This manual uses group number for the examples that follow.

Group averagesTo display average response times for a selected group, (for example, group 03) enter the following commands:

IRSP03

ATIME

These commands result in a display like the following:

IRSP01| ID | (00:05) 00:00:36 | (00:15) 00:05:36 | (01:00) 00:05:36 | TIMEP |T=PA* | | 2.3 | 2.3 |+ |T=PART | | 2.7 | 2.7 |+ | AVERAGES| | 2.5 | 2.5 |

IRSP GRP=PARTS+ | ID | (00:05) 00:00:36 | (00:15) 00:05:36 | (01:00) 00:05:36 | TIMEP |T=PA* | | 2.3 | 2.3 |+ |T=PART | | 2.7 | 2.7 |+ | AVERAGES| | 2.5 | 2.5 |

RTA Displays 57


FIGURE 20. Average Response Time Analysis for a Group

Figure 20 on page 57 shows that the average response time for group 03 during the last four minutes and 50 seconds was 1.8 seconds. During the last 9 minutes and 50 seconds, the average response time was 1.6 seconds. This indicates that the average response time for group 03 is going up. The response time measured is response time 1 (R1), as the default for the TIME command is TIMER1.

Response type AL optionTo display average response times for all six response types, enter the AL option in the argument field of the TIME command, as follows:

IRSP

TIMEAL


FIGURE 21. All Six Response Types Display

Note: Resptime 1 is not time the sum of Resptime 0 and Outqueue. These numbers are averages within each response time component type.

Transaction counts (CNT)The TIME command displays the response time data that RTA collects during each interval. The CNT minor command displays the number of transactions recorded during each of these time intervals. The transaction rate for each

IRSP03| ID | (00:05) 00:04:50 | (00:15) 00:09:50 | (01:00) 00:09:50 |ATIME | AVERAGES| 1.8 | 1.6 | 1.6 |

IRSP | ID | (00:05) 00:02:50 | (00:15) 00:02:50 | (01:00) 00:02:50 | TIMEAL|Inqueue | 3.5 | 3.5 | 3.5 |+ |Pgm Inq | | | |+ |Processing| 4.1 | 4.1 | 4.1 |+ |Resptime 0| 7.6 | 7.6 | 7.6 |+ |Outqueue | 13.7 | 13.7 | 13.7 |+ |Resptime 1| 23.0 | 23.0 | 23.0 |



interval also displays within parentheses. The rate is in transactions per minute.

FIGURE 22. Transaction Counts Display

=============================================================================== IRSP03| ID | (00:05) 00:02:23 | (00:15) 00:02:23 | (00:30) 00:02:23 | TIMER1|T=BILLINQ | 0.2 | 0.2 | 0.2 |+ | AVERAGES| 0.2 | 0.2 | 0.2 | ====-------------------------------------------------------------------------- CNT R1|T=BILLINQ | (31.9) 76 | (31.9) 76 | (31.9) 76 |+ | TOTALS | (31.9) 76 | (31.9) 76 | (31.9) 76 | ====-------------------------------------------------------------------------- CNT AL|Inqueue | (33.1) 79 | (33.1) 79 | (33.1) 79 |+ |Pgm Inq | | | |+ |Processing| (32.7) 78 | (32.7) 78 | (32.7) 78 |+ |Resptime 0| (32.7) 78 | (32.7) 78 | (32.7) 78 |+ |Outqueue | (31.9) 76 | (31.9) 76 | (31.9) 76 |+ |Resptime 1| (31.9) 76 | (31.9) 76 | (31.9) 76 |===============================================================================

RTA Displays 59

Time Slot Analysis (SRSP)


SRSP commandThe SRSP major command displays the time slot analysis. The $OIRTA SLOT macros in the KOIGBL global module define the time slots which SRSP displays. (For more information about the $OIRTA SLOT macro and the KOIGBL module, see the Configuration and Customization Guide.) With SRSP you can display totals for all groups, all items within a specific group, or totals for a single group item. Figure 23 on page 59 shows the format of the SRSP command.

FIGURE 23. SRSP (Time Slot) Display Command Format

To select specific groups for display, enter the group number in the command argument field (nn in the example above), or use the GRP= keyword to specify the group’s number or name.

The minor command TIME displays response time information. The minor command CNT displays transaction count information. Figure 24 on page 60 shows the format of the TIME and CNT minor commands.

xSRSPnn xxxxxxxx| | || | %----> xxxxxxxx is either a group or group item, not both.| || | GRP=group - Name or number of group to display.| | If you omit both xxxxxxxx and nn,| | all groups display.| || | group item - Group item for which data is to| | display. Items are specified as| | follows&gml.| | TRAN=xxxxxxxx (transaction name)| | TERM=xxxxxxxx (LTERM name)| | PSB=xxxxxxxx (PSB name)| | CLASS=nnn (transaction class)| || %-> nn - group number to display|%------> time slot scrolling selection character&gml. 0 - select time slots 1-4 (1-8 if 132 column terminal) 1 - select time slots 5-8 (9-16 if 132 column terminal) . . . . . . . . . . 5 - select time slots 21-24 (41-48 if 132 column terminal) . . . . . 9 - select time slots 37-40 A - select time slots 41-44 B - select time slots 45-48



FIGURE 24. Time and CNT Minor Commands Format

The following sections show examples of several typical time slot analyses.

All groups plus averagesTo display response time 1 for all groups, plus averages for each time slot, enter the following commands:

SRSP

TIMER1

FIGURE 25. Time Slot Response Analysis for All Groups

xTIMEzzxCNT zz| || +-> response type: I - Input Queue Time| PI - Program Input Queue Time| P - Processing Time| O - Output Queue Time| R0 - Response Time 0| R1 - Response Time 1 (default display)| AL - All six response types listed above|+------> scrolling/average selection character: (blank) display all groups/items and average A display averages only 0-9 scrolling value 0 - show 1st 10 groups/items 1 - show 2nd 10 groups/items . . 9 - show 10th 10 groups/items

SRSP | ID | 08:00-09:00 | 09:00-10:00 | 10:00-10:30 | 10:30-11:00 | TIMER1|G=PARTS | 1.7 | 1.9 | 1.7 | 2.0 |+ |G=BILLING | 0.5 | 0.8 | 0.8 | 0.5 |+ |G=INVOICE | 1.7 | 2.1 | 2.1 | 1.2 |+ |G=MAIL | 0.4 | 0.7 | 1.2 | 1.0 |+ | AVERAGES| 1.3 | 2.1 | 1.1 | 1.8 |+ | OTHER | 0.2 | 1.4 | 3.1 | 2.4 |+ | SYSTEM | 1.2 | 1.8 | 2.3 | 2.1 |

RTA Displays 61


All items within a group plus averagesTo display response time 1 for all items within a group plus averages for each time slot, enter the following commands:

SRSP01

TIMER1


FIGURE 26. Time Slot Response Analysis for All Items within a Group

Note: If you choose the group by name rather than number, RTA generates an extra line with the slot TIME headings under the group names. See Figure 19 on page 56 for an example.

RTA can display a maximum of four time slots on one line of an 80-column terminal. On a 132-column terminal, RTA can display up to eight time slots on one line. To display the next set of time slots, place a scrolling character in column 1 of the SRSP command. Blank fields indicate there were no transactions during the interval. Figure 27 on page 61 shows a typical display which contains an interval with no transactions.

FIGURE 27. Scrolling Time Slot Analysis

SRSP01| ID | 08:00-09:00 | 09:00-10:00 | 10:00-10:30 | 10:30-11:00 | TIMER1|T=ADDPART | | 2.0 | 1.6 | 1.8 |+ |T=DELPART | 9.2 | | 1.3 | |+ |T=PA* | 0.4 | 0.7 | 0.8 | 0.9 |+ |T=PART | 0.4 | 0.7 | 0.6 | 0.7 |+ |T=PARTS | | | 1.0 | 1.1 |+ |T=UPDPART | | 2.1 | | |+ | AVERAGES| 2.3 | 1.9 | 1.4 | 1.2 |

1SRSP01| ID | 11:00-11:30 | 11:30-12:00 | 12:00-13:00 | 13:00-14:00 | TIMER1|T=ADDPART | | 2.0 | 1.6 | |+ |T=DELPART | 9.2 | | 1.3 | |+ |T=PA* | | | 0.8 | |+ |T=PART | 0.7 | 1.2 | 2.0 | |+ |T=PARTS | | | 1.2 | |+ |T=UPDPART | | 2.1 | | |+ | AVERAGES| 2.3 | 2.1 | 1.4 | |



The empty time slot on the right indicates that this time slot is not active.

Transaction group averagesTo display average response times for selected response time components, enter the following commands:

1SRSP03

ATIMEO

ATIMER1


FIGURE 28. Average Time Slot Response Analysis for a Group (Slot 5–8)

This display shows the average response time for two response components in time slots 5–8. To see the response time for other time slots, simply change the scrolling character. Figure 29 on page 62 shows an example of average response within time slots 1–4.

FIGURE 29. Average Time Slot Response Analysis for a Group (Slot 1–4)

Response type AL optionTo display average response times for all six response types, you can enter the AL option in the argument field of the TIME command as follows:

SRSP

TIMEAL

1SRSP03| ID | 11:00-11:30 | 11:30-12:00 | 12:00-13:00 | 13:00-14:00 |ATIMEO | AVERAGES| 0.7 | 1.2 | 0.8 | 1.2 |ATIMER1| AVERAGES| 1.8 | 2.1 | 1.4 | 1.4 |

SRSP03| ID | 08:00-09:00 | 09:00-10:00 | 10:00-10:30 | 10:30-11:00 |ATIMEO | AVERAGES| 1.1 | 1.0 | 1.3 | 1.2 |ATIMER1| AVERAGES| 1.5 | 1.3 | 1.9 | 2.4 |

RTA Displays 63



FIGURE 30. Time Slot Analysis for All Six Response Types

Transaction counts (CNT)The TIME command displays the response time data that RTA collected during each time slot. The CNT minor command displays the number of events that RTA recorded during each of these time slots.

FIGURE 31. Time Slot Response Analysis with Transaction Counts

SRSP03| ID | 08:00-09:00 | 09:00-10:00 | 10:00-10:30 | 10:30-11:00 | TIMEAL|Inqueue | 0.2 | 0.1 | 0.2 | 0.7 |+ |Pgm Inq | | | | |+ |Processing| 0.2 | 0.2 | 0.4 | 0.5 |+ |Resptime 0| 0.4 | 0.3 | 0.6 | 1.2 |+ |Outqueue | 1.1 | 1.0 | 1.3 | 1.2 |+ |Resptime 1| 1.5 | 1.3 | 1.9 | 2.4 |

2SRSP03| ID | 12:00-13:00 | 13:00-14:00 | 14:00-14:30 | 14:30-15:00 | TIMER1|T=BILLING | | 0.2 | 0.8 | |+ | AVERAGES| | 0.2 | 0.8 | | ====---------------------------------------------------------------------- CNT R1|T=BILLING | | 84 | 2 | |+ | TOTALS | | 84 | 2 | |

Moving Time Slot Analysis (GRSP)



GRSP commandThe GRSP major command displays the moving time slot analysis.

You can control the parameters that affect a group/item for display, as well as the scaling and window of the display. You can change the defaults of these values in the KOIGBL table (see the Configuration and Customization Guide), or change them dynamically with the ISET immediate command as “Moving Time Slots (ISET)” on page 38 describes.

The parameters for a group item are independent of the groups containing it. An item may be in several groups but it only has one set of controlling parameters.

FIGURE 32. GRSP (Moving Time Slot) Display Command Format

To select specific groups for display, either enter the group number in the command argument field (nn in Figure 32 on page 64), or use the GRP= keyword to specify the group’s number or name.

The TIME minor command graphically shows transaction response time during the last ten minutes.

GRSPnn xxxxxxxx | | | %----> xxxxxxxx is either a group or group item, not both. | | GRP=group - Name or number of group to display. | If xxxxxxxx and nn are both omitted, | all groups are displayed. | | group item - Group item for which data is to be | displayed. Items are specified as | follows&gml. | TRAN=xxxxxxxx (transaction name) | TERM=xxxxxxxx (LTERM name) | PSB=xxxxxxxx (PSB name) | CLASS=nnn (transaction class) | %-> nn - group number to display

RTA Displays 65


FIGURE 33. TIME Minor Commands Format

RTA displays groups or group items in two ways:

Groups/items are defined as eligible for display if they are either fixed or dynamic, and exceeded their threshold during the window.

The following rules apply to the display of groups/items with GRSP:

n Fixed groups/items (marked with > and < surrounding the name) are chosen for display first and dynamic groups/items are used to fill in the remaining positions.

n If there are six or more fixed groups/items (11 if using a 132-column terminal), then dynamic groups/items do not appear unless you use the scrolling capability.

n Fixed groups/items always fill in from the right side of the display and dynamic from the left.

n If you do not specify a group name, number, or the name of an individual group item, then RTA selects group totals for display.

fixed Always displays.

dynamic Displays only when the response time exceeds a specified threshold during the last 1-10 minute window.

xTIMEzz| || %-> response type&gml. I - Input Queue Time| PI - Program Input Queue Time| P - Processing Time| O - Output Queue Time| R0 - Response Time 0| R1 - Response Time 1 (default display)| AL - All six response types listed above|%------> scrolling/subselection character&gml. A set consists of six groups/items on an 80 column terminal, or eleven groups or items on a 132 column terminal. (blank or 0) - display 1st set of eligible groups/items 1 - display 2nd set of eligible groups/items . . . . . . . . 9 - display 10th set of eligible groups/items A - display 11th set of eligible groups/items . . . . Z - display 36th set of eligible groups/items



The asterisks (*) in the display show response times for the group/item for the last ten minutes. If the time is 12:31:24, then RTA calculates the current minute from 12:31:00 through 12:31:24. At 12:32, the 12:31 minute display shifts to the previous minute’s slot.

The default display shows groups in the boxes, however you may display group items in the boxes instead. To do this, enter the group number or name after the GRSP command.

The response of the group/item during the last minute shows numerically on the line below the group/item ID. The response value appears as MM:SS.T or as HH:MM:SS if the response is greater than or equal to one hour.

RTA displays the threshold line (when it exists and falls within the scale) as a series of minus signs (-) or as plus signs (+) where the threshold intercepts the response graph.

Moving time slot examplesFigure 34 on page 66 shows three dynamic groups (BILLING, PARTS, and MAIL) and two fixed groups (INVOICE and SHIPPING). The special SYSTEM group, which displays the response time for all transactions in the system, is also defined as a fixed display group. RTA displays the dynamic groups because they exceeded their threshold within the eligible window. This window for threshold checking spans at least the past five minutes, since RTA would not have displayed the dynamic group MAIL if it were shorter. This is because MAIL did not exceed its threshold during the past four minutes.

A string of asterisks appears beneath the box of any group or item which exceeded its response time threshold. This highlights transactions which are experiencing response time problems.

FIGURE 34. Moving Time Slot Display

GRSP >> Transaction Group totals display << TIMER1 | BILLING | PARTS | MAIL |>SHIPPING<|>INVOICE <|>SYSTEM <|+ | 0.8 | 0.4 | 0.0 | 0.0 | 0.6 | 0.4 |+ |==========+==========+==========+==========+==========+==========++ 1.0| | | | | | |+ .9| | | | |----------| |+ s .8| *| | | | | |+ e .7|---------+| | | | | |+ c .6| *| * | | | *| * |+ o .5| * *| * |-----+----| | * * *| ** * |+ n .4| * *|--+-++---+| * | * | * * *|-++----+-+|+ d .3| ** *| ***** *| * ** | ** |** **** *|**** ***|+ s .2| ** **| ****** **| ** ** * |-++---+---|******* **|***** ****|+ .1| *****|**********|********* |*** ** |**********|**********|+ +----------+----------+----------+----------+----------+----------++ ***** ***** ***** ***** *****+ min -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0

RTA Displays 67


Now use the ISET command to modify the display parameters.

ISETR1 GRP=MAIL THRESH=0

ISETR1 SCALE=2

ISET WINDOW=1


Notice that MAIL disappeared, since the one minute window had no responses over the threshold. To ensure a constant display of MAIL, you can set it as a fixed transaction.

GRSP >> Transaction Group totals display << TIMER1 | BILLING | PARTS | |>SHIPPING<|>INVOICE <|>SYSTEM <|+ | 0.8 | 0.4 | | 0.0 | 0.6 | 0.4 |+ |==========+==========+==========+==========+==========+==========++ 2.0| | | | | | |+ 1.8| | | | | | |+ s 1.6| | | | | | |+ e 1.4| | | | | | |+ c 1.2| | | | | | |+ o 1.0| | | | | | |+ n .8|---------+| | | | | |+ d .6| * *| * | | | * * *| * |+ s .4| ** *|--+-++---+| | * |******* *|-++----+-+|+ .2| *****|**********| |-++---+---|**********|***** ****|+ +----------+----------+----------+----------+----------+----------++ ***** ***** ***** *****+ min -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0



This example resets the scale back to 1 second and sets MAIL as a fixed transaction:

ISETR1 GRP=MAIL FIX=YES

ISETR1 SCALE=1

The display now shows four fixed groups/items and two dynamic groups/items.

If all six windows are full, and you want to add another group for display, use the scrolling feature of the TIME command. To illustrate this, add one additional fixed group to the display (even though it had no activity in the last ten minutes):

ISETR1 GRP=SAMA FIX=YES

Now GRSP produces a display similar to Figure 35 on page 69.

GRSP >> Transaction Group totals display << TIMER1 | BILLING | PARTS |>SHIPPING<|>INVOICE <|>MAIL <|>SYSTEM <|+ | 0.8 | 0.4 | 0.0 | 0.6 | 0.0 | 0.4 |+ |==========+==========+==========+==========+==========+==========++ 1.0| | | | | | |+ .9| | | | | | |+ s .8| *| | | | | |+ e .7|---------+| | | | | |+ c .6| *| * | | *| | * |+ o .5| * *| * | | * * *|-----+----| ** * |+ n .4| * *|--+-++---+| * | * * *| * |-++----+-+|+ d .3| ** *| ***** *| ** |** **** *| * ** |**** ***|+ s .2| ** **| ****** **|-++---+---|******* **| ** ** * |***** ****|+ .1| *****|**********|*** ** |**********|********* |**********|+ +----------+----------+----------+----------+----------+----------++ ***** ***** ***** ***** *****+ min -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0

RTA Displays 69


FIGURE 35. Moving Time Slot Response Display

GRSP replaces the dynamic group PARTS with the fixed group SAMA.

To scroll the display, enter an alphanumeric character in column one of the TIME minor command. 0 means do not scroll, 1 means scroll past the first six groups or items eligible for display, etc.

Now scroll to illustrate how we can display the group PARTS. Even though we do not have room on one display for all eligible groups, scrolling lets you see more than only six groups.

FIGURE 36. Moving Time Slot Response Display with Scrolling

GRSP >> Transaction Group totals display << TIMER1 | BILLING |>SAMA <|>SHIPPING<|>INVOICE <|>MAIL <|>SYSTEM <|+ | 0.8 | 0.0 | 0.0 | 0.6 | 0.0 | 0.4 |+ |==========+==========+==========+==========+==========+==========++ 1.0| | | | | | |+ .9| | | | | | |+ s .8| *| | | | | |+ e .7|---------+| | | | | |+ c .6| *| | | *| | |+ o .5| * *| | | * * *|-----+----| |+ n .4| * *| | * | * * *| * |-++----+-+|+ d .3| ** *| | ** |** **** *| * ** |**** ***|+ s .2| ** **| |-++---+---|******* **| ** ** * |***** ****|+ .1| *****| |*** ** |**********|********* |**********|+ +----------+----------+----------+----------+----------+----------++ ***** ***** ***** *****+ min -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0

GRSP >> Transaction Group totals display <<1TIMER1 | PARTS | | | | | |+ | 0.4 | | | | | |+ |==========+==========+==========+==========+==========+==========++ 1.0| | | | | | |+ .9| | | | | | |+ s .8| | | | | | |+ e .7| | | | | | |+ c .6| * | | | | | |+ o .5| * | | | | | |+ n .4|--+-++---+| | | | | |+ d .3| ***** *| | | | | |+ s .2| ****** **| | | | | |+ .1|**********| | | | | |+ +----------+----------+----------+----------+----------+----------++ *****+ min -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0



Figure 36 on page 69 shows only the dynamic group PARTS. The TIME command scrolled past the other groups.

Response type AL optionTo display average response times for all six response types, enter the AL option in the argument field of the TIME command as follows:

GRSP

TIMEAL

This results in a display similar to the following:

FIGURE 37. Graphical Display Showing all Six Response Types

If the GRSP command selects a single group item, such as TRAN=BILLUPD, then AL is the only valid option for the TIME command. If you enter any other response type, such as R0, the TIME command issues a warning message and dynamically changes the response type to AL. This is a powerful method for identifying the cause of a response time delay. For example, if you enter the following commands:

GRSP TRAN=BILLUPD

TIMER0

A display similar to Figure 38 on page 71 appears:

GRSP >> Transaction Group totals display << TIMEAL |Inqueue |Pgm Inq |Processing|Resptime 0|Outqueue |Resptime 1|+ | 0.1 | 0.0 | 0.2 | 0.3 | 0.1 | 0.4 |+ |==========+==========+==========+==========+==========+==========++ 1.0| | | | | | * * |+ .9| | | | * | |* * * |+ S .8| | | | * | |* * ** * |+ E .7| | | |* * * | |** **** * |+ C .6| | | |* *** | |+++++++++-|+ O .5| | | * |* ****** | |********* |+ N .4| * | |* * * * |+++++++++-| * |**********|+ D .3|* *** | |++-++++++-|**********|-+---++-+-|**********|+ S .2|+-+++++-+-|----------|**********|**********|**** ** * |**********|+ .1|**********| |**********|**********|**********|**********|+ +----------+----------+----------+----------+----------+----------++ ***** ***** ***** ***** *****+ MIN -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0

RTA Displays 71


FIGURE 38. Single Group Item Display

This display shows that input queuing and processing time are contributing almost equally to push response time over target thresholds.

GRSP TRAN=BILLUPD TIMEAL >> OI322: Response type ALL forced for single item <<+ |Inqueue |Pgm Inq |Processing|Resptime 0|Outqueue |Resptime 1|+ | 0.1 | 0.0 | 0.2 | 0.3 | 0.1 | 0.4 |+ |==========+==========+==========+==========+==========+==========++ 1.0| | | | | | * * |+ .9| | | | * | |* * * |+ S .8| | | | * | |* * ** * |+ E .7| | | |* * * | |** **** * |+ C .6| | | |* *** | |+++++++++-|+ O .5| | | * |* ****** | |********* |+ N .4| * | |* * * * |+++++++++-| * |**********|+ D .3|* *** | |++-++++++-|**********|-+---++-+-|**********|+ S .2|+-+++++-+-|----------|**********|**********|**** ** * |**********|+ .1|**********| |**********|**********|**********|**********|+ +----------+----------+----------+----------+----------+----------++ ***** ***** ***** ***** *****+ MIN -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0 -8-6-4-2-0




RTM commandThe response time monitor (RTM) quickly identifies poorly-performing transactions and terminals. RTM lets you monitor all transactions in IMS, independent of group definitions. It also reports on the transactions and logical terminals with the longest response times.

The RMON command activates the data analysis function of RTM. The XMON command activates the data display function for transactions; TMON activates it for terminals.

Data analysis (RMON)RMON starts and stops RTM data analysis. RMON parameters control the duration of the sampling interval as well as the size of your RTM displays.

Figure 39 on page 72 shows the format of the RMON command.

FIGURE 39. RMON Command Format

The SIZE parameter controls the number of transactions and terminals with the longest response time, which the XMON and TMON commands display. The default is 10 items.

The INTRV parameter controls the sampling interval in minutes. The default is 15 minutes.

RMON ccc SIZE=nn INTRV=nnn FIXED/NFIXED UNIQ/NUNIQ | | | | | | | | | %-> controls display of | | | | items - unique (default) | | | | or non-unique | | | | | | | %-> controls display of | | | items - fixed (default) | | | or not fixed | | | | | %-> controls sampling interval (n = 1-999 in minutes) | | | %-> controls number of items that | can appear on the screen | (n = 1-999) | %-> ON - turn on RTM data collector OFF - turn off RTM data collector ? or blank - display current status

RTA Displays 73


The FIXED/NFIXED parameters control how RTM deletes data from its displays. Let us assume an INTRV (interval) of 15 minutes. With a FIXED window, RTM samples data for 15 minutes and then clears all its displays before it samples more data. FIXED window interval displays are more characteristic of the environment later in the interval when the collected data represents a larger sample.

With an NFIXED or moving window, RTM deletes each piece of response time data from its display individually after another one occurs with a higher response time or after 15 minutes, whichever comes first.

The UNIQ/NUNIQ parameters control the number of items within a group that RTM can display. For example, assume that there is one type of transaction called ADDINV that always takes longer than all the other types within the IMS environment. NUNIQ allows more than one ADDINV transaction among those transactions with the highest response time to appear on RTM displays, leaving no space for any other type of transaction. If you do not want this, specify UNIQ.

With UNIQ, RTM only displays the ADDINV transaction with the highest response time to appear on RTM displays, leaving space for other transaction codes.

The first line of Figure 40 on page 73 shows the status of RTM that displays when RMON is issued with no command arguments. The second line is an example of the RMON ON command which sets display parameters.

FIGURE 40. Typical RMON Display

RMON values are effective until the time interval elapses, or you temporarily turn off the RMON facility.

Data display for transactions (XMON)The XMON command displays transactions with the highest response time.

Figure 41 on page 74 shows the format for the XMON command.

RMON >> OI342: RTM is active; SIZE=5 INTRV= 2 NFIXED NUNIQ>RMON ON SIZE=10 INTRV=15 FIXED NUNIQ



FIGURE 41. XMON Command Format

RTM samples each response time component independently. Therefore, the transactions with the highest output queue times (O) will not necessarily be the same as those with the highest processing times (P).

The Response Time 0 display also shows the response times of the other components that comprise it: Input Queue Time (I) and Processing Time (P).

In the following example, the status is NFIXED or moving window and NUNIQ or non-unique data collection. That is why more than one of the same type of item (BILLING) can appear on the screen at the same time. The sampling interval is 2 minutes, so at any given moment RTM displays those transactions with the highest response times over the last 2 minutes (16:09:14 to 16:11:14). Response times are in seconds.

The SIZE specified is 5, so only the 5 transactions with the highest response times will display per response time component. Yet, in the Input Queue Time display, only four transactions are active at this time and none are in the output queue. Also note that the R0 display breaks down into input queue and processing time components.

XMONcc | %-> response type: I - Input Queue Time PI - Program Input Queue Time P - Processing Time O - Output Queue Time R0 - Response Time 0 (default) R1 - Response Time 1 blank - Default Response Time 0

RTA Displays 75


FIGURE 42. Typical XMON Display

Data display for terminals (TMON)TMON displays logical terminals with the highest response time.

Figure 43 on page 76 shows the format of the TMON command.

========================================================================== XMONI Transactions with longest I time 16:09:14 - 16:11:14+ ID I | ID I | ID I+ BILLING 43.3 | BILLING 25.6 | BILLING 23.4+ BILLING 17.5 |========================================================================== XMONPI Transactions with longest PI time 16:09:14 - 16:11:14+ ID PI | ID PI | ID PI========================================================================== XMONP Transactions with longest P time 16:09:14 - 16:11:14+ ID P | ID P | ID P+ BILLING 20.5 | BILLING 20.2 | BILLING 18.0+ BILLING 17.9 |========================================================================== XMONO Transactions with longest O time 16:09:14 - 16:11:14+ ID O | ID O | ID O========================================================================== XMONR0 Transactions with longest R0 time 16:09:14 - 16:11:14+ ID I P R0 | ID I P R0+ BILLING 43.3 17.9 61.2 | BILLING 25.6 20.5 46.1+ BILLING 23.4 18.0 41.4 | BILLING 17.5 20.2 37.7========================================================================== XMONR1 Transactions with longest R1 time 16:09:14 - 16:11:14+ ID R1 | ID R1 | ID R1==========================================================================



FIGURE 43. TMON Command Format

RTM samples each response time component independently. Therefore the terminals with, for example, the highest output queue times (O) are not necessarily the same as those with the highest processing times (P).

The Response Time 0 display also shows the response times of the other components that comprise it: Input Queue Time (I) and Processing Time (P).

In the following example, the status is NFIXED or moving window and NUNIQ or non-unique data collection. That is why more than one of the same type of item can appear on the screen at the same time. The sampling interval is two minutes, so at any given moment RTM displays those transactions with the highest response times over the last two minutes (16:09:14 - 16:11:14). Response times are in seconds.

The SIZE is five, allowing the five transactions with the highest response times to display per response time component. Yet, in the Input Queue Time display, only four transactions are active at this time and none are in the output queue. Also note that the R0 display breaks down into input queue and processing time components.

TMONcc | %-> response type: I - Input Queue Time PI - Program Input Queue Time P - Processing Time O - Output Queue Time R0 - Response Time 0 R1 - Response Time 1 (default) blank - Default Response Time 1

RTA Displays 77


FIGURE 44. Typical TMON Display

RMON >> OI342: RTM is active; SIZE=5 INTRV= 2 NFIXED NUNIQ==========================================================================> The following monitors terminal response time components.========================================================================== TMONI Logical Terminals with longest I time 16:09:14 - 16:11:14+ ID I | ID I | ID I+ LDEP1D01 43.3 | L62D 25.6 | L635 23.4+ LDEP0P01 17.5 |========================================================================== TMONPI Logical Terminals with longest PI time 16:09:14 - 16:11:14+ ID PI | ID PI | ID PI========================================================================== TMONP Logical Terminals with longest P time 16:09:14 - 16:11:14+ ID P | ID P | ID P+ LDEP1D01 20.5 | L64F 20.2 | L62D 18.0+ LDEP0P01 17.9 |========================================================================== TMONO Logical Terminals with longest O time 16:09:14 - 16:11:14+ ID O | ID O | ID O========================================================================== TMONR0 Logical Terminals with longest R0 time 16:09:14 - 16:11:14+ ID I P R0 | ID I P R0+ LDEP1D01 43.3 17.9 61.2 | L62D 25.6 18.0 43.6+ L635 23.4 18.0 41.4 | LDEP0P01 17.5 17.9 35.4========================================================================== TMONR1 Logical Terminals with longest R1 time 16:09:14 - 16:11:14+ ID R1 | ID R1 | ID R1==========================================================================

Guide to Candle Customer Support 79

Guide to CandleCustomer Support

IntroductionCandle Corporation is committed to producing top-quality software products and services. To assist you with making effective use of our products in your business environment, Candle is also committed to providing easy-to-use, responsive customer support.

Precision, speed, availability, predictability—these terms describe our products and Customer Support services.

Included in this Guide to Candle Customer Support is information about the following:

Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80– Telephone Support

– eSupport

– Description of Severity Levels

– Service-level objectives

– Recording and monitoring calls for quality purposes

– Customer Support Escalations

– Above and Beyond

Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84– Assigned Support Center Representative (ASCR)

– Maintenance Assessment Services (MAS)

– Multi-Services Manager (MSM)

Customer Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85– Link to Worldwide Support Telephone and E-mail information

A

Base Maintenance Plan



OverviewCandle offers a comprehensive Base Maintenance Plan to ensure that you realize the greatest value possible from your Candle software investments. We have more than 200 technicians providing support worldwide, committed to being responsive and to providing expedient resolutions to support requests. Technicians are available worldwide at all times during the local business day. In the event of an after-hours or weekend emergency, our computerized call management and forwarding system will ensure that a technician responds to Severity One situations within one hour. For customers outside of North America, after-hours and weekend support is provided in English language only by Candle Customer Support technicians located in the United States.

Telephone supportCandle provides consistently reliable levels of service—thanks to our worldwide support network of dedicated experts trained for specific products and operating systems. You will always work with a professional who truly understands your problem.

We use an online interactive problem management system to log and track all customer-reported support requests. We give your support request immediate attention by routing the issue to the appropriate technical resource, regardless of geographic location.

Level 0 Support is where your call to Candle Customer Support is first handled. Your support request is recorded in our problem management system, then transferred to the appropriate Level 1 support team. We provide Level 0 manual interaction with our customers because we support more than 170 products. We feel our customers would prefer personal interaction to a complex VRU or IVR selection menu.

Level 1 Support is the service provided for initial support requests. Our Level 1 team offers problem determination assistance, problem analysis, problem resolutions, installation assistance, and preventative and corrective service information. They also provide product usage assistance.

Level 2 Support is engaged if Level 1 cannot provide a resolution to your problem. Our Level 2 technicians are equipped to analyze and reproduce errors or to determine that an error is not reproducible. Problems that cannot be resolved by Level 2 are escalated to Candle’s Level 3 R&D support team.

Level 3 Support is engaged if a problem is identified in Candle product code. At Level 3, efforts are made to provide error correction, circumvention or notification that a correction or circumvention is not available. Level 3 support provides available maintenance modifications and maintenance delivery to correct appropriate documentation or product code errors.



eSupportIn order to facilitate the support process, Candle also provides eSupport, an electronic full-service information and customer support facility, using the World Wide Web at www.candle.com/support/. eSupport allows you to open a new service request and update existing service requests, as well as update information in your customer profile. New and updated service requests are queued to a support technician for immediate action. And we can respond to your request electronically or by telephone—it is your choice.

eSupport also contains a continually expanding knowledge base that customers can tap into at any time for self-service access to product and maintenance information.

The Candle Web Site and eSupport can be accessed 24 hours a day, 7 days a week by using your authorized Candle user ID and password.

Description of Candle severity levelsResponses to customer-reported product issues and usage questions are prioritized within Candle according to Severity Code assignment. Customers set their own Severity Levels when contacting a support center. This ensures that we respond according to your individual business requirements.

Severity 1 Crisis

A crisis affects your ability to conduct business, and no procedural workaround exists. The system or application may be down.

Severity 2High

A high-impact problem indicates significant business effect to you. The program is usable but severely limited.

Severity 3Moderate

A moderate-impact problem involves partial, non-critical functionality loss or a reasonable workaround to the problem. A “fix” may be provided in a future release.

Severity 4Low

A low-impact problem is a “how-to” or an advisory question.

Severity 5Enhancement Request

This is a request for software or documentation enhancement. Our business units review all requests for possible incorporation into a future release of the product.

http://www.candle.com/support/



Candle has established the following service-level objectives:

Recording and Monitoring Calls for Quality PurposesCandle is committed to customer satisfaction. To ensure that our customers receive high levels of service, quality and professionalism, we’ll monitor and possibly record incoming and outgoing Customer Support calls. The information gleaned from these calls will help us serve you better. If you prefer that your telephone call with Candle Customer Support in North America not be monitored or recorded, please advise the representative when you call us at (800) 328-1811 or (310) 535-3636.

Customer Support EscalationsCandle Customer Support is committed to achieving high satisfaction ratings from our customers. However, we realize that you may occasionally have support issues that need to be escalated to Candle management. In those instances, we offer the following simple escalation procedure:

If you experience dissatisfaction with Candle Customer Support at any time, please escalate your concern by calling the Candle support location closest to you. Ask to speak to a Customer Support manager. During standard business hours, a Customer Support manager will be available to talk with you or will return your call. If you elect to hold for a manager, you will be connected with someone as soon as possible. If you wish a return call, please tell the Candle representative coordinating your call when you will be available. After contacting you, the Customer Support manager will develop an action plan to resolve your issue. All escalations or complaints received about support issues are logged and tracked to ensure responsiveness and closure.

Call Status Severity 1 Goal

Severity 2 Goal

Severity 3 Goal

Severity 4 Goal

Severity 5Goal

First Call Time to Answer

90% within one minute

Level 1 Response

(Normal Business Hours)

90% within 5 minutes

90% within one hour

Level 2 Response

(Normal Business Hours)

Warm Transfer

90% within two hours

90% within eight hours

Scheduled follow-up (status update)

Hourly or as agreed

Daily or as agreed

Weekly or as agreed Notification is made when an enhancement is incorporated into a generally available product.

Notification is made when a fix is incorporated into a generally available product.

The above information is for guideline purposes only. Candle does not guarantee or warrant the above service levels. This information is valid as of October 1999 and is subject to change without prior notice.



Above and BeyondWhat differentiates Candle’s support services from our competitors? We go the extra mile by offering the following as part of our Base Maintenance Plan:

n Unlimited multi-language defect, installation and operations support

n eSupport using the World Wide Web

n Regularly scheduled product updates and maintenance provided at no additional charge

n Over 200 specialized technicians providing expert support for your Candle products

Enhanced Support Services


Enhanced Support Services

OverviewOur Base Maintenance Plan provides a high level of software support in a packaged offering. However, in addition to this plan, we have additional fee-based support services to meet unique customer needs.

The following are some examples of our added-value support services:

n Assigned Support Center Representative Services (ASCR)

– An assigned focal point for managing support escalation needs

– Proactive notification of available software fixes

– Proactive notification of product version updates

– Weekly conference calls with your ASCR to review active problem records

– Monthly performance reviews of Candle Customer Support service levels

– Optional on-site visits (extra charges may apply)

n Maintenance Assessment Service (MAS)

– On-site assessment services

– Advice about product maintenance and implementation

– Training your staff to develop efficient and focused procedures to reduce overall cost of ownership of your Candle software products

– Analysis of your Candle product environment: versions, updates, code correction history, incident history and product configurations

– Reviews to ensure that purchased Candle products and solutions are used effectively

n Multi-Services Manager (MSM)

Multi-Services Manager provides highly valued services to customers requiring on-site full time expertise to complement their technical resources.

– Dedicated on-site Candle resource (6 months or one year) at your site to help ensure maximum use and effectiveness of your Candle products

– Liaison for all Candle product support activities, coordination and assistance with implementation of all product updates and maintenance releases

– Works with your staff to understand business needs and systems requirements

– Possesses technical and systems management skills to enhance your staff ’s knowledge and expertise

– Other projects as defined in Statement of Work for MSM services


Customer Support Contact Information


Link to Worldwide Support Telephone and E-mail informationTo contact Customer Support, the current list of telephone numbers and e-mail addresses can be found on the Candle Web site, www.candle.com/support/.

Select Support Contacts from the list on the left of the page.

http://www.candle.com/support/

Index 87

Symbols$OIRTA macro 34, 35$OIRTA SLOT macros 59

AADDINV transaction 73Adobe portable document format 12all six types display 57application response time 42ARSP exception 26, 39, 47

defining threshold 48ASCR

assigned support center representative 84assigned support center representative

ASCR 84automatic response time threshold monitoring

(ARSP) 26, 47average response time analysis for a group 57average time slot response

analysis for a group 62

BBMPs 9

CCNT minor 53, 57, 63

command format 54, 60format 59

customer supportbase maintenance plan 80contact information 85enhanced support services 84eSupport 81severity levels 81telephone support 80

Ddata

analysis (RMON) 72collection 33–40display for terminals (TIMON) 75display for transactions (XMON) 73

Default Parameters 34DEXAN and BMPs 9documentation set information 12

dynamic display 65

EEnd-toEnd Response Time

calculating 42End-to-End Response Time Feature 41–46

calculating response time 42displaying 45

eSupportcustomer support 81

exceptions 47–49EXPTHR parameter 48

Ffixed display 65FIXED parameter 73FIXED window 73

GGRAPH

menu option screen 31group

analysis 28default 38item 38item types 55

group displayrules 65

GRSP (moving time slot) displaycommand format 64

GRSP major 64display commands 39

GRSP major see moving time slot analysis (GRSP)

Hhost response time 42

IICTL immediate 36

format 36input queue time (I) 22input technique 29INTRV parameter 72IRSP (time interval) display

command format 53IRSP major 54, 55

Index


IRSP major see time interval analysis (IRSP)IRTA command 49IRTA major 27, 33

format 34IRTA OFF 36ISET immediate 38, 67

format-group 38format-group items 39with SCALE 40

Mmaintenance assessment service

MAS 84MAS

maintenance assessment service 84menus 30Message and BMPs 9moving time slot

display 51, 66, 67moving time slot (ISET)

scale and windowchanging defaults 38

moving time slot analysis (GRSP) 24, 25, 64moving time slot examples 66moving time slot response

display 68scrolling 69

moving time slots (ISET) 38moving window 73MSM

multi-services manager 84multi-services manager

MSM 84

NNETW immediate 45network response time 42NFIXED parameter 73, 74, 76NFIXED window 73Non-Message and BMPs 9NUNIQ parameter 73, 74, 76

OOTHER major 28output queue time (0) 23overview 19–31

Pprinting problems 12processing time (P) 22program input queue time (PI) 22

Rresponse 57response time

all group plus averages 60all groups plus averages 54all items within group plus averages 61application 42end-to-end 42group averages 56interval 24tracking 24type AL option 57

response time 0 (RO) 23response time 1 (R1) 23response time analysis component

description 9response time monitor (RTM) 27, 72

display 51response type AL option 62, 70response types

display of all six 70RIME minor

command format 54RMON immediate 72

display 73format 72

RTA 9default parameters 35description 9displays 51–77menu 30switch off with IRTA OFF 27

RTM 27RTMA

see response type monitor

SSCALE parameter 40selected time slot analysis (SRSP) 24, 25set up transactions for ARSP commands 49SETG major 49severity levels

customer support 81short-term analysis 24single group item

display 71SIZE parameter 72SNA

how ETE calculates events in 42SRSP display

format 59SRSP major 59SYSTEM major 28

Index 89

Ttelephone support

customer support 80time interval

analysis for all items in group PARTS 56display 51

time interval analysis (IRSP) 24, 53time interval response analysis

analysis for all groups 54time intervals (ICTL) 36TIME minor 24, 53, 57, 62, 63, 64

command format 60format 59

Time minorformat 65

time slotdisplay 51max displayers 61

time slot analysis 25, 59all six response types 63moving 25scrolling 61

time slot response analysisfor all groups 60for all items within a group 61with transaction counts 63

TMON immediate 75display 77format 76

transaction counts (CNT) 57, 63display 58

transaction groupanalysis 55

UUNIQ parameter 73

VVTAM response time 42

WWINDOW 40

XXMON immediate 73

display 75format 74

Response Time Analysis (RTA) Reference...

Documents

Transcript of Response Time Analysis (RTA) Reference...