command language reference manual -...

Command Language Reference ManualOMEGAMON II® for MVS

EPILOG™ for MVS Commands and Keywords

Version 520

GC32-9275-00

December 2001

Candle Corporation201 North Douglas Street

El Segundo, California 90245

2OMEGAMON II for MVS V.520 EPILOG for MVS Command Language Reference Manual

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, 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, CandleLight, CandleNet, CandleNet 2000, CandleNet Command Center, CandleNet eBP, CandleNet eBP Access for S.W.I.F.T., 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, eBA, eBA*ServiceMonitor, eBA ServiceNetwork, 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, eBusiness Platform 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, and MQSeries 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 © July 2001, 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 Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9EPILOG Command Syntax and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

What’s New in Version 520. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Descriptions of the New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Chapter 1. Command Groupings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Command and Keyword Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Chapter 2. A Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Chapter 3. B Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Chapter 4. C Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Chapter 5. D Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Chapter 6. E Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Chapter 7. F Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Chapter 8. G-H Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Chapter 9. I Commands and Keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Contents

4 OMEGAMON II for MVS V.520 EPILOG for MVS Command Language Reference Manual

Chapter 10. J Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Chapter 11. K-L Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

Chapter 12. M Commands and Keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Chapter 13. N-O Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

Chapter 14. P-Q Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Chapter 15. R Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

Chapter 16. S Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187

Chapter 17. T Commands and Keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212

Chapter 18. U-W Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220

Chapter 19. X-Z Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224

Appendix A. Data Dictionary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Interpreting the Information Provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227

Appendix B. Guide to Candle Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .302Customer Support Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

List of Figures 5

FIGURE 1. SINGLE Interval DETAIL Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176

List of Figures

List of Tables 7

Table 1. Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229

List of Tables

Preface 9

Preface

About This Document

Who should read this bookThis document is intended for OMEGAMON II® for MVS users who:

n are already familiar with EPILOG™ for MVS commands and want to refresh their memory about a command’s syntax or available keywords

n have zoomed to EPILOG from the GoTo pull-down menu

The document is organized alphabetically by command name and includes “Command Groupings” on page 19 that is an introduction organized by topic (exception analysis, hiperspace, paging, and so on) where you can refresh your memory as to the proper spelling of a command or keyword.

“Data Dictionary” on page 227 is an alphabetized list of the data elements that can be exported from the historical datastores. Use this appendix as a reference when you write programs that use data generated by the OBTAIN, EXTRACT, or COMPEXT commands.

P

EPILOG Command Syntax and Conventions



IntroductionYou can control the format and content of EPILOG reporter displays and reports using a set of commands and keywords. Keywords as a rule do not have to be entered in any particular order, unless noted otherwise. The following sections describe some general rules for entering commands, keywords, and operands.

Keyword and Operand DelimitersKeywords are separated from other EPILOG keywords and operands by one or more blank spaces, equal signs, commas, or parentheses. In this manual, we use blank spaces to separate keywords and parentheses to separate operands.

Operands that contain blanks or other delimiters must be enclosed in single quotes. To include a single quote in the operand, enter two single quotes. An operand enclosed in quotes may not be continued from one line to another.

Continuing a Command LineTo continue a command line, end it with a hyphen (-) preceded by a blank space, and press Enter. A new line is generated for you to continue the command. You can use as many lines as you need in this manner. Nothing will be executed until the reporter encounters a line that does not contain a hyphen. If you leave text to the right of the hyphen, that text is treated as a comment.

Comment LinesDuring batch processing, it is often useful to include comments with the commands. To do so, place an asterisk (*) in position 1 of the command line. The comment is written out to the message dataset pointed to by the RKM2OUTM DD statement.

Short and long Forms of CommandsMost commands and keywords have both a long and a short form. In addition, most keywords (but not commands) are recognized if you enter an unambiguous abbreviation of the long form (for example, COMBI instead of COMBINE).

Preface 11


Using Masks for OperandsYou can use the asterisk (*) as a wildcard character in certain operands, such as job names, device numbers, and volume serial numbers. The asterisk is interpreted as a variable character; any character found in the position of the asterisk meets the selection criteria.

For example, to select any job that begins with IEB, regardless of length, enter this command:

DISPLAY JOB(IEB*)

To select a job beginning with IE, followed by any single character, followed by the number 100, enter this command:

DISPLAY JOB(IE*100)

Multiple OperandsYou can enter multiple operands with any workload selection keywords. Multiple operands are logically ORed together. For example, to select batch workloads of class Q or class F, enter the following command:

DISPLAY CLASS(Q,F)

Interpreting Graphic Display CharactersThe graphic arrow displayed on detail and summary workload displays graphically depicts time, for instance, the percentage of time a workload spent in a particular wait state.

For detail displays, the scale against which values are plotted represents the percent of total degradation, from zero through one hundred. The appearance of the arrow changes as the degradation percentage passes the 30% and 60% marks, as follows:

n Below the 30% mark, the shaft of the arrow is constructed with hyphens.

n Above the 30% mark, the shaft of the arrow is constructed with equal signs instead of hyphens.

n Above the 60% mark, the shaft of the arrow is constructed with greater-than signs.

For summary displays, the scale represents the average transaction time for the interval. This time is typically displayed in seconds, and the low and high end of the scale varies from display to display. The arrows in a summary display consist of asterisks and hyphens. The segment of the line depicted with asterisks indicates the average time spent on a wait reason for the interval, and the hyphens extend the scale to represent the remaining transaction time for the interval.



Obtaining Online HelpTo obtain online help for an EPILOG command, enter HELP commandname. If you are not sure of the exact name of a command and would like to see a list of commands and topics, enter HELP without any operands.

You can enter the HELP command at any time, even while you have the output of a DISPLAY command on the screen. When you are finished with the help facility, press Enter to return to the interrupted display.

You can also request help by entering the command or topic name on the input line and pressing F1 or F13.

Preface 13

Documentation Set

Documentation Set

IntroductionCandle provides a complete set of documentation for OMEGAMON II for MVS. Each manual in this documentation set contains a specific type of information to help you use the product.

n The OMEGAMON II for MVS Configuration and Customization Guide provides instructions for configuring and customizing OMEGAMON II for MVS after it is installed.

n The OMEGAMON II for MVS User’s Guide describes how to use OMEGAMON II for MVS panels to monitor your system’s performance, solve performance problems, and prevent problems from recurring.

n The OMEGAMON II for MVS Command Language Reference Manual provides comprehensive descriptions of the OMEGAMON II for MVS commands and keywords, arranged in alphabetical order.

n The Epilog for MVS Command Language Reference Manual provides comprehensive descriptions of the Epilog for MVS commands and keywords, arranged in alphabetical order.

n The OMEGAMON II for MVS Quick Reference explains how to use the CUA interface and lists all of the fast paths. This book is available in pocket-size format.

Messages for this product can be found in the Candle Products Messages Manual.

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 MVS V.520 EPILOG for MVS Command Language Reference Manual" in the subject line.

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 product

Ordering additional documentationTo order additional product manuals, contact your Candle Customer Support representative.

Adobe Portable Document Format

Printing this book

Documentation Set


Candle 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:

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.

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

On the Print pop-up, select one of the Print Range options for

All

Current page

Pages from: [ ] to: [ ]

(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:

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.)

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.)

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.

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 Adobe

If 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.

http://www.adobe.com



What’s New in Version 520 15

What’s New in Version 520

What’s newThis chapter provides information about the new features provided with OMEGAMON II for MVS, Version 520.

W

Descriptions of the New Features



New fields on the Set Service Class Thresholds panelNew fields have been added to the Set Service Class Thresholds panel to permit you to qualify goal reporting for a specific service class. The qualification applies to either Velocity goals or Response Time Goals.

On this panel, if the Goal Type is specified as Velocity, then an updatable field, with CPU percent busy, is presented to you. If your system is displaying a workload warning or critical light that is unexpected or misleading, you can specify a percentage in this field to identify the minimum percentage of CPU that must be consumed before OMEGAMON II for MVS displays the warning or critical light.

If the Goal Type is specified as Response time, then the updatable field, with transaction rate is presented. Your response is entered in two parts, the number of transactions and a time qualifier, that may be h, m, or s (hours, minutes, or seconds). This field represents the number of transactions per time period that must occur before OMEGAMON II for MVS displays a warning or critical light.

Support for the IBM 2105 Enterprise Storage ServerThis release of OMEGAMON II for MVS provides cache memory reports for IBM’s 2105 Enterprise Storage Server. These statistics include cache read and write hit percentages and I/O requests indirectly related to the cache. Both realtime and historical data is available.

Bottleneck analysis for multi-tasking jobsSome workloads are capable of performing in multiple execution states simultaneously. An example is a workload that is actively using CPU while delayed waiting for a tape mount. Such workloads are considered multi-tasking and, therefore, capable of achieving resource total percentages greater than 100%.

Service class information now available through a zoom to Epilog sessionYou can now use the Display command to display reports about workload manager data. The Workload Manager Service Classes report will provide information, by service class, on the goal type and importance, its duration, percent of transactions to complete within the specified response time goal, as well as the transaction count, transaction rate, I/O rate, average storage, and CPU percent. Display commands you can use include:

n DIS RSCL displays summary information about service classes from the perspective of the WLM (goal information and performance index). You can also use the display command to view three detail reports:

– DIS SCL(nnnnnnnn) to display service class information, where nnnnnnnn is a service class name.

– DIS WKL(nnnnnnnn) to display workloads, where nnnnnnnn is a workload name.

– DIS RPC(nnnnnnnn) to display report classes, where nnnnnnnn is a report class name.

What’s New in Version 520 17


Threshold for CPs expected onlineThe Set CPU Exception Thresholds panel permits you to specify a value called CPs expected online. If, during a sampling interval, the actual number of central processors (CPs) detected as being online is less than the value you specified, the CPU light on the System Status panel turns red. If the number of CPs online is greater than the value you specified, the light turns yellow.

You can analyze the problem by navigating to the Analyze CPU Problems panel or navigate directly to the System Environment panel for details.

Online documentation provided in PDF formatWith this release of OMEGAMON II for MVS, Candle Corporation has moved the manuals from IBM’s 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 MVS 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 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.

Command Groupings 19

Command Groupings

IntroductionThe command groupings listed in this chapter will assist users who want to perform a particular function, but do not remember the command name

Chapter ContentsCommand and Keyword Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

A-Matrix keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Automatic analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Batch data extract commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Batch job degradation data keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Batch utilities commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Batch workload keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Buffer keywords for the REOPEN command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Cache subsystem statistics keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Channel resource keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Collector commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23CPU utilization keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23DASD resource keyword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Datastore maintenance commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Date and time keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Degradation analysis keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Detail wait reason codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25EPILOG commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Exception analysis keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Exception filter reporting keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Exporting EPILOG data keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Fast-path navigation commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Filtering keyword for resource exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Filtering keywords for workload exceptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Historical commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

1


Historical reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34I/O queuing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Navigation commands, Fast-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Page dataset information keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Paging information keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Performance group degradation data keywords for the COMPEXT command . . . . . . 36Performance group degradation data keywords for OBTAIN/EXTRACT commands . . 36Performance group keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Performance group resource keyword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Plot scale keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Reporter commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Reporting format keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Reporting utility commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Reporting with SAS commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Resource display keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Resource exception filter keyword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Shared-DASD degradation display keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42SRM information keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Started task degradation data keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Summary wait categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Swapping information keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Time keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43TSO user session degradation data keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Utility reporting commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44VLF class statistics keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Wait categories, summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Wait reason codes, detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Workload display options keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Workload exception filter keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Workload keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Workload profile facility (WPF) commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47


Command and Keyword Groups


A-Matrix keywords

Automatic analysisSee “A-Matrix keywords” on page 21.

Batch data extract commandsSee “Reporting utility commands” on page 41.

Batch job degradation data keywords

CMAT See CREATEM.

CREATEM or CMAT

Creates a new automatic analysis member in the rhilev.midlev.RKANPAR dataset.

DELETEM or DMAT

Delete an existing automatic analysis member.

DMAT See DELETEM.

LISTM or LMAT

Lists an existing automatic analysis member from the rhilev.midlev.RKANPAR dataset.

LMAT See LISTM.

REPLACEM or RMAT

Used to add, modify, or delete wait reasons from a specified A-matrix.

RMAT See REPLACEM.

Commands and Keywords

Selects batch job or TSO session degradation data.

ACCT See ACCOUNT.


Selects batch job degradation data by JES job class.

CLS See CLASS.

JOB See JOBNAME.

JOBNAME or JOB



Batch utilities commandsSee “Reporting utility commands” on page 41.

Batch workload keywords

Selects batch job degradation data by job name.

PGM See PROGRAM.

PROGRAM or PGM

Selects batch job, started task, or TSO session degradation data by program name.



ACCT See ACCOUNT.



CLS See CLASS.

INT See INTERVAL.

INTERVAL or INT

Specifies that the data should be displayed at RMF-based intervals.

JOB See JOBNAME.

JOBNAME or JOB


PGM See PROGRAM.

PROGRAM or PGM


STARTTSK or STC

Selects started task degradation data by task name.

STC See STARTTSK.

STEP Specifies that the data should be displayed.

TSOUSER or TSO

Selects TSO session degradation data by TSO user ID.



Buffer keywords for the REOPEN command

Cache subsystem statistics keyword

Channel resource keyword

Collector commandsSee the OMEGAMON II for MVS Configuration and Customization Guide for a description of these commands.

CPU utilization keyword

DASD resource keyword

Datastore maintenance commandsSee the OMEGAMON II for MVS Configuration and Customization Guide for usage instructions for these commands.

Date and time keywords

Band|Range keywords

Date keywords

BUFND Sets the number of data buffers for the reporter to use.

BUFNI Sets the number of index buffers for the reporter to use.

RCCH Generates information about cache subsystem activity.

RCHN Generates information about physical channel activity.

RCPU Generates information about CPU activity.

RDAS Generates information about DASD device activity.

BAND Displays data between the start and end times.

RANGE or RNG

Displays data from the start time and date to the end time and date.

EDATE See ENDDATE.

ENDDATE or EDATE



Day Keywords

Specifies the end date of the display.

EXD See EXDATE.

EXDATE or EXD

Excludes the specified date(s) from the display.

LASTMONTH or LMN

Displays data from the first day to the last day of the previous month.

LASTWEEK or LWK

Displays data from Monday to Sunday of the previous week.

LASTYEAR or LYR

Displays data from the first day to the last day of the previous year.

LMN See LASTMONTH.

LWK See LASTWEEK.

LYR See LASTYEAR.

SDATE See STARTDATE.

STARTDATE or SDATE

Specifies the start date of the display.

THISMONTH or TMN

Displays data from the first day of the current month.

THISWEEK or TWK

Displays data from the first day of the current week.

THISYEAR or TYR

Displays data from the first day of the current year.

TMN See THISMONTH.

TWK See THISWEEK.

TYR See THISYEAR.

DAY See DAYOFWK.

DAYOFWK or DAY

Displays data only for the specified days.


See TODAY.

TODAY or TDAY

Displays data from the beginning of the current day.



Time keywords

Degradation analysis keywordsSee “Workload keywords” on page 46.

Detail wait reason codesSee, “Wait reason codes, detail” on page 44.

EPILOG commands

Collector commands

See the OMEGAMON II for MVS Configuration and Customization Guide for a description of these commands.

Datastore maintenance commands

See the OMEGAMON II for MVS Configuration and Customization Guide for a description of these commands.

Reporter commands

YDAY See YESTERDAY.

YESTERDAY or YDAY

Displays data from the beginning of the previous day.

ENDTIME or ETIME

Specifies the end time of the display.

ETIME See ENDTIME.

STARTTIME or STIME

Specifies the start time of the display.

STIME See STARTTIME.


Used in system navigation to return to a previous display.

CMAT See CREATEM.

CNTL See CONTROL.

COM See COMPARE.

COMPARE or COM

Compares the degradation data.

CONTROL COLOR or CNTL COLOR



Allows you to control extended color support.

CONTROL LOG or CNTL LOG

Logs the current screen to the EPILOG dataset when you press F9 or F21.

CONTROL MODE or CNTL MODE

Provides flexibility in how you format and scroll through displays.

CONTROL RECALL or CNTL RECALL

Saves keystrokes because it allows you to modify and reissue a command rather than type in the next command from scratch.

CONTROL TITLE or CNTL TITLE

Displays the report title block.

CREATEM or CMAT


DAT See DATASTOR.

DATASTOR Dynamically allocates and frees datastores during a reporter session.

DELETEM or DMAT


DIS See DISPLAY.

DISPLAY or DIS

Displays workload degradation, resource utilization, or workload profile.

DMAT See DELETEM.

END Exits the reporter. STOP and QUIT are aliases for END.

HELP Invokes the online help facility. Can be abbreviated as “H”.

INQ See INQUIRE.

INQUIRE or INQ

Makes online inquiries about the status of your EPILOG and Profile datastores.

LISTM or LMAT


LMAT See LISTM.

PAGESEP or PSEP

Formats separator pages between batch reports.

PRODUCTS

Displays the version numbers and expiration dates of all Candle background monitors.

PSEP See PAGESEP.



Utility Reporting Commands

REOPEN Modifies the number of index or data buffers used by RTA™ to read the EPILOG datastore.

REPLACEM or RMAT


RES See RESOURCE.

RESOURCE or RES

Displays the resource panels associated with the most severe wait reason.

RMAT See REPLACEM.

STEP Establishes a default workload, time period, and/or SYSID value.

TSOUSER or TSO


CMX See COMPEXT.

COMPEXT or CMX

Used to export a comparison of degradation data.

EXT See EXTRACT.

EXTRACT or EXT

Used to export data from the historical datastore in a format that is SAS® compatible.

OBT See OBTAIN.

OBTAIN or OBT

Used to export data from the EPILOG datastore to user-defined output datasets.



Exception analysis keywords

ACTIVEIO or AIO

Exclude or select delays due to an active I/O in progress.

AIO See ACTIVEIO.

APPCWAIT (or APS)

Delay due to voluntary swap-out of an idle APPC address space. (See its entry as a detail wait reason code under EXWAIT or EXW.)

AUXSTOR (or AUX)

Delay due to swaps caused by a shortage of auxiliary space. (See its entry as a detail wait reason code under EXWAIT or EXW.)

BACKUP (or BKP)

Delay due to waiting for HSM to execute a dataset backup request. (See its entry as a detail wait reason code under EXWAIT or EXW.)

CANCEL (or CAN)

Delay due to a job cancel request issued to JES. (See its entry as a detail wait reason code under EXWAIT or EXW.)

CENTSTOR (or CSS)

Delay caused by swap-out to improve central storage availability. (See its entry as a detail wait reason code under EXWAIT or EXW.)

CILOCATE (or CIL)

Delay due to waiting for HSM to execute a locate request for a converter/interpreter. (See its entry as a detail wait reason code under EXWAIT or EXW.)

COMMON (or COM)

Delay due to address spaces waiting for a PLPA or common page-in. (See its entry as a detail wait reason code under EXWAIT or EXW.)

CPUTIL (or CPU)

Time spent using CPU. (See its entry as a detail wait reason code under EXWAIT or EXW.)

CPUWAIT (or CPW)

Delay due to address spaces waiting on the active CPU dispatching queue. (See its entry as a detail wait reason code under EXWAIT or EXW.)

DELETEDS (or DLD)

Delay due to waiting for HSM to delete a dataset. (See its entry as a detail wait reason code under EXWAIT or EXW.)

DELETEJOB (or DEL)

Delay due to a job delete request issued to JES. (See its entry as a detail wait reason code under EXWAIT or EXW.)

DETECTED (or DET)



Delay due to swaps caused by a detected wait. (See its entry as a detail wait reason code under EXWAIT or EXW.)

DISKMOUNT (or DMP)

Delay due to address spaces waiting for an operator to mount a disk. (See its entry as a detail wait reason code under EXWAIT or EXW.)

ECBSTIMER (or ECS)

Delay due to ECB waits with a STIMER TASK or REAL pending. (See its entry as a detail wait reason code under EXWAIT or EXW.)

ECBWAIT (or ECB)

The address space has issued a voluntary wait for some reason. (See its entry as a detail wait reason code under EXWAIT or EXW)

ENQEXC (or EEX)

Delay due to swaps performed to make room for users that are enqueued on a resource required by other users. (See its entry as a detail wait reason code under EXWAIT or EXW.)

ENQUEUE (or ENQ)

Delay due to waiting for an enqueue. (See its entry as a detail wait reason code under EXWAIT or EXW.)

EXCHANGE (or EXG)

Delay due to exchange swaps. (See its entry as a detail wait reason code under EXWAIT or EXW.)

HLIST (or HLS)

Delay due to waiting for HSM to execute an HLIST command. (See its entry as a detail wait reason code under EXWAIT or EXW.)

HSPCPGIN (or HSP)

A hiperspace page delay. (See its entry as a detail wait reason code under EXWAIT or EXW.)

JOBSTATUS (or JST)

Delay due to a job status request issued to JES that has been queued. (See its entry as a detail wait reason code under EXWAIT or EXW.)

LONGWAIT (or LON)

Delay due to swaps caused by user-requested long waits. (See its entry as a detail wait reason code under EXWAIT or EXW.)

MIGRATE (or MIG)

Delay due to waiting for HSM to migrate a dataset. (See its entry as a detail wait reason code under EXWAIT or EXW.)

MVSLOCK (or LCK)

Delay due to address spaces waiting to acquire a local or global MVS lock. (See its entry as a detail wait reason code under EXWAIT or EXW.)



OPENMVS1 (or OM1)

Delay due to an Open MVS Swap1. (See its entry as a detail wait reason code under EXWAIT or EXW.)

OPENMVS2 (or OM2)

Delay due to an Open MVS Swap2. (See its entry as a detail wait reason code under EXWAIT or EXW.)

OUTLONG (or OLS)

Delay caused by swap-out to enable the swap-in of an address space that had been swapped out too long. (See its entry as a detail wait reason code under EXWAIT or EXW.)

PAGEIN (or PAG)

Delay due to address spaces waiting for a private page-in operation. (See its entry as a detail wait reason code under EXWAIT or EXW.)

PAGEIN (or PAG)

Delay due to address spaces waiting for a private page-in operation. (See its entry as a detail wait reason code under EXWAIT or EXW.)

QUEUEDIO (or QIO)

Delay due to waiting for queued I/O. (See its entry as a detail wait reason code under EXWAIT or EXW.)

READCTL (or RCR)

Delay due to waiting for HSM to read a control dataset record. (See its entry as a detail wait reason code under EXWAIT or EXW.)

READY (or RDY)

SRM Delay (MPL); this can occur when a domain is at the maximum MPL and a unilateral or exchange swap must occur to get the ready work swapped in. (See its entry as a detail wait reason code under EXWAIT or EXW.)

REALSTOR (or RST)

Delay due to swaps caused by a shortage of real pageable frames. (See its entry as a detail wait reason code under EXWAIT or EXW.)

RECALL (or RCL)

Delay due to waiting for HSM to recall a dataset. (See its entry as a detail wait reason code under EXWAIT or EXW.)

RECOVER (or RCV)

Delay due to waiting for HSM to recover a backup dataset. (See its entry as a detail wait reason code under EXWAIT or EXW.)

REQUEST (or REQ)

Delay due to requested swaps. (See its entry as a detail wait reason code under EXWAIT or EXW.)

REQUEUE (or RQU)



Delay due to a job requeue request to JES. (See its entry as a detail wait reason code under EXWAIT or EXW.)

RESGCAP (or RSG)

Delay due to a resource group. (See its entry as a detail wait reason code under EXWAIT or EXW.)

SRMRTO (or RTO)

Delay imposed by SRM to meet the response time objective set in the IPS. (See its entry as a detail wait reason code under EXWAIT or EXW.)

STAGING (or MSS)

Waiting for a mass storage volume to be staged. (See its entry as a detail wait reason code under EXWAIT or EXW.)

STIMER (or STI)

The address space has issued a STIMER and is voluntarily waiting for it to end. (See its entry as a detail wait reason code under EXWAIT or EXW.)

SWAPIN (or SWI)

The address space has been given to the ASM queue and is waiting for MVS to swap it into storage. (See its entry as a detail wait reason code under EXWAIT or EXW.)

SYSOUT (or PSO)

Delay due to a process SYSOUT request issued to JES that has been queued. (See its entry as a detail wait reason code under EXWAIT or EXW.)

SYSPAGE (or SPS)

Delay caused by swap-out to reduce the system page fault rate. (See its entry as a detail wait reason code under EXWAIT or EXW.)

TAPEMOUNT (or TMP)

Delay due to tape mounts. (See its entry as a detail wait reason code under EXWAIT or EXW.)

TERMIN (or TIN)

Delay due to swaps caused by waiting for terminal input. (See its entry as a detail wait reason code under EXWAIT or EXW.)

TERMOUT (or TOU)

Delay due to swaps caused by a TSO session that is waiting for an output buffer or waiting for the user to press Enter after (See its entry as a detail wait reason code under EXWAIT or EXW.)

TRANSWAP (or TSW)

Delay due to swap-outs that occur because an address space was made non-swappable. (See its entry as a detail wait reason code under EXWAIT or EXW.)

UNILATERAL (or UNI)

Delay due to swaps that occur because the MPL for a domain exceeded the target MPL. (See its entry as a detail wait reason code under EXWAIT or EXW.)



Exception filter reporting keywordsSee “Exception analysis keywords” on page 28.

Exporting EPILOG data keywords

Exporting batch job degradation data

Exporting performance group degradation data

VIOPAGIN (or VIO)

A VIO page delay. (See its entry as a detail wait reason code under EXWAIT or EXW.)

WTORWAIT (or WTO)

Delay due to a long or detected wait swap with WTOR pending. (See its entry as a detail wait reason code under EXWAIT or EXW.)

XMEMPGIN (or XME)

A cross memory page delay. (See its entry as a detail wait reason code under EXWAIT or EXW.)



ACCT See ACCOUNT.

Commands and Keywords or CLS


CLS See CLASS.

JOB See JOBNAME.

JOBNAME or JOB


PGM See PROGRAM.

PROGRAM or PGM


PERFGROUP or PGN

Allows you to select performance groups for degradation analysis.

PGN See PERFGROUP.

SYM See SYMBOLIC.

SYMBOLIC or SYM



Exporting started task degradation data

Exporting TSO user session degradation data

Fast-path navigation commandsSee “Navigation commands, Fast-path” on page 35.

Selects degradation data for a performance group.

SYS See SYSTEM.

SYSTEM or SYS

Used to display workload degradation across the entire system.



ACCT See ACCOUNT.

PGM See PROGRAM.

PROGRAM or PGM


STARTTSK or STC


STC See STARTTSK.



ACCT See ACCOUNT.

PGM See PROGRAM.

PROGRAM or PGM


TSOUSER or TSO




Filtering keyword for resource exceptions

Filtering keywords for workload exceptions

Historical commandsSee “EPILOG commands” on page 25.

Historical reportingSee “Reporter commands” on page 37.

REPORTIF or RIF

Used to specify workload or resource exception filters.

RIF See REPORTIF.

REPORTIF or RIF


RIF See REPORTIF.

SELECTIF or SIF

Used to specify workload exception filters.

SIF See SELECTIF.



I/O queuing information

Navigation commands, Fast-path

RLCU Generates information about I/O queueing.


Navigates you from the Summary display to the Detail display.

J Navigates you to the Shared-DASD Degradation display.


Navigates you to the Shared-DASD Degradation display.


Navigates you to the Resource display.

S Navigates you from the Combined display to the Single display.

V Navigates you from the DASD Resource (overall on a single system) to the DASD Resource (single device across multiple systems) display.

W Navigates you from the Summary Wait

X Navigates you from the Degradation display to the XPG display.



Page dataset information keyword

Paging information keyword

Performance group degradation data keywords for the COMPEXT command

Performance group degradation data keywords for OBTAIN/EXTRACT commands

Performance group keywords

RPDS Generates information about page dataset resource activity.

RPAG Generates information about paging and storage resource activity.

PGPERIOD or PGP

Selects performance periods for performance groups.

SYMBOLIC or SYM


SYSTEM or SYS


SYMBOLIC or SYM


SYSTEM or SYS


PGPERIOD or PGP


SYMBOLIC or SYM




Performance group resource keyword

Plot scale keyword

Reporter commands

RPGN Generates information about performance group resource activity.


See MAXSCALE.

MAXSCALE or MAX

Sets the scale for the graphic section of the summary degradation display.


Used in system navigation to return to a previous display.

CMAT See CREATEM.

CNTL See CONTROL.

COM See COMPARE.

COMPARE or COM


CONTROL COLOR or CNTL COLOR

Allows you to control extended color support.

CONTROL LOG or CNTL LOG

Logs the current screen to the EPILOG dataset when you press F9 or F21.

CONTROL MODE or CNTL MODE

Provides flexibility in how you format and scroll through displays.

CONTROL RECALL or CNTL RECALL

Saves keystrokes because it allows you to modify and reissue a command rather than type in the next command from scratch.

CONTROL TITLE or CNTL TITLE

Displays the report title block.

CREATEM or CMAT


DAT See DATASTOR.

DATASTOR

Dynamically allocates and frees datastores during a reporter session.



See also “Reporting utility commands” on page 41.

DELETEM or DMAT


DIS See DISPLAY.

DISPLAY or DIS


DMAT See DELETEM.

END Exits the reporter. STOP and QUIT are aliases for END.

HELP Invokes the online help facility. Can be abbreviated as “H”.

INQ See INQUIRE.

INQUIRE or INQ

Makes online inquiries about the status of your EPILOG and Profile datastores.

LISTM or LMAT


LMAT See LISTM.

PAGESEP or PSEP

Formats separator pages between batch reports.

PRODUCTS

Displays the version numbers and expiration dates of all Candle background monitors.

PSEP See PAGESEP.

REOPEN Modifies the number of index or data buffers used by RTA to read the EPILOG datastore.

RESOURCE or RESM or RMAT


RES See RESOURCE.

RESOURCE or RES

Displays the resource panels associated with the most severe wait reason.

RMAT See REPLACEM.

SETP Establishes a default workload, time period, and/or SYSID value.

TSOUSER or TSO

Selects TSO session degredation data by TSO user ID.



Reporting format keywords

AMAT See AMATRIX.

AMATRIX or AMAT

Specifies an Automatic Analysis matrix member of the rhilev.midlev.RKANPAR dataset.

AUTO See AUTOMATIC.

AUTOMATIC or AUTO

Displays resource panels associated with the highest wait reason.

AVERAGE or AVG

Displays average performance group figures.

AVG See AVERAGE.

CMB See COMBINE.

COMBINE or CMB

Combines intervals, job steps, or entire jobs.

COMPLETE or CMPL

Generates all display panels when the DISPLAY command is executed.

DET See DETAIL.

DETAIL or DET

Displays detailed degradation for a workload.

EXW See EXWAIT.

EXWAIT or EXW

Excludes one or more wait reasons from a degradation display.

FOLDOFF

Causes output to be written in upper and lower case characters.

FOLDON

Used to fold output to the terminal and to the log file.

INT See INTERVAL.

INTERVAL or INT


LIM See LIMIT.

LIMIT or LIM

Sets the limit for the number of display panels in the command output.

LOGOFF

Turns off logging to the log file defined by the ddname RKM2LOG.



LOGON The LOGON keyword writes out reporter displays to a log file.


See MAXSCALE.

MAXSCALE or MAX


NOPRDX

See NOPRODIDX.

NOPRODIDX or NOPRDX

Turns off the productivity index display.

PLOTMIN or PMIN

Limits the display by excluding wait reasons.

PLOT See PLOTMIN.

PRDD See PRDXDEF.

PRDX See PRODIDX.

PRDXDEF or PRDD

Specifies a productivity index definition member of rhilev.midlev.RKANPAR.

PRODIDX or PRDX

Turns on the productivity index display.

SHORT Indicates that the report title block should be in a condensed format.

Specifies that the data should be displayed.

SUM See SUMMARY.

SUMD See SUMDEF.

SUMDEF or SUMD

Specifies a summary wait definition member of rhilev.midlev.RKANPAR.

SUMMARY or SUM

Displays only the most important wait reason.

SUMW See SUMWAIT.

SUMWAIT or SUMW

Summarizes the display by grouping similar wait reasons.

SYS See SYSID.

SYSID or SYS

Combines data from selected systems by SMF ID.

TITLE Produces one line of a possibly multi-line report title.



Reporting utility commands

Reporting with SAS commands

TITLE2 Produces one line of a possibly multi-line report title.

TITLE3 Produces one line of a possibly multi-line report title.

TOT See TOTAL.

TOTAL or TOT

Displays total performance group figures.

TWAITOF

See TWAITOFF.

TWAITOFF or TWAITOF

Excludes swaps due to terminal input waits in the degradation display.

TWAITON

Includes swaps due to terminal input waits in the degradation display.

CMX See COMPEXT.

COMPEXT or CMX


EXT See EXTRACT.

EXTRACT or EXT

Used to export data from the historical datastore in a format that is SAS compatible.

OBT See OBTAIN.

OBTAIN or OBT


CMX See COMPEXT.

COMPEXT or CMX


EXT See EXTRACT.

EXTRACT or EXT




Resource display keywords

Resource exception filter keyword

Shared-DASD degradation display keywords

SRM information keywords

RALL Generates information about all resource types.

RCCH Generates information about cache subsystem activity.

RCHN Generates information about physical channel activity.

RCPU Generates information about CPU activity.

RDAS Generates information about DASD device activity.

RDOM Generates information about SRM domain activity.

RINF Generates information about the status of general system resources.

RLCU Generates information about I/O queueing.

RPAG Generates information about paging and storage resource activity.

RPDS Generates information about page dataset resource activity.

RPGN Generates information about performance group resource activity.

RSDS Generates information about swap dataset resource activity.

RSCL Generates summary information about service classes from the perspective of the WLM.

RSRM Generates information about SRM MPL adjustment values.

RSWA Generates information about swapping activity.

RSWR Generates information about swap reasons.

RVLF Generates information about VLF class activity.

REPORTIF or RIF


RIF See REPORTIF.

JDAS Displays shared-DASD usage by workload.

PDAS Displays shared-DASD degradation for the indicated device.

RDOM Generates information about SRM domain activity.

RSRM Generates information about SRM MPL adjustment values.



Started task degradation data keywords

Summary wait categories

Swapping information keywords

Time keywords



ACCT See ACCOUNT.

PROGRAM or PGM


STARTTSK or STC


STC See STARTTSK.

REPORTIF or RIF


SUMWAIT or SUMW


RSDS Generates information about swap dataset resource activity.

RSWA Generates information about swapping activity.

RSWR Generates information about swap reasons.

ENDTIME or ETIME

Specifies the end time of the display.

ETIME See ENDTIME.

STARTTIME or STIME

Specifies the start time of the display.

STIME See STARTTIME.



TSO user session degradation data keywords

Utility reporting commands

VLF class statistics keyword

Wait categories, summary

Wait reason codes, detail



PROGRAM or PGM


TSOUSER or TSO


CMX See COMPEXT.

COMPEXT or CMX


EXT See EXTRACT.

EXTRACT or EXT


OBT See OBTAIN.

OBTAIN or OBT


RVLF Generates information about VLF class activity.

SUMWAIT or SUMW


ACTIVEIO or AIO

Exclude or select delays due to an active I/O in progress.

ENQUEUE or ENQ

Excludes or selects delays due to waiting for an enqueue.



For a complete list of detail wait reason codes, see “EXWAIT or EXW” on page 100.

Workload display options keywords

QUEUEDIO or QIO

Exclude or select delays due to waiting for queued I/O.

AVERAGE or AVG

Displays average performance group figures.

DETAIL or DET

Displays detailed degradation for a workload.

EXWAIT or EXW

Excludes one or more wait reasons from a degradation display.

MAXSCALE or MAX


PLOTMIN or PMIN

Limits the display by excluding wait reasons.

STEP Specifies that the data should be displayed.

SUMMARY or SUM

Displays only the most important wait reason.

SUMWAIT or SUMW


TOTAL or TOT

Displays total performance group figures.

TWAITOFF or TWAITOF

Excludes swaps due to terminal input waits in the degradation display.

TWAITON

Includes swaps due to terminal input waits in the degradation display.



Workload exception filter keywords

Workload keywords

REPORTIF or RIF


SELECTIF or SIF

Used to specify workload exception filters.



ACCT See ACCOUNT.

Commands and Keywords or CLS


CLS See CLASS.

INT See INTERVAL.

INTERVAL or INT


JOBNAME or JOB


PGPERIOD or PGP


PGM See PROGRAM.

PROGRAM or PGM


REPTCLAS or RPC

Selects Workload Manager report class task degradation data by task name.

SERVCLAS or SCL

Selects Workload Manager service class task degradation data by task name.

STARTTSK or STC


STC See STARTTSK.

SYMBOLIC or SYM


SYSTEM or SYS




Workload profile facility (WPF) commands

TSOUSER or TSO


WORKLOAD or WKL

Specifies the workload name.

COMPARE or COM


DISPLAY or DIS


PROFILE or PROF

Creates a profile by averaging degradation data for a workload.

STEP Establishes a default workload, time period, and/or SYSID value.

A Commands and Keywords 49

A Commands and Keywords

Chapter ContentsCommands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

ACCOUNT or ACCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50ACCT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51ACTIVEIO or AIO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53AIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53AMAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53AMATRIX or AMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53APPEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54AUTO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54AUTOMATIC or AUTO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54AVERAGE or AVG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57AVG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

2




ACCOUNT or ACCTType: EPILOG Keyword

Description: Selects batch job or TSO session degradation data by installation account code. The operand for this keyword is 1–12 characters long; it also accepts a wildcard (*) character.

If the JOB or TSO keyword is included with the command, a single display panel is generated for each job run or TSO session that meets the ACCOUNT criteria. If neither of these keywords is included (or if you are not collecting data by intervals), a separate display panel is generated for each job or session step that meets the ACCOUNT criteria.

ACCOUNT is not compatible with the STARTTSK keyword.

For example,

Display TSO(*) ACCT(4301) INTERVAL

displays degradation data for all TSO user sessions that ran in account group 4301. The INTERVAL keyword specifies that a separate display panel is generated for each interval.

When Exporting Data to SAS®

Since ACCOUNT can be used to select batch jobs, started tasks, and TSO user sessions, you might write to several SAS datasets with a single EXTRACT command using ACCOUNT. Depending upon the type of degradation data being exported, EXTRACT...ACCOUNT... or COMPEXT...ACCOUNT... writes the following data elements to the respective SAS report:

n Batch job degradation data (SAS dataset BTCHCOMP): ACCTCDE, DEVADD, DPRODIDX, DTRXELAP, DWAITTME, EDATTIME, ENQNAME, JESCLASS, JESNUM, JOBNAME, PACCTCDE, PAVGELAP, PDATTIME, PEDATTIM, PGMNAME, PJESCLAS, PJOBNAME, PPGMNAME, PPRODIDX, PRODIDX, PROFNAME, PSDATTIM, PSMFID, PWAITPCT, PWAITTME, PWKLNAME, SDATTIME, SMFID, TRXELAP, VOLSER, WAITNAME, WAITPCT, WAITTIME, and WKLNAME.

n Batch job degradation data (SAS dataset BTCHDETL): ACCTCDE, CPUTRXTM, DEVADD, EDATE, EDATTIME, ETIME, ENQNAME, EXTDTIME, HIGHSTEP, JESCLASS, JESNUM, JOBNAME, NUMICMB, PGMNAME, PROCNAME, PRODIDX, RDRTIME, SDATE, SDATTIME, STIME, SMFID, STEPNAME, TRXELAP, VOLSER, WAITNAME, WAITPCT, WAITTIME, and WKLNAME.

n Started task degradation data (SAS dataset STCCOMP): ACCTCDE, DEVADD, DPRODIDX, DTRXELAP, DWAITTME, EDATTIME, ENQNAME, JESNUM, PACCTCDE, PAVGELAP, PDATTIME, PEDATTIM, PGMNAME, PPGMNAME, PPRODIDX, PRODIDX, PROFNAME, PSDATTIM, PSMFID, PSTCNAME, PWAITPCT, PWAITTME, PWKLNAME, SDATTIME, SMFID, STCNAME, TRXELAP, VOLSER, WAITNAME, WAITPCT, WAITTIME, and WKLNAME.



n Started task degradation data (SAS dataset STCDETL): CPUTRXTM, DEVADD, EDATE, EDATTIME, ETIME, ENQNAME, EXTDTIME, HIGHSTEP, JESNUM, NUMICMB, PGMNAME, PROCNAME, PRODIDX, SDATE, SDATTIME, STIME, SMFID, STCNAME, STEPNAME, TRXELAP, VOLSER, WAITNAME, WAITPCT, WAITTIME, and WKLNAME.

n TSO user session degradation data (SAS dataset TSOCOMP): ACCTCDE, DEVADD, DPRODIDX, DTRXELAP, DWAITTME, EDATTIME, ENQNAME, JESNUM, PACCTCDE, PAVGELAP, PDATTIME, PEDATTIM, PPRODIDX, PRODIDX, PROFNAME, PSDATTIM, PSMFID, PTSOUSER, PWAITPCT, PWAITTME, PWKLNAME, SDATTIME, SMFID, TRXELAP, TSOUSER, VOLSER, WAITNAME, WAITPCT, WAITTIME, and WKLNAME.

n TSO user session degradation data (SAS dataset TSODETL): ACCTCDE, CPUTRXTM, DEVADD, EDATE, EDATTIME, ETIME, ENQNAME, EXTDTIME, JESNUM, NUMICMB, PRODIDX, SDATE, SDATTIME, STIME, SMFID, TRXELAP, TSOUSER, VOLSER, WAITNAME, WAITPCT, WAITTIME, and WKLNAME.

These data elements are defined in the Data Dictionary appendix to this manual.

Note: The EPILOG collector requires a certain amount of SQA to collect account, class, and program information for various workloads. Under normal conditions, this amount is automatically calculated and allocated during collector startup. However, one of the collector options (SQAMAX) limits the maximum amount of SQA that can be allocated by the collector, and if this limit is set too low, collection of information for the ACCOUNT, CLASS, and PROGRAM keywords is affected. If you use these keywords and suspect that some records are missing, you should check to see if the SQAMAX keyword has been used in the collector options. If it has, you may want to increase the maximum SQA available to the collector.

Related Information: Keyword of: COMPARE, COMPEXT, DISPLAY, EXTRACT, INQUIRE, OBTAIN, PROFILE, and SETP

Other Workload Keywords: See Workload Keywords in “Command Groupings” on page 19.

ACCTType: EPILOG Keyword

Description: See ACCOUNT.

Related Information: None

ACTIVEIO or AIOType: EPILOG Detail Wait Reason Code

Description: Used in exception analysis to exclude or select delays due to an active I/O in progress. The valid device and enqueue operands are:

ALLWAITS Exception applies to the sum of all the I/O or ENQ waits.

ANY Exception applies to any I/O or ENQ wait.



DASD(cuu or nnnn) or D (cuu or nnnn)

Exception applies only to the specified DASD device (cuu = the device address in MVS/370; nnnn = the device number in MVS/XA™ and above). (This option is allowed with the NO prefix; the NODASD exception applies if no DASD waits were seen.)

DISK(cuu or nnnn) or D (cuu or nnnn)

Exception applies only to the specified DASD device. (This option permits the NO prefix; the NODISK exception applies only if no DASD waits were seen.)

EVERY Exception applies only if all I/O or ENQ waits exceed the threshold.

TAPE(cuu or nnn) or T (cuu or nnnn)

Exception applies only to the specified tape device. (This option is allowed with the NO prefix; the NOTAPE exception applies only if no tape waits were seen.)

UNIT(cuu or nnn) or U (cuu or nnnn)

Exception applies only to the specified disk or tape device. (This option is allowed with the NO prefix; the NOUNIT exception applies only if no disk or tape waits were seen.)

VOLUME(volser) or V (volser)

Exception applies only to the device with the specified volser. (This option is allowed with the NO prefix; the NOVOLUME exception applies only if no volser waits were seen.)

MAJOR(enqname) or M (enqn)

Exception applies only to specified major enqueue name. This operand requires an additional argument, selected from the following list:

MISC SYS Miscellaneous SYS prefixed enqueue. Any detected enqueue that does not match the names specified with the ENQUEUE keyword on the OPTIONS statement is put into one of two categories: MISC SYS or MISC USR. MISC SYS contains system enqueues. If you specify this category as a major name with REPORTIF or SELECTIF, you must enclose it in quotes because it contains a blank space.

MISC USR Miscellaneous USR prefixed enqueue. Any detected enqueue that does not match the names specified with the ENQUEUE keyword on the OPTIONS statement is put into one of two categories: MISC SYS or MISC USR. MISC USR contains user enqueues. If you specify this category as a major name with REPORTIF or SELECTIF, you must enclose it in quotes because it contains a blank space.

SYSDSN System major for dataset integrity.

SYSIEA01 Dump dataset.

SYSIEFSD Scheduler and allocation serialization.



For example,

Display PGN(2) SIF(AIO(VOLUME(VSRESA)>5%)) THISWEEK

displays all intervals in which performance group 2 was performing active I/O to VSRESA more than 5% of the time.

Related Information: Operand of Keywords: EXWAIT, REPORTIF, and SELECTIF

ADDType: EPILOG Keyword

Description: Adds one or more datastores to the end of the active datastore list.

Related Information: Keyword of: DATASTOR

AIOType: EPILOG Detail Wait Reason Code

Description: See ACTIVEIO.


AMATType: EPILOG Keyword

Description: See AMATRIX.


AMATRIX or AMATType: EPILOG Keyword

Description: Specifies an Automatic Analysis matrix member of rhilev.midlev.RKANPAR. (The A-matrix is used to associate resource panels with detail wait reasons, and is invoked during system navigation, with the AUTO keyword, and with the RESOURCE command.) By

SYSIEWLP Linkage editor syslmod serialization.

SYSIGGV1 Master catalog open.

SYSIGGV2 VSAM catalog serialization.

SYSIKJBC Broadcast dataset serialization.

SYSSMF01 SMF dataset serialization.

SYSVSAM VSAM CI serialization.

SYSVTOC DADSM VTOC update serialization.

SYSZJES2 JES2 spool space. For JES3 systems, modify the major name default to SYSZJES3.

SYSZVARY CPU reconfiguration.



default, these displays use the KEPDEF@ member of rhilev.midlev.RKANPAR; the AMATRIX keyword allows you to specify another member.

The operand for this keyword is 1–7 characters long.

In the example below, EPILOG uses the A-matrix called MYMAT instead of DEFAULT to make its decisions:

DISPLAY PGN(2) TODAY AUTO AMATRIX(MYMAT)

Related Information: Keyword of: DISPLAY, EXTRACT, OBTAIN, RESOURCE, and SET

Other Reporting Format Keywords: See Reporting Format Keywords in “Command Groupings” on page 19.

APPENDType: EPILOG Keyword

Description: Specifies that data exported with OBTAIN should add (append) records to the end of the file, without overwriting any records already in the file.

Related Information: Keyword of: OBTAIN and SET

AUTOType: EPILOG Keyword

Description: See AUTOMATIC.


AUTOMATIC or AUTOType: EPILOG Keyword

Description: Displays resource panels associated with the highest (or specified) wait reason on a degradation display. The panels associated with a given wait reason are defined in an Automatic Analysis matrix (a user-defined table which tells EPILOG what resource panels you consider relevant to each type of bottleneck), whose member name is specified with the AMATRIX keyword.

The AUTOMATIC keyword is not compatible with SUMMARY.

EPILOG has a feature called Automatic Resource Reporting which automatically generates the resource panels associated with the most significant wait reason.

For example, suppose we want to look for all intervals today where the response time for TSO was greater than 1.5 seconds. If we add the AUTOMATIC keyword (or AUTO for short) to the request, EPILOG automatically finds the most significant wait reason (that is, the one with the highest percentage) and looks it up in the DEFAULT Automatic Analysis matrix. Based on what it finds there, it automatically generates certain resource panels for the corresponding interval.

In the following example, the most significant wait reason was Private Page-In Wait. The first two resource panels for this wait reason, as specified in the DEFAULT A-matrix, are



Paging and Storage (RPAG) and Page Dataset Activity (RPDS). These automatically appear when you enter AUTO as part of the command:

DIS PGN(2) TODAY RIF(RESP(>1.5S)) AUTO

The resulting displays might look like the following examples:

+=============================================================================+| Performance Group = 2 Symbolic Name = TSO || From 11:30 to 11:45 on 09/07/99 Elap = 15:00 M SYSA |+-----------------------------------------------------------------------------+|Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0||Using CPU 0.06 S 4.0|-> . . . . . . . . . .||Private Page-In Wait 0.26 S 16.4|------> . . . . . . . . .||Terminal Output Wait 0.18 S 11.3|----> . . . . . . . . .||Waiting for CPU 0.15 S 9.9|--->. . . . . . . . . .||Swap Page-In Wait 0.12 S 7.7|--->. . . . . . . . . .||Disk DEV023 36D Act 0.11 S 7.4|--> . . . . . . . . . .||Disk DEV022 151 Que 0.08 S 5.1|--> . . . . . . . . . .||Average Trans Time 1.60 S 705 MVS Transactions Ended ||Productivity Index 15% |+=============================================================================++=========================== Paging and Storage ==============================+| Period: 11:30 to 11:45 on 09/07/99 Elap =15:00 M A083 |+-----------------------------------------------------------------------------+| |Virtual | Average Frame Counts | Page/sec. | Swap paging/sec. || | Memory | Real = Fixed + Non-Fix| In | Out | In Out |+-----+--------+--------+--------+--------+--------+--------+--------+--------+| SQA | 512K | 173 | 173 | | | | | || LPA | 4380K | 405 | 20 | 385 | 3.2 | | | || CSA | 3004K | 172 | 61 | 111 | .8 | .5 | | |+-----+--------+--------+--------+--------+--------+--------+--------+--------+| LSQA| | 223 | 223 | | | | | || Pvt | 7552K | 2407 | 177 | 2230 | 8.3 | 5.9 | 41.0 | 40.9 || Free| | 235 | | 235 | | | | |+-----+--------+--------+--------+--------+--------+--------+--------+--------+| Nuc | 896K | 224 | 224 | | | | | |+-----+--------+--------+--------+--------+--------+--------+--------+--------+|Total| 16384K | 3839 | 878 | 2961 | 12.4 | 6.5 | 41.0 | 40.9 |+-----+--------+--------+--------+--------+--------+--------+--------+--------+| | | Total Pages / second | 18.9 | 81.9 |+=============================================================================+

+========================== Page Dataset Activity ============================+| Period: 11:30 to 11:45 on 09/07/99 Elap =15:00 M A083 |+-----------------------------------------------------------------------------+| Space Dev Dev % % In I/O’s Pages Trnsfr || Type Adr VOLSER Type Full Use per sec per IO Time || ------ --- ------ ---- ----- ----- ------- ------ ------ || PLPA 150 MVSA21 3380 57.3 13.0 2.7 1.2 .040 || Common 140 SYS021 3380 27.5 7.3 .8 1.6 .054 || Local 143 TIME21 3380 35.7 27.6 2.6 9.2 .011 || Local 153 TIME22 3380 35.3 28.0 2.6 9.2 .012 || Local 141 TSO021 3380 32.9 24.2 2.4 10.1 .010 || Local 151 TSO022 3380 33.1 28.4 2.6 9.1 .012 |+=============================================================================+



The other resource panels associated with private page-in waits (RCHN, RCPU, and RINF) would be displayed after the RPAG and RPDS.



If, when using AUTO, you specify other exception criteria in addition to response time, EPILOG displays the resource panel(s) for those other criteria, even if they do not reflect the most significant bottleneck. To illustrate, in the example below, we have asked only for intervals with poor response time, where waiting for CPU (CPW) makes up more than 10 percent of an average transaction. Even though CPW is not the most significant wait reason (disk active and disk queued for device 36D are higher), AUTO produces a resource panel for CPW (RCPU in this case).

DIS PGN(2) TODAY RIF(RESP(>1.5S) CPW(>10%) ) AUTO

The resulting display might look like this:

Note that the AUTO keyword is only valid when you request a DETAILed degradation display (that is, if you omit the SUMMARY keyword).

By default, the A-matrix called DEFAULT selects the associated resource panels. You can override this with the AMATRIX keyword in combination with AUTO. In the example below, EPILOG uses the A-matrix called MYMAT instead of DEFAULT to make its decisions:

DISPLAY PGN(2) TODAY AUTO AMATRIX(MYMAT)

Related Information: Keyword of: DISPLAY, EXTRACT, OBTAIN, and SET


AVERAGE or AVGType: EPILOG Keyword

Description: Displays average performance group figures, and combines the data over the time range specified in the command.

+=============================================================================+| Performance Group = 2 Symbolic Name = TSO || From 12:30 to 12:45 on 09/07/99 Elap = 15:00 M SYSA |+-----------------------------------------------------------------------------+|Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0||Using CPU 0.09 S 5.6|--> . . . . . . . . . .||Disk DEV023 36D Act 0.22 S 13.2|-----> . . . . . . . . .||Disk DEV023 36D Que 0.21 S 12.2|----> . . . . . . . . .||Waiting for CPU 0.20 S 12.0|----> . . . . . . . . .||Private Page-In Wait 0.16 S 9.5|--->. . . . . . . . . .||Swap Page-In Wait 0.12 S 7.2|--> . . . . . . . . . .||Disk DEV022 151 Act 0.12 S 7.1|--> . . . . . . . . . .||Average Trans Time 1.72 S 501 MVS Transactions Ended ||Productivity Index 25% |+=============================================================================++============================== CPU Activity =================================+| Period: 12:30 to 12:45 on 09/07/99 Elap =15:00 M A083 |+-----------------------------------------------------------------------------+| Min Max Avg Ready Users CPU Utilization || --- --- ---- ----------- ------------------------------ || Batch 0 1 .4 In = 1.3 SRB = 3.6 % CPU2 = 43.8 % || STC 27 28 27.5 Out = .1 TCB = 28.4 % || TSO 12 19 15.1 MVS = 11.8 % |+=============================================================================+



By default, performance group information is displayed as average figures for each interval. These figures are calculated by dividing the total transaction elapsed time by the number of transactions that ended during the interval. AVERAGE allows you to display average transaction time over a specified period of time.

The AVERAGE keyword differs from the default in that it shows average figures over the specified time period instead of the individual RMF interval. This has exactly the same effect as adding the COMBINE keyword to the command without an operand.

For example,

DISPLAY PGN(2) AVERAGE YESTERDAY

displays:

Notice that the AVERAGE display combines all intervals for the specified time period (YESTERDAY), and shows you the following information:

n the start and end time/dates of the display

n the number of intervals combined in the display

n the average transaction time and the number of transactions that ended during the period

Related Information: Keyword of: DISPLAY, EXTRACT, and OBTAIN


AVGType: EPILOG Keyword

Description: See AVERAGE.


+=============================================================================+ | Performance Group = 2 Symbolic Name = DEV TSO | | From 00:16 To 24:00 On 08/29/99 SYSA | | Average Of 94 Intervals | +-----------------------------------------------------------------------------+ |Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0| |Using CPU 0.06 S 4.6|-> . . . . . . . . . .| |Long Wait 0.60 S 43.4|------------=====> . . . . . .| |Waiting For CPU 0.17 S 12.2|----> . . . . . . . . .| |Average Trans Time 1.39 S 80948 MVS Transactions Ended | |Productivity Index 7% | +=============================================================================+

B Commands and Keywords 59

B Commands and Keywords


BACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60BAND. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60BLOCK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60BUFND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61BUFNI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

3




BACKType: EPILOG Reporter Command

Description: This navigation command returns you to the previous display.

Related Information: Other Reporter Commands: See Reporter Commands in “Command Groupings” on page 19.

BANDType: EPILOG Keyword

Description: Displays data between the start and end times on the specified days. BAND is the default value and treats the specified period as a series of periods. For example,

DISPLAY...STARTDATE(9/05/99) STARTTIME(0900)-

ENDDATE(9/10/99) ENDTIME(1700)

displays the data gathered between the hours of 9:00 AM-5:00 PM on the specified days. If you had specified RANGE instead of BAND, the data display would begin at 9:00 AM on 9/5/99 and end at 5:00 PM on 9/10/99.

The keywords BAND and RANGE are mutually exclusive.

Related Information: Keyword of: DISPLAY, EXTRACT, OBTAIN, PROFILE and SET

Other Date and Time Keywords: See Date and Time Keywords in “Command Groupings” on page 19.

BLOCKType: EPILOG Keyword

Description: Formats the specified report title in 5x7 block letters. The operand for this keyword is a report title. For example,

PAGESEP DUP(3) BLOCK(‘ROOM 1’) TITLE3(‘SPECIAL REPORT’) -

TITLE(‘TO THE DIRECTOR’)

produces the following page separator:

B Commands and Keywords 61


Related Information: Keyword of: PAGESEP

BUFNDType: EPILOG Keyword

Description: Sets the number of data buffers for the reporter to use when reopening the EPILOG datastore. The default is 10.

Related Information: Keyword of: REOPEN

Other Buffer Keyword for the REOPEN Command: BUFNI

BUFNIType: EPILOG Keyword

Description: Sets the number of index buffers for the reporter to use when reopening the EPILOG datastore. The default is 20.

Related Information: Keyword of: REOPEN

Other Buffer Keyword for the REOPEN Command: BUFND

******************************************************************************** ** ** **** *** *** * * * ** * * * * * * ** ** ** ** * * * * * * * * * * * ** **** * * * * * * * ** * * * * * * * * * ** * * * * * * * * * ** * * *** *** * * ***** ** ** ** SPECIAL REPORT ** TO THE DIRECTOR ** ** ********************************************************************************

C Commands and Keywords 63

C Commands and Keywords


CLASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64CLEAR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65CLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65CMAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65CMB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65CMPL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65CMX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65CNTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65COM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66COMBINE or CMB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66COMPARE or COM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68COMPEXT or CMX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72COMPLETE or CMPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75CONTROL COLOR or CNTL COLOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76CONTROL LOG or CNTL LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78CONTROL MODE or CNTL MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78CONTROL RECALL or CNTL RECALL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79CONTROL TITLE or CNTL TITLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79CREATEM or CMAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

4




CLASSType: EPILOG Keyword

Description: Selects batch job degradation data by JES job class. The operand for this keyword is 1 character. This keyword accepts a wildcard (*) character.

If the JOB keyword is included with the command, a separate display panel is generated for each job that meets the JOB and CLASS criteria. If JOB is not included (or if you are not collecting data by intervals), a separate display panel is generated for each job step that meets the CLASS criteria.

CLASS is not compatible with the STARTTSK or TSOUSER keywords. For example, to select batch workloads of class Q or class F, enter:

DISPLAY CLASS(Q,F)

When Exporting Data to SAS

When exporting data to SAS, this keyword writes the following data elements to the respective SAS report:



These data elements are defined in the Data Dictionary appendix of this manual.






CLEARType: EPILOG Keyword

Description: When CLEAR is used with the SET command, all previously established SET defaults are cancelled (as if the reporter had been stopped and another session started). Similarly, when CLEAR is used with the SETP command, all previously established SETP defaults are cancelled.

Related Information: Keyword of: SET and SETP

CLSType: EPILOG Keyword

Description: See CLASS.


CMATType: EPILOG Reporter Command

Description: See CREATEM.


CMBType: EPILOG Keyword

Description: See COMBINE.


CMPLType: EPILOG Keyword

Description: See COMPLETE.


CMXType: EPILOG Reporting Utility Command

Description: See COMPEXT.


CNTLType: EPILOG Reporter Command

Description: See CONTROL.




COMType: EPILOG Reporter Command

Description: See COMPARE.


COMBINE or CMBType: EPILOG Keyword

Description: Combines intervals, job steps, or entire jobs into larger reporting units. The operand for this keyword is a time period (for example, 24H or 30M).

Degradation and resource data that has been collected over multiple time intervals can be summarized using the COMBINE keyword. Performance groups and system resources are monitored continuously, and data for them is collected and stored in increments corresponding to the RMF interval. The COMBINE keyword is used to summarize this data over longer periods of time. Since batch workloads do not run continuously, however, this method of summarization does not apply to them. COMBINE summarizes batch workload data according to the keywords you use in the command; that is, by job name, program, account code, or class. If data was collected at termination time, you can use the COMBINE keyword to combine steps together, or combine together selected job runs, TSO sessions, or started tasks.

COMBINE is not compatible with INTERVAL or STEP.

For example,

DISPLAY PERFGROUP(7) SUMMARY COMBINE(1H) -

STARTTIME(8:00) ENDTIME(10:00) -

STARTDATE(1/9/99) ENDDATE(1/13/99)

displays historical data for performance group 7, for the time period 8:00 AM to 10:00 AM during the date period 1/9/99 to 1/13/99, combines the data into hourly intervals, and shows only the most important wait reason in each interval display. In other words, this command shows hourly system views of activity in the analyzed region.

If you do not supply a combined interval length with the COMBINE keyword, then all the intervals between the start time and end time are combined into one display. For example, to see a COMBINEd resource display of CPU activity from 9:00 AM to 5:00 PM, enter:

DISPLAY RCPU YESTERDAY STIME(9) ETIME(17) COMBINE

The result is a single display panel for the entire day.

The following command combines records across MVS systems:

DIS RDAS STIME(10) ETIME(11) TODAY SYSID(MERGE) COMBINE(1H)



The result is shown below.

In this example, the COMBINE keyword generates a single cross-system display of DASD device activity for each one hour interval. When the COMBINE keyword is used without the SYSID(MERGE) keyword, records with different SYSIDs are not combined.

Deciding upon a Time Interval:

The time interval length specified as an operand of COMBINE should generally be an even multiple of your RMF collection interval length. Using an interval which is not an even multiple, while allowed, can often (not surprisingly) cause displays which are irregular, confusing, or difficult to use. You should also not use an interval shorter than your RMF collection interval. If you are specifying your interval in hours, we recommend that you use a number that divides evenly into 24, that is, 1, 2, 3, 4, 6, 8, or 12.

Guidelines for Using Combine with Batch Jobs, Started Tasks, and TSO Sessions

n If the INTERVAL keyword is used to display data by RMF-based intervals, then the data is reported by RMF-based intervals, and COMBINE is not allowed.

n If the INTERVAL keyword is not included on the display command, but data was collected by intervals, the data is automatically combined into a single display panel, according to the time/date range specified on the command. The COMBINE keyword in this instance is superfluous.

n If the data was not collected by intervals and data is being displayed at the step level (by use of the ACCOUNT, PROGRAM, or CLASS keyword) and the COMBINE keyword is used, then all steps that meet the criteria are combined into a single display panel. (Note that steps can only be combined when ACCOUNT, PROGRAM, or CLASS is used without JOB, STC, or TSO. This is because the STEP keyword, which is used with JOB, STC, and TSO to display data at the step level, is not allowed with the COMBINE keyword.)

n If the data was not collected by intervals and data is being displayed at the job, started task, or TSO session level, then all jobs, tasks, or sessions that meet the criteria are combined into a single display panel.

+========================== DASD Device Activity =============================+| From: 10:00 to 11:00 on 10/18/99 Elap = 1:00 H || Sysid: SYSA SYSF || Combination and Merge of 8 Intervals |+-----------------------------------------------------------------------------+|Volume SMF Dev I/O -------- Time in Milliseconds -------- % Dev Avg||Serial id # LCU Rate Total = IOSQ+Pend+Conn+Disc CUB DB Util Allcs||------ ---- --- --- ---- ----- ---- ---- ---- ---- ---- ---- ----- -----||CHKPT1 SYSA 150 00C 1.1 69 0 48 7 14 47.8 17.2 1.0|| SYSF 150 00A 1.0 32 0 10 7 15 9.5 22.0 1.0||COM001 SYSA D89 055 6.8 16 4 3 6 3 .2 2.0 5.7 134.2|| SYSF D89 056 4.5 10 1 2 4 3 .2 1.6 4.0 381.0||COM002 SYSA D8A 055 .3 14 0 5 6 3 1.9 2.3 .2 223.5|| SYSF D8A 056 1.3 19 1 3 6 9 .3 2.6 3.7 168.1|+=============================================================================+





See also INTERVAL, SINGLE, and STEP.

COMPARE or COMType: EPILOG Reporter Command

Description: Compares the degradation data for a given workload with that of a profile. Unless preceded by a SETP command directing otherwise, the COMPARE command chooses the most current profile for the workload and PROFNAME that you have specified.

COMPARE {workload} -

{PROFNAME(cc...cc)} -

[time period] -

[SYSID(cccc,...)] -

[REPORTIF(filter)] -

[IODEVICE] -

[LINECNT(nnnnn)] -

[SUMWAIT]-

[SUMMARY]

workload Identifies the group of jobs or performance group you are selecting for comparison with a profile. You can use any of the workload keywords, as listed in Workload Keywords in the “Command Groupings” on page 19, except STEP and INTERVAL.

PROFNAME(cc...cc) or PNAME (cc...cc)

Defines the 1- to 16-character profile name of the profile against which you want to compare the historical datastore records. Typically, this is the name you assigned to the specified workload when you created its profile with the PROFILE command. If you created the profile with the PNAME default (that is, automatic), simply specify PNAME without any operand. Note that you cannot use the asterisk as a substitute for a profile name or for any part of a profile name.



time period Specifies the date and/or time interval for which you are selecting the specified workload’s degradation data (historical datastore records). Use any of the date/time keywords as listed in Date and Time Keywords in the “Command Groupings” on page 19. If no time period is given, all historical datastore records for the specified workload are selected.

Note that your time period specification applies only to the selection of workload data from the historical datastore. Unless you have indicated otherwise on a prior SETP command, the profile selected is the most current profile for the workload, PROFNAME, and SYSID that you have specified on the command.

SYSID(cccc,...) Specifies the SMF System ID for the workload you are comparing. Required only when the records in your datastores contain different SYSIDs and you want to compare a workload and profile with a specific SYSID. If you specify multiple SYSIDs, for example (SYSA,SYSB), you will compare each workload-profile combination with a corresponding SYSID that meets your other comparison criteria. If no SYSID is specified, the specified workload and the most recent profile that meet your other comparison criteria will be compared regardless of SYSID. If you want to compare a profile that has a SYSID different from that specified on the COMPARE command, you may do so by setting the SYSID of the profile with the SETP command.

REPORTIF(filter) Specifies the criteria that workload records must satisfy to be included in a comparison. The REPORTIF keyword must be followed by a valid wait reason and appropriate reporting criteria. Use any of the exception-threshold keywords (detail wait reason codes, summary wait categories, RESP, or ELAP). In addition, you may apply the filter (ELAP(>nn%) or RESP(>nn%)) to indicate that you want to compare only those workload records with an elapsed (ELAP) or response (RESP) time nn% greater than the profile’s.

IODEVICE or IODEV

Allows you to override the generic listing of device wait reasons, the default, with a detailed I/O device listing.

When using the IODEVICE keyword, you should keep in mind that, in the profiles of some workloads, a considerable number of devices may be associated with the various wait reasons. Therefore, specifying IODEVICE may produce a rather lengthy report. To limit the comparison to the most significant wait reasons, use the LINECNT keyword.

LINECNT(nnnnn) or LCNT(nnnnn)

Specifies the maximum number of wait-reason lines that you want to display. When specified together with SUMMARY, LINECNT limits the number of records to be displayed. You may specify any number from 0 to 32767. The default is LINECNT(20). Note that Using CPU and the averaged response- or elapsed-time lines will always be displayed and are not counted as wait reasons.

SUMWAIT or SUMW

Indicates that summary wait categories should be displayed instead of detailed wait reasons.



Notes:

n The COMPARE command can only be used to compare a specific workload type to a profile.

n The REPORTIF filter applies only to the historical datastore records for the specified workload and not to the profiles.

n You must precede the COMPARE command with a SETP command whenever the profile you want for the comparison has a workload name, time period, or SYSID different from the most current profile for PROFNAME on the COMPARE command.

For example,

COMPARE JOB(PAYROLL) -

PNAME(PAY) -

TODAY -

RIF(ELAPSED(>15%))

displays a report comparing the current day’s job named PAYROLL with a profile created for the same workload. Because no SETP command was issued prior to this command, the basis for comparison is the most current profile. In addition, the RIF keyword indicates that only those historical datastore records with elapsed times which exceed the profile’s by 15% should be displayed.

The following command

COMPARE JOB(MGTMN01) PROFNAME(MGTJOBS) -

YDAY RIF(ELAPSED(>10%))

compares the historical datastore records for all jobs with the name MGTMN01 that ran yesterday to the last profile created for MGTMN01 jobs with the profile name MGTJOBS, as shown in the following display.

SUMMARY or SUM

Indicates that all data should be displayed in summary format. That is, the following information will be displayed:n the amount of elapsed or response time by which the workload deviates

from its profilen the workload’s run time, start date, and start timen the profile’s run time, start date, and end date



The following command generates a summary comparison report:

COMPARE JOB(*) -

PNAME -

SUMMARY

Because an asterisk (*) has been substituted for a job name and the PNAME is set to default, the report displays, in descending order, the workloads that deviated most from their profiles. Because no LINECNT is specified, up to twenty workloads are listed.

The following command

COMPARE JOB(*) PROFNAME SUMMARY:

produces the following display.

+======================== Profile/Workload Comparison ========================+ | Job = MGTMN01 Prof Job = MGTMN01 Profname = MGTJOBS | | Prof Period: 00:01 to 12:10 on 10/03/99 Sysid = SYSA | | Wkld Period: 09:29 to 09:30 on 11/05/99 Sysid = SYSA | +-----------------------------------------------------------------------------+ | Times Delta Plot (in Seconds) | |Wait_Reason____________Profile_Workload|16.59___ 8.29_____0_____ 8.29___16.59| |Using CPU 2.48 S 0.26 S | . . . . <-| . . . . | |Waiting for CPU 9.80 S 26.39 S | . . . . |+++++++++++++++> | |Enqueue 0.95 S 11.73 S | . . . . |+++++++++> . . | |I/O Queued 1.19 S 2.93 S | . . . . |> . . . . | |ECB Wait 1.43 S 2.93 S | . . . . |> . . . . | |Swap Page-In Wait 0.23 S n/a | . . . . <| . . . . | |I/O Reserved 0.71 S n/a | . . . . <| . . . . | |SRM Delay (MPL) 1.67 S n/a | . . . . <| . . . . | |Waiting for MVS Lock 2.15 S n/a | . . . . <-| . . . . | |I/O Active 14.34 S n/a | . <------------| . . . . | |Elapsed Time 34.99 S 44.27 S | . . . . |+++++++> . . | |Productivity Index 53% 41% | +=============================================================================+



Related Information: Other EPILOG Reporter Commands: See Reporter Commands in “Command Groupings” on page 19.

COMPEXT or CMXType: EPILOG Reporting Utility Command

Description: Used to export a comparison of the degradation data for a specified workload and time period with that of a workload profile. COMPEXT functions like COMPARE, but the results of the comparison are converted into a format that is compatible with SAS processing and are written out to SAS datasets. Unless preceded by a SETP command directing otherwise, the COMPEXT command selects the most recent profile record for the workload and PROFNAME that you specify.

To export data to SAS, you must submit a batch job or execute a CLIST. Two sample files are included on the product tape to facilitate this process. One file, rhilev.midlev.RKANSAM(KEPPMTSO) contains a sample CLIST to submit a job from the SAS starter kit; the other, rhilev.midlev.RKANSAM(KPMJCL6), contains sample JCL. The SAS starter kit is found in thilev.RKANSAM. Each member of this dataset produces a separate report using the imbedded procedure KEPILGPM. KEPILGPM accepts both EXTRACT and COMPEXT commands.

+======================== Compare Profile Summary ============================+ | Profile Job = ************ Profname = (automatic) | | Job = ************ | | Profile Period: 00:01 on 11/11/99 to 24:00 on 11/11/99 | | Workload Period: 00:02 on 10/03/99 to 15:52 on 11/11/99 | +-----------------------------------------------------------------------------+ | Delta Workload Profile | | Workload Time Run Time Sdate Stime Run Time Sdate Edate | | USER08AA 18:31 M 19:13 M 10/03/89 09:29 42.01 S 11/11/99 11/11/99| | USER12A 11:29 M 12:11 M 10/29/89 08:53 42.09 S 11/11/99 11/11/99| | USER07A 10:47 M 12:35 M 10/28/89 12:39 1:47 M 11/11/99 11/11/99| | USER08AA 9:21 M 10:03 M 10/18/89 11:20 42.01 S 11/11/99 11/11/99| | USER07A 8:31 M 10:18 M 11/07/89 15:33 1:47 M 11/11/99 11/11/99| | USER12A 6:42 M 7:24 M 10/14/89 11:57 42.09 S 11/11/99 11/11/99| | USER07A 6:22 M 8:10 M 10/16/89 10:47 1:47 M 11/11/99 11/11/99| | USER07A 3:43 M 5:31 M 10/30/89 15:36 1:47 M 11/11/99 11/11/99| | USER08AA 3:36 M 4:18 M 10/18/89 10:54 42.01 S 11/11/99 11/11/99| | USER08AA 3:33 M 4:15 M 10/11/89 11:08 42.01 S 11/11/99 11/11/99| | USER08AA 3:11 M 3:53 M 10/11/89 10:58 42.01 S 11/11/99 11/11/99| | USER12A 2:50 M 3:32 M 10/25/89 11:32 42.09 S 11/11/99 11/11/99| | USER12A 2:49 M 3:31 M 10/14/89 12:18 42.09 S 11/11/99 11/11/99| | USER08AA 2:41 M 3:23 M 10/23/89 11:30 42.01 S 11/11/99 11/11/99| | USER08AA 2:40 M 3:22 M 10/08/89 09:19 42.01 S 11/11/99 11/11/99| | USER07A 2:36 M 4:24 M 10/28/89 11:43 1:47 M 11/11/99 11/11/99| | USER08AA 2:33 M 3:15 M 10/10/89 14:31 42.01 S 11/11/99 11/11/99| | USER08AA 2:25 M 3:07 M 11/11/89 13:45 42.01 S 11/11/99 11/11/99| | USER07A 2:10 M 3:57 M 11/04/89 11:08 1:47 M 11/11/99 11/11/99| | USER07A 2:01 M 3:48 M 10/30/89 09:47 1:47 M 11/11/99 11/11/99| +=============================================================================+



COMPEXT {workload} -


[time period] -

[SYSID(cccc,...)] -

[REPORTIF(filter)]

[certain display options]

The only required keywords are a workload identifier and a profile name. A description of the keywords follows.

workload The workload identifier used to select the workloads records you want to extract and compare with a profile. Workload records can be performance groups, batch jobs, started tasks, or TSO user sessions. You can use any of the workload keywords, as listed in Workload Keywords in the “Command Groupings” on page 19, except STEP and INTERVAL.

PROFNAME(cc...cc) or PNAME(cc...cc)

The 1- to 16-character name of the profile with which you want to compare the historical datastore records. Typically, this is the name you assigned to the specified workload when you created its profile with the PROFILE command. If you created the profile with the PROFNAME default, simply specify PNAME without any operand. Note that you cannot use the asterisk as a substitute for a profile name or for any part of a profile name.

time period The date and/or time interval for which you are extracting the specified workload’s historical datastore records. Use any of the date/time keywords as listed in Date and Time Keywords in “Command Groupings” on page 19. If no time period is given, all historical datastore records for the specified workload are selected.

Note that your time period specification applies only to the selection of historical datastore data. Unless you have indicated otherwise on a prior SETP command, the profile selected is the most current profile for the workload, PROFNAME, time period, and SYSID that you have specified on the command.

SYSID(cccc,...) The SMF System ID for the workload you are comparing. Required only when the records in your datastores contain different SYSIDs and you want to extract a workload and profile with a specific SYSID. If you specify multiple SYSIDs, for example (SYSA,SYSB), you will compare each workload-profile combination with a corresponding SYSID that meets your other comparison criteria. If no SYSID is specified, the specified workload and the most recent profile that meet your other comparison criteria will be compared regardless of SYSID. If you want to compare a profile that has a SYSID different from that specified on the COMPEXT command, you may do so by setting the SYSID of the profile with the SETP command.



For example,

COMPEXT PGN(2) -

PNAME(‘TSO DEV’) -

TODAY STIME(0900) ETIME(1700) -

RIF(RESP(>15%))

extracts historical datastore records for performance group 2 for the current day between the hours 9 a.m. to 5 p.m., and the profile named TSO DEV that was created for performance group 2. In addition, the RIF keyword indicates that only those historical datastore records with response times that exceed the profile’s by 15% should be extracted. Assuming that no SETP command was issued prior to this command, the historical datastore records are compared with the most current profile record created for performance group 2 with the name TSO DEV.

The following example,

COMPEXT JOB(*) -

PNAME

compares all batch job workloads with their most recent profiles. Because the PNAME keyword is specified without any operand, the profiles must have been created with the PNAME default (that is, automatic).

The following example extracts data for two MVS systems:

COMPEXT JOB(SORT) -

PNAME(‘NITE BATCH’) -

SYSID(SYSA,SYSB) -

LASTWEEK -

STIME(1700) ETIME(0700)

Because multiple SYSIDs are specified, qualifying workload-profile combinations for either SYSID (SYSA or SYSB) are extracted and compared. Thus, for SYSA and SYSB, this command extracts the historical datastore records for jobs named SORT that ran last week between the hours of 5 P.M. and 7 A.M. It compares them with the most recent profile for the corresponding SYSID, that has the name NITE BATCH and that was created for SORT jobs.

REPORTIF(filter) Specifies the criteria that workload records must satisfy to be extracted. The REPORTIF keyword must be followed by a valid wait reason and appropriate reporting criteria. Use any of the exception-threshold keywords. In addition, you may apply the filter (ELAP(>nn%) or RESP(>nn%)) to indicate that you want to compare only those workload records with an elapsed (ELAP) or response (RESP) time nn% greater than the profile’s. (REPORTIF(filter) may also be expressed as RIF(filter).)

display options COMPLETE, LIMIT, LOGOFF, LOGON, PLOTMIN, TWAITOFF, AND TWAITON. All others are disallowed.



Note:

n The COMPEXT command does not support multiple types of workloads.

n The REPORTIF filter applies only to the historical datastore records for the specified workload and not to the profiles.

n When the PROFNAME is used to display a profile record, the COMBINE and SELECTIF keywords are disallowed (REPORTIF is used to specify exception criteria).

In most instances, the COMPEXT command writes to only one SAS dataset. The exceptions to this occur with the PROGRAM and ACCOUNT keywords. Since these keywords may select batch jobs, started tasks, and TSO user sessions, they may update more than one SAS dataset with a single COMPEXT command.

The SAS datasets for workload keywords on the COMPEXT command are:

n BTCHCOMP for batch job degradation data. JOB, PROGRAM, ACCOUNT, and CLASS write to BTCHCOMP.

n PGNCOMP for performance group degradation data. PGN, PGP, SYMBOLIC, and SYSTEM write to PGNCOMP.

n STCCOMP for started task degradation data. STC, PROGRAM, and ACCOUNT write to STCCOMP.

n TSOCOMP for TSO user session degradation data. TSO, PROGRAM, and ACCOUNT write to TSOCOMP.

Each invocation of the KEPILGPM procedure resets all 16 SAS datasets. If the COMPEXT command does not write any data to a particular dataset, that dataset contains no records after the procedure is executed.

Related Information: Other Reporting Utility Commands: See Reporting Utility Commands in “Command Groupings” on page 19.

COMPLETE or CMPLType: EPILOG Keyword

Description: Generates all display panels when the DISPLAY command is executed. This keyword gives you the ability to scroll up and down through reporter output, but also has some drawbacks with respect to processing time and storage utilization.

By adding the COMPLETE keyword to a DISPLAY command, you generate all display panels when the command is executed. You can then scroll up and down through the panels using the UP and DOWN ISPF commands, or their function key equivalents.

You should keep in mind that the COMPLETE keyword adds considerably to the processing time and storage requirements of the DISPLAY command. We recommend that you do not use COMPLETE with DISPLAY commands that generate more than 20 or 30 panels, depending on the size of the panels.

You can use the LIMIT keyword with COMPLETE to reduce the processing time and storage requirements. For example, if you enter:

DISPLAY PGN(2) LASTWEEK RIF(RESP >2S) COMPLETE LIMIT(10)



only the first ten display panels that meet the exception criteria are generated by the command.



CONTROL COLOR or CNTL COLORType: EPILOG Reporter Command

Description: Allows you to control extended color support. In full-screen mode, EPILOG can use the extended color capabilities of 3279 displays which are so equipped. Extended color support is turned on automatically; if your terminal is not configured to support it, EPILOG will fall back on simple high and low intensity highlighting.

CNTL COLOR allows you to set colors and highlighting attributes for the following types of lines:

Headings and separator lines

Warnings and errors

Data entry lines

Odd display panels

Even display panels

Highlighted areas

Measure lines

Title blocks and graph lines

Note: If you are running the reporter under ISPF, the graph lines default to the same color and highlighting attributes as the rest of the display panel.

The CONTROL COLOR operands are:

Note: Display screen formatting errors may result if you turn extended color mode on (with CONTROL COLOR) while using a non-color terminal. (PROG471 and IKT00405I SCREEN ERASURE CAUSED BY ERROR RECOVERY PROCEDURE are two likely error messages.) If this happens, use the PA1 key to reset EPILOG into non-color mode.

OFF Turns off extended color mode.

None Turns on color mode using the default color and highlighting definitions.

string A 1–8 character string that sets the color areas for 3279 operation and turns color mode on. Each character in the string is a color designation (or a period to indicate no change) for the specific color areas.



The string operand can be used to select a color and a highlighting attribute for each line type. The color selections are standard 3279 colors. The four available highlighting attributes are:

The default color assignments for the eight-character string are shown below.

Control color ‘G R W T Y R B W’

Control hilite ‘. . . . . . . .’

| | | | | | | |

| | | | | | | Title blocks and graph lines

| | | | | | Measure line

| | | | | Highlighted areas

| | | | Even display panels

| | | Odd display panels

| | Data entry line

| Warnings and errors


Colors:

B = Blue G = Green P = Pink

R = Red T = Turquoise W = White

Y = Yellow

Attributes:

B = Blink R = Reverse

U = Underscore D = Default

A period (.) signifies no change

The previous figure shows the display that appears when you enter the CONTROL COLOR command. To change the color of a particular area, type the letter of the color you want the area to be on top of the color letter which points to that area, and press Enter.

B Causes the line type to blink.

U Underscores the line type.

R Reverses the line type. Normally, the display consists of colored characters against a dark background. The REVERSE instruction displays dark characters against a colored background.

D No highlighting (default).



You can also assign certain attributes to an area so that any text that appears in that area blinks, appears in reverse video (dark letters on white background), or is underscored. To change the attributes of an area, type the letter of the attribute you want for the area on top of the period which points to that area.

Control color ‘G R W T Y g B W’

Control hilite ‘. . r . . . . .’

| | | | | | | |

| | | | | | | Title blocks and graph lines

| | | | | | Measure line

| | | | | Highlighted areas

| | | | Even display panels

| | | Odd display panels

| | Data entry line

| Warnings and errors


In this example, highlighted areas are changed to green, and the data entry line appears in reverse video.

Related Information: Other Reporting Format Keywords: See Reporting Format Keywords in “Command Groupings” on page 19.

CONTROL LOG or CNTL LOGType: EPILOG Reporter Command

Description: Logs the current screen to ddname RKM2LOG when you press F9 or F21. These keys are preset to issue the CNTL LOG command.


CONTROL MODE or CNTL MODEType: EPILOG Reporter Command

Description: Provides flexibility in how you format and scroll through displays. The default is PAGE.

CONTROL MODE [ONE|PAGE|ROLL|HOLD]

When EPILOG is used in full-screen mode, the display header includes a Mode field. The settings for the display mode are described below:

ONE The screen shows only one display panel at a time, even though the next one may fit.

PAGE In PAGE mode, the reporter generates as many display panels as will fit on the screen. When you press Enter, the currently displayed panels are discarded, and the next set of panels is displayed. This is the default mode.



You may change the display mode directly using the CONTROL command (abbreviated CNTL) with the mode as an operand (CNTL PAGE, CNTL HOLD, and so on). Alternatively you could use F2 (or F14), which by default are set to issue the CONTROL MODE command. CONTROL MODE advances the display mode through all the possible settings; just keep pressing the function key until it rolls around to the one you want.


CONTROL RECALL or CNTL RECALLType: EPILOG Reporter Command

Description: Saves keystrokes because it allows you to modify and reissue a command rather than type in the next command from scratch.

When a reporter command is executed, the command is normally not included on the output display. You can reshow the command on the command line by pressing F4 or F16. These keys are preset to issue the CONTROL RECALL command. After reshowing the command, you must modify at least one character in the command to reissue it. Thus, if you want to reissue the same command, overtype the first letter of the command and press Enter.

If you enter a command on multiple input lines (using a hyphen as a continuation character), only the first line of the command is displayed.


CONTROL TITLE or CNTL TITLEType: EPILOG Reporter Command

Description: Displays the report title block.

ROLL Each time you press Enter, the topmost panel is discarded and the next panel beneath it rolls to the top of the screen.

HOLD The topmost panel is held on the screen and ROLL mode is invoked for the panels below. Note that in HOLD mode you may only be able to view part of a bottom display panel because the held panel on top is taking up most of the screen. When this is the case, you will be able to scroll to the rest of the non-held panel.



You can add a title block to the display by pressing F5 or F17. These keys are preset to issue the CONTROL TITLE command. A sample title block follows.

The title block gives you a summary of the command. In this example, the input command was:

DISPLAY PGN(2) SDATE(9/19/99) RIF(RESP >2S) -

COMBINE(1H) PLOTMIN(10)

The AVERAGE keyword in the miscellaneous options indicates that average, not total, figures are being displayed. If the COMBINE keyword had not been included in the command, the word SINGLE would have been displayed as a miscellaneous option, indicating that single intervals were being displayed.

You can also obtain a shortened version of the title block by adding the SHORT keyword to the CONTROL TITLE command.


CREATEM or CMATType: EPILOG Reporter Command

Description: Creates a new automatic analysis member in the rhilev.midlev.RKANPARM partitioned dataset.

The Automatic Analysis matrix is a user-definable table which tells EPILOG what resource panels you consider relevant to each type of bottleneck. Each row of the matrix represents a wait reason identified by its 3-character abbreviation (AIO, AUX, COM, and so on). The names of the resource panels (RCHN, RCPU, and so on) associated with each wait reason are shown in the order in which they will be displayed.

CMAT A-matrix-ID wait-reason(resource keyword...) ...

------------------------------------------------------------------------------- | | | Workloads: Performance Group(2) | | Periods: Starting On 9/18/99 and Ending on 9/18/99 | | Report if : Response Time is greater than 2 Seconds | | Misc Options: COMBINE(60M) AVERAGE PLOTMIN(10) | | | ------------------------------------------------------------------------------- +=============================================================================+ | Performance Group = 2 Symbolic Name = DEV TSO | | From 17:00 To 18:00 On 09/18/99 SYSA | | Average of 4 Intervals | +-----------------------------------------------------------------------------+ |Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0| |Using CPU 0.08 S 3.6|-> . . . . . . . . . .| |Long Wait 0.88 S 38.1|------------===>. . . . . . .| |ECB Wait (w/ STIMER) 0.64 S 27.5|----------->. . . . . . . .| |Average Trans Time 2.31 S 5548 MVS Transactions Ended | |Productivity Index 22% | +=============================================================================+



The first operand is a 1- to 7-character A-matrix name and is required. You must also enter one or more detail wait reason codes, each followed by the resource panel names which are to be associated with it. Valid 3-character detail wait reason codes are listed in the EXWAIT entry of this manual. Valid resource keywords are listed under Resource Keywords in “Command Groupings” on page 19.

For example,

CMAT SHIFT1 PAG(RINF RPDS, RPAG)

creates a new A-matrix which will display the RINF, RPDS, and RPAG resource keywords whenever waiting for local page-in (PAG) is the most significant wait reason. The name of the member created in rhilev.midlev.RKANPARM is @SHIFT1.

After you create the A-matrix member with CREATEM, you may use the REPLACEM command to add more lines to the matrix, LISTM to list its contents, or DELETEM to delete it. To invoke this A-matrix member, you must use the AMATRIX keyword.


D Commands and Keywords 83

D Commands and Keywords


D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84DAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84DATASTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84DAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85DAYOFWK or DAY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85DELETEM or DMAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87DET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87DETAIL or DET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87DIS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88DISPLAY or DIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88DMAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90DROP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90DUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90DUPLICATE or DUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

5




DType: EPILOG Navigational Command

Description: Navigates you from the Summary display to the Detail display.

Related Information: Other Fast Path Navigation Commands: J, P, R, S, V, W, and X

DATType: EPILOG Reporter Command

Description: See DATASTOR.


DATASTORType: EPILOG Reporter Command

Description: Dynamically allocates and frees datastores during a reporter session. Changes that you make through the DATASTOR command apply only to the current reporter session because it alters only the active datastore list, not the initial datastore list. The syntax of the DATASTOR command is shown below.

DATASTOR {USE|ADD} EDS(dsname1, dsname2, ...)

or

DATASTOR {DROP} [EDS(n1, n2, ...)] [ALL]

Usage Notes

n Each time you invoke the DATASTOR command, you also invoke INQUIRE SUMMARY, which displays the currently active datastores.

n The DATASTOR USE and ADD commands automatically verify that the newly allocated file is a valid datastore.

ADD Adds one or more datastores to the end of the active datastore list.

DROP Removes one or more datastores from the active datastore list, based on the datastore’s sequence number in the active datastore list as shown by the INQUIRE command. You can use the ALL operand to DROP all datastores from the active list.

USE Defines a list of datastores that supersede the active datastore list. The use operand is similar to the ADD operand, except that the ADD operand adds datatstores to the active datastore list, while the USE operand supersedes the active datastore list with a new list of one or more datastores.



n If you allocate multiple datastores, certain types of requests (such as extensive COMBINE/MERGE operations) may be time consuming to process. A message alerts the user to this condition.


DAYType: EPILOG Keyword

Description: See DAYOFWK.


DAYOFWK or DAYType: EPILOG Keyword

Description: Displays data only for the specified days. The operands used with this keyword can be abbreviated to an unambiguous short form with truncation. For example, WEDNESDAY can be abbreviated to WED or just W, but SATURDAY can only be shortened to SA. (This keyword may not be used when deleting records from the Profile datastore with the EXCLUDE command. For further information on the EXCLUDE command, refer to the OMEGAMON II for MVS Configuration and Customization Guide.)

Operands for DAYOFWK are:

n ALL

n WEEKDAY or WKDAY

n WEEKEND or WKEND

n MONDAY

n TUESDAY

n WEDNESDAY

n THURSDAY

n FRIDAY

n SATURDAY

n SUNDAY

For example,

Display.... SDATE(9/13/99) DAY(MON,THUR) STIME(0900) ETIME(1300) -

BAND

displays data collected on Mondays and Thursdays between the hours of 9:00 AM and 1:00 PM. The Display begins on September 13, 1999 and continues through the present.

Related Information: Keyword of: COMPARE, COMPEXT, DISPLAY, EXTRACT, OBTAIN, PROFILE, SET, and SETP



DELETEM or DMATType: EPILOG Reporter Command

Description: The DELETEM command is used to delete an existing automatic analysis member from the rhilev.midlev.RKANPAR dataset. The only required operand is a 1- to 7-character A-matrix name.

DMAT A-matrix-ID


DETType: EPILOG Keyword

Description: See DETAIL.


DETAIL or DETType: EPILOG Keyword

Description: Displays detailed degradation for a workload. DETAIL is the default. The detail display shows multiple wait reasons for each interval, job, or step. The following display is an example of a detail display for performance group 2, showing multiple wait reasons for each interval:

The scale of the detail display represents the percent of the total degradation attributable to that wait reason, and is always zero through one hundred. The format of the graphic arrow changes if the wait reason exceeds the 30% and 60% marks.



See also SUMMARY.

+=============================================================================+ | Performance Group = 2 Symbolic Name = DEV TSO | | From 03:00 To 03:15 On 08/07/99 Elap = 14:54 M SYSA | +-----------------------------------------------------------------------------+ |Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0| |Using CPU 0.04 S 11.8|----> . . . . . . . . .| |Swap Page-In Wait 0.11 S 29.4|----------->. . . . . . . .| |ECB Wait 0.04 S 11.8|----> . . . . . . . . .| |Waiting For MVS Lock 0.04 S 11.8|----> . . . . . . . . .| |Detected Wait 0.04 S 11.8|----> . . . . . . . . .| |Long Wait 0.02 S 5.9|--> . . . . . . . . . .| |STIMER Wait 0.02 S 5.9|--> . . . . . . . . . .| |ECB Wait (W/ STIMER) 0.02 S 5.9|--> . . . . . . . . . .| |Disk TSO022 320 Act 0.02 S 5.9|--> . . . . . . . . . .| |Average Trans Time 0.37 S 97 MVS Transactions Ended | |Productivity Index 22% | +=============================================================================+



DISType: EPILOG Reporter Command

Description: See DISPLAY.


DISPLAY or DISType: EPILOG Reporter Command

Description: Displays workload degradation, resource utilization, or workload profile information. This is the most frequently used command. The DISPLAY command allows you to report information from the EPILOG and Profile datastores, and can be used to display information online or to generate batch reports.

Display {workload | resource | shared DASD} -

[time period] -

[combining factor] -

[SYSID([MERGE,] cccc, ...)] -

[REPORTIF | SELECTIF (filter1,filter2 ...)] -

[IODEVICE]-

[display options]

The only required keywords for this command syntax are those that specify a workload or resource. However, if you omit the time period, the reporter displays the entire span of data from the EPILOG datastore. This usually results in long Displays that do not focus on useful information.

The keyword types used with the Display command are summarized below:

workload The workload keywords display degradation data by performance group, batch job, started task, or TSO user session. For a list of workload keywords, see Workload Keywords (EPILOG) in “Command Groupings” on page 19.

You can display degradation data in detail or summary format by using the DETAIL and SUMMARY keywords.

The workload utilization keywords (JDAS and PDAS) display shared-DASD usage in a multi-system environment.

resource The resource keywords display information about the types of system resources that are monitored by EPILOG For a list of resource keywords, see Resource Display Keywords in “Command Groupings” on page 19.

time period Since the EPILOG datastore is a historical database, you can select data from any time period that the EPILOG collector was running. The date and time keywords for doing so are listed in Date and Time Keywords in “Command Groupings” on page 19.



A single DISPLAY command often generates more than one display panel. For example, if the RMF interval is set to 15 minutes, the following command generates four panels:

DISPLAY PGN(2) TODAY STIME(9) ETIME(10)

combining factor Typically, resource and performance group collection is synchronized with RMF intervals at your installation. By default, each display panel usually corresponds to an RMF interval. However, this interval is not always a convenient or desirable unit for reporting data; it may provide more detail than is really useful. For reporting purposes, you can combine RMF-based intervals into a more reasonable interval size, such as 1 hour or 1 day.

Batch jobs, started tasks, and TSO user sessions can either be collected at RMF-based intervals, or at termination time (end-of-job, end-of-step, end-of-session, or task termination). The way you combine this data depends on how it was collected. If data was collected at RMF-based intervals, the data is automatically combined unless you specify the INTERVAL keyword. If data was collected at termination time, you can use the COMBINE keyword to combine steps together, or combine together selected job runs, TSO sessions, or started tasks.

SYSID[MERGE] If you are reporting on more than one system, DISPLAY generates one panel per reporting interval for each system. To restrict the data Display to a particular system, include the SYSID(ccc) keyword in the Display, where ccc is the SMF ID of the system data you want to Display. To restrict the data display to several systems, use the format SYSID (aaaa, bbbb, cccc,...), where aaaa is the SMF ID of the first system to be displayed, bbbb is the SMF ID of the second system to be displayed, and so on.

The MERGE keyword allows you to combine DASD device activity from multiple systems into a cross-system, shared-DASD display.

REPORTIF|SELECTIF

These keywords are used to specify workload or (REPORTIF only) resource exception filters. Although the DISPLAY command syntax allows you to use both REPORTIF and SELECTIF in the same command, we recommend that you use either one or the other.

IODEVICE or IODEV

Allows you to override the generic listing of device wait reasons, the default, with a detailed I/O device listing.

When using the IODEVICE keyword, you should keep in mind that, in the profiles of some workloads, a considerable number of devices may be associated with the various wait reasons. Therefore, specifying IODEVICE on a DISPLAY command may produce a rather lengthy report. To limit the display to the most significant wait reasons, use the PLOTMIN keyword.

display options There are a number of display formatting keywords to help you set up your display screen or batch report. Certain formatting keywords apply to workload displays only. These keywords are listed under Workload Display Options Keywords in “Command Groupings” on page 19.

Others allow you to format workload or resource displays, such as the command CONTROL COLOR.



Related Information: Command of: See Date and Time Keywords, Resource Display Keywords, Shared-DASD Degradation Display Keywords, Wait Categories, Summary, Wait Reason Codes, Detail, Workload Display Options Keywords, Workload Exception Filter Keywords, and Workload Keywords in “Command Groupings” on page 19. Other valid keywords include: COMBINE, COMPLETE, FOLDOFF, FOLDON, LIMIT, LOGOFF, LOGON, and SINGLE.

Other Reporter Commands: See Reporter Commands in “Command Groupings” on page 19.

DMATType: EPILOG Reporter Command

Description: See DELETEM.


DROPType: EPILOG Keyword

Description: Removes one or more datastores from the active datastore list, based on the datastore’s sequence number in the active datastore list as shown by the INQUIRE command. You can use the ALL operand to DROP all datastores from the active list.


DUPType: EPILOG Keyword

Description: See DUPLICATE.


DUPLICATE or DUPType: EPILOG Keyword

Description: Specifies the number of separator pages to print. The default is one.

DUPLICATE(n)

The operand for DUPLICATE is a decimal number from 0 to 9.

Related Information: Keyword of: PAGESEP

E Commands and Keywords 91

E Commands and Keywords


EDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92ELAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92ELAPSED or ELAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92ELEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92ELEMENTS or ELEM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92ELT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93END . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93ENDDATE or EDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93ENDTIME or ETIME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94ENQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95ENQUEUE or ENQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95ETIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96EXD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97EXDATE or EXD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97EXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97EXTRACT or EXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98EXW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100EXWAIT or EXW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

6




EDATEType: EPILOG Keyword

Description: See ENDDATE.


ELAPType: EPILOG Operand

Description: See ELAPSED.


ELAPSED or ELAPType: EPILOG Operand

Description: Selects records for batch jobs, started tasks, or TSO user sessions by elapsed time. This operand cannot be entered with a percentage operand on DISPLAY; it requires a specific time, such as 2S, 30M, or 1H. It can, however, be used with a percentage operand on COMPARE, in which case both the profile record and the workload record are used to make the selection.

For example,

display JOB(PAYROLL) STEP RIF(ELAP(>45M)) LASTWEEK

displays only those steps of the PAYROLL jobs last week that ran longer than 45 minutes.

In contrast to the previous example,

display TSO(*) RIF(ELAP(>1H)) LASTWEEK

displays only those TSO sessions that ran longer than 1 hour.

ELAPSED is a valid exception filter for RIF or SIF.

Related Information: Operand of: REPORTIF and SELECTIF

ELEMType: EPILOG Keyword

Description: See ELEMENTS.


ELEMENTS or ELEMType: EPILOG Keyword



Description: Identifies the elements to be selected from the specified reports. Each EPILOG field name is associated with an element name; in addition, there are data fields that are not displayed on EPILOG reports, but which are available for OBTAIN processing.

For a list of all of the valid data elements, see the Data Dictionary appendix to this manual.

ELEMENTS(element1,element2,...)

If ELEMENTS (ELEM for short) is omitted or ELEMENTS(*) is specified, all elements for the named reports are selected.

Field names specified by ELEM on an OBTAIN command are extracted only for that command. Field names specified by ELEM on one or more SET commands are cumulative. They will be extracted on all subsequent OBTAIN commands for reports that contain them. SET ELEM(*) or SET ELEM() clears previous elements activated by SET commands.


ELTType: EPILOG Keyword

Description: See ELAPSED.


ENDType: EPILOG Reporter Command

Description: To exit the reporter, you can enter the END command on the command line at any time. STOP and QUIT are aliases for END. This command has no keywords. When you enter END on the command line, you will return to the Primary Option Menu:

Enter X on the OPTION line to complete reporter termination.


ENDDATE or EDATEType: EPILOG Keyword

Description: Specifies the end date of the display. If no ENDDATE is specified, data is selected up to the most recent record in the database. Dates can be entered in either of two formats:

------------------------- CANDLE PRIMARY OPTION MENU -------------------------OPTION ===> 0 PARMS - Change user session parms1 COMMAND - Begin COMMAND driven sessionX EXIT - Return to ISPF



n Julian

n Gregorian

Note: If slashes are used with Gregorian dates, leading zeros are not required (for example, 7/2/99 is an acceptable date entry). If slashes are not used, leading zeros are required.

See the STARTDATE entry for a discussion of how to specify relative dates and times.



ENDTIME or ETIMEType: EPILOG Keyword

Description: Specifies the end time of the display. Defaults to 23:59:59 on the specified ENDDATE. (If no ENDDATE is specified, data is selected up to the most recent record in the database.) Times must be entered in 24-hour format (that is, 1300 instead of 1:00 PM), and can be abbreviated as follows:

See the STARTTIME entry for a discussion of how to specify relative dates and times.



yyddd (ddd = 001 through 366)

mmddyy

mm/dd/yy

mm/dd (assume the current year)

dd (assume the current month and year)

h One-digit hour without a leading zero

hh Two-digit hour

hmm or h:mm Hours and minutes without a leading zero

hhmm or hh:mm Hours and minutes

hhmmss or hh:mm:ss

Hours, minutes, and seconds



ENQType: EPILOG Detail Wait Reason Code

Description: See ENQUEUE.


ENQUEUE or ENQType: EPILOG Detail Wait Reason Code

Description: Used in exception analysis to exclude or select delays due to waiting for an enqueue. The valid device and enqueue operands are:




Exception applies only to the specified DASD device (cuu = the device address in MVS/370; nnnn = the device number in MVS/XA and above). (This option is allowed with the NO prefix; the NODASD exception applies if no DASD waits were seen.)


Exception applies only to the specified DASD device. (This option permits the NO prefix; the NODISK exception applies only if no DASD waits were seen.)



Exception applies only to the specified tape device. (This option is allowed with the NO prefix; the NOTAPE exception applies only if no tape waits were seen.)


Exception applies only to the specified disk or tape device. (This option is allowed with the NO prefix; the NOUNIT exception applies only if no disk or tape waits were seen.)







For example,

DISPLAY TSO(*) SIF(ENQ(ANY >1S)) INTERVAL TODAY

displays all intervals in which any TSO user session waited for an enqueue more than 1 second.


ETIMEType: EPILOG Keyword

Description: See ENDTIME.


















EXDType: EPILOG Keyword

Description: See EXDATE.


EXDATE or EXDType: EPILOG Keyword

Description: Excludes the specified date(s) from the display. Dates can be entered in either of two formats:

n Julian

n Gregorian


For example,

display... DAY(WKDAY) SDATE(7/1/99) STIME(0900) -

EDATE(7/10/99) ETIME(1700) EXDATE(7/4/99) BAND

displays data collected on weekdays from 9:00 AM - 5:00 PM starting July 1, 1999 until July 10, 1999. Data from July 4 is excluded from the display.

Related Information: Keyword of: DISPLAY, EXTRACT, OBTAIN, PROFILE, and SET


EXTType: EPILOG Reporting Utility Command

Description: See EXTRACT.



mmddyy

mm/dd/yy

mm/dd (assume the current year)

dd (assume the current month and year)



EXTRACT or EXTType: EPILOG Command

Description: Used to export data from the historical datastores and converts it into a format that is compatible with SAS processing.

To export data to SAS, you must submit a batch job or execute a CLIST. Two sample files are included on the product tape to facilitate this process. One file rhilev.midlev.RKANCLI(KEPPMTSO) contains a sample CLIST to submit a job from the SAS starter kit; the other, rhilev.midlev.RKANSAM(KPMJCL6), contains sample JCL. The SAS starter kit is found in thilev.RKANSAM. Each member of this dataset produces a separate report using the imbedded procedure KEPILGPM. KEPILGM accepts both EXTRACT and COMPEXT commands.

EXTRACT {workload | resource} -

[time period]-

[combining factor]-

[SYSID(cccc, ...)]-

[REPORTIF (filter) | SELECTIF (filter)]

The only required keywords are those that specify a workload or resource. However, you will generally want to include a time period in the command. If you omit the time period, data will be extracted from the time when collection first began to the time when the last interval was collected. This usually results in large output datasets that do not focus on useful information.

The keyword types used with the EXTRACT command are:

workload The workload keywords extract degradation data for a performance group, batch job, started task, or TSO user session. These keywords are listed in Workload Keywords in “Command Groupings” on page 19.

resource The resource keywords extract information about any of the types of system resources that are monitored by EPILOG. These keywords are listed in Resource Display Keywords in “Command Groupings” on page 19.

time period Since the historical datastores is a historical database, you can select data from any time period that the EPILOG collector was running. The date/time keywords are listed in Date and Time Keywords in “Command Groupings” on page 19.



For example, if you specify

EXTRACT RCHN LASTMONTH

in the KEPILGPM procedure, the SAS interface will extract information about channel resources, and write that information out to the SAS dataset called RCHN.

In most instances, the EXTRACT command writes to only one SAS dataset. For example if you specify

EXTRACT PGN LASTMONTH

in the KEPILGPM procedure, the SAS interface will extract information about performance groups, and write that information out to the PGNDETL dataset.

The exceptions to this occur with the PROGRAM and ACCOUNT keywords. Since these keywords may select batch jobs, started tasks, and TSO user sessions, they may update more than one SAS dataset with a single EXTRACT command.

The SAS datasets for workload keywords on the EXTRACT command are:

n BTCHDETL for batch job degradation data. JOB, PROGRAM, ACCOUNT, and CLASS write to BTCHDETL.

combining factor Typically, resource and performance group collection is synchronized with RMF intervals at your installation. Thus, by default, each record usually corresponds to an RMF interval. However, this interval is not always a convenient or desirable unit for reporting data; it may provide more detail than is really useful. For reporting purposes, you can combine RMF-based intervals into a more reasonable interval size, such as one hour or one day.

Batch jobs, started tasks, and TSO user sessions can either be collected at RMF-based intervals, or at termination time (end-of-job, end-of-step, end-of-session, or task termination). The way you combine this data depends on how it was collected. If data was collected at RMF-based intervals, the data is automatically combined unless you specify the INTERVAL keyword. If data was collected at termination time, you can used the COMBINE keyword to combine steps together, or combine selected job runs, TSO sessions, or started tasks together.

See “COMBINE or CMB” on page 66.

SYSID If you run more than one system on the same hardware, you can report on each system individually or on both systems together. To restrict the data display to a particular system, include the SYSID(cccc) keyword in the EXTRACT command, where cccc = the SMF ID of the system data you want to extract.

exception filters There are times when you are only interested in those time periods when certain criteria were met. For example, you might only want to display degradation data for those periods when TSO response time was greater than two seconds. Exception filters allow you to select periods using such criteria as response time, elapsed time, or a particular wait reason.

To set exception filters, refer to “REPORTIF or RIF” on page 168 or “SELECTIF or SIF” on page 187.



n PGNDETL for performance group degradation data. PGN, SYMBOLIC, and SYSTEM write to PGNDETL.

n STCDETL for started task degradation data. STC, PROGRAM, and ACCOUNT write to STCDETL.

n TSODETL for TSO user session degradation data. TSO, PROGRAM, and ACCOUNT write to TSODETL.

Each invocation of the KEPILGPM procedure resets the 16 SAS datasets. If the EXTRACT command in the procedure does not write any data to a particular dataset, that dataset contains no records after the procedure is executed.


EXWType: EPILOG Keyword

Description: See EXWAIT.


EXWAIT or EXWType: EPILOG Keyword

Description: Excludes one or more wait reasons from a degradation display.

EXWAIT (reason1, reason2, ...)

The list of valid detail wait reason codes appears at the end of this discussion.

You can exclude one or more detail wait reasons from a degradation display with the EXWAIT keyword. This is often desirable when one wait reason dominates the display. For example, when displaying a CICS™ performance group, you will sometimes find very large ECB waits with STIMER:

(Notice that since no CICS address space terminated during this interval, there are no average transaction time figures, nor does the display show any values in the Time field.)

Since this wait reason does not really represent degradation, you may want to exclude it from the display. To do so, include the EXWAIT(cccccccccc) keyword in the command, where

+=============================================================================+| Performance Group = 6 Symbolic Name = CICSP || From 14:00 to 14:15 on 03/29/99 Elap = 14:44 M SYSA |+-----------------------------------------------------------------------------+|Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0||Using CPU 4.7|-> . . . . . . . . . .||ECB Wait (w/ STIMER) 56.5|------------==========> . . . . .||Disk SYSA21 D87 Act 14.2|-----> . . . . . . . . .||Waiting For CPU 6.3|--> . . . . . . . . . .||Productivity Index 22% |+=============================================================================+



cccccccccc = a detail wait reason. (See the list at the end of this entry for valid detail wait reason codes and their short names.)

For example, to exclude ECB waits from the previous display, enter:

DISPLAY PGN(6) EXWAIT(ECBSTIMER)

or, using the short form of the detail wait reason code, enter:

DISPLAY PGN(6) EXWAIT(ECS)

All detail wait reason codes have short forms that are 3 characters in length.

The resulting display looks like this:

The ECBSTIMER waits have been ignored and the remaining wait reason percentages have been normalized to 100 percent. Note that when EXWAIT is used, the Time field is suppressed. By excluding segments of the transaction with EXWAIT and normalizing the percentages, we have made the percentages irrelevant to the total time. Also, because a major wait was excluded, new wait reasons may appear on the display because the percentages were normalized and their new values exceed the PLOTMIN threshold.

The productivity index is recalculated with the normalized values for each remaining wait reason.

Detail Wait Reason Codes Valid with EXWAIT

n ACTIVEIO (or AIO). Delay due to an active I/O in progress. ACTIVEIO has a separate entry in this manual which describes its operands.

n APPCWAIT (or APS). Delay due to voluntary swap-out of an idle APPC address space.

n AUXSTOR (or AUX). Delay due to swaps caused by a shortage of auxiliary space. Auxiliary space shortage is due to a high allocation of local page slots.

n BACKUP (or BKP). Delay due to waiting for HSM to execute a dataset backup request.

n CANCEL (or CAN). Delay due to a job cancel request issued to JES.

n CENTSTOR (or CSS). Delay caused by swap-out to improve central storage availability.

n CILOCATE (or CIL). Delay due to waiting for HSM to execute a locate request for a converter/interpreter.

n COMMON (or COM). Delay due to address spaces waiting for a PLPA or common page-in.

+=============================================================================+| Performance Group = 6 Symbolic Name = CICSP || From 14:00 to 14:15 on 03/29/99 Elap = 14:44 M SYSA |+-----------------------------------------------------------------------------+|Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0||Using CPU 10.5|----> . . . . . . . . .||Disk SYSA21 D87 Act 32.7|------------=> . . . . . . .||Waiting for CPU 14.6|-----> . . . . . . . . .||ECB Wait 7.7|--->. . . . . . . . . .||Swap Page-In Wait 5.6|--> . . . . . . . . . .||Productivity Index 45% |+=============================================================================+



n CPUTIL (or CPU). Time spent using CPU.

n CPUWAIT (or CPW). Delay due to address spaces waiting on the active CPU dispatching queue. High percentages here may mean that the address space is low priority or that there is a shortage of CPU cycles.

n DELETEDS (or DLD). Delay due to waiting for HSM to delete a dataset.

n DELETEJOB (or DEL). Delay due to a job delete request issued to JES.

n DETECTED (or DET). Delay due to swaps caused by a detected wait. A detected wait swap occurs when a user address space has not executed in more than 8 SRM seconds or 2 seconds, whichever is less (in current versions of MVS), and has not issued a long WAIT command.

n DISKMOUNT (or DMP). Delay due to address spaces waiting for an operator to mount a disk.

n ECBSTIMER (or ECS). Delay due to ECB waits with an STIMER TASK or REAL pending (see ECBWAIT below).

n ECBWAIT (or ECB). The address space has issued a voluntary wait for some reason. Examples are an IMS message region waiting for work, a CICS region waiting for work, or even OMEGAMON® for MVS waiting between screen refreshes. High percentages of ECB waits may indicate a program error, normal voluntary waits, or, if the Candle Subsystem is not running, a system I/O reconfiguration.

n ENQEXC (or EEX). Delay due to swaps performed to make room for users that are enqueued on a resource required by other users.

n ENQUEUE (or ENQ). Delay due to waiting for an enqueue. ENQUEUE has a separate entry in this manual which describes its operands.

n EXCHANGE (or EXG). Delay due to exchange swaps. Exchange swaps are performed when one user in a given domain must be swapped out to make room for another user in the same domain that has a higher recommendation value.

n HLIST (or HLS). Delay due to waiting for HSM to execute an HLIST command.

n HSPCPGIN (or HSP). A hiperspace page delay.

n JOBSTATUS (or JST). Delay due to a job status request issued to JES that has been queued.

n LONGWAIT (or LON). Delay due to swaps caused by user-requested long waits.

n MIGRATE (or MIG). Delay due to waiting for HSM to migrate a dataset.

n MVSLOCK (or LCK). Delay due to address spaces waiting to acquire a local or global MVS lock.

n OPENMVS1 (or OM1). Delay due to an Open MVS Swap1.

n OPENMVS2 (or OM2). Delay due to an Open MVS Swap2.

n OUTLONG (or OLS). Delay caused by swap-out to enable the swap-in of an address space that had been swapped out too long.

n PAGEIN (or PAG). Delay due to address spaces waiting for a private page-in operation.



n QUEUEDIO (or QIO). Delay due to waiting for queued I/O. QUEUEDIO has a separate entry in this manual which describes its operands.

n READCTL (or RCR). Delay due to waiting for HSM to read a control dataset record.

n READY (or RDY). SRM Delay (MPL); this can occur when a domain is at the maximum MPL and a unilateral or exchange swap must occur to get the ready work swapped in. The READY delay occurs while waiting for SRM to allow the swap. When the ASM has scheduled a swap-in, any subsequent delay will then show up in the Swap Page-In (SWAPIN) category.

n REALSTOR (or RST). Delay due to swaps caused by a shortage of real pageable frames.

n RECALL (or RCL). Delay due to waiting for HSM to recall a dataset.

n RECOVER (or RCV). Delay due to waiting for HSM to recover a backup dataset.

n REQUEST (or REQ). Delay due to requested swaps.

n REQUEUE (or RQU). Delay due to a job requeue request to JES.

n RESGCAP (or RSG). Delay due to a resource group.

n SRMRTO (or RTO). Delay imposed by SRM to meet the response time objective set in the IPS.

n STAGING (or MSS). Waiting for a mass storage volume to be staged.

n STIMER (or STI). The address space has issued an STIMER and is voluntarily waiting for it to end. This is typically not considered degradation since it is a voluntary wait.

n SWAPIN (or SWI). The address space has been given to the ASM queue and is waiting for MVS to swap it into storage. A high value for this wait can be caused by I/O problems such as a slow I/O device or DASD contention.

n SYSOUT (or PSO). Delay due to a process SYSOUT request issued to JES that has been queued.

n SYSPAGE (or SPS). Delay caused by swap-out to reduce the system page fault rate.

n TAPEMOUNT (or TMP). Delay due to tape mounts. The percentage indicated in the degradation data reflects the percentage of time in which the tape mount pending condition was in effect. Note that this may not always represent degradation.

For example, an application may issue a tape mount request some time before it actually requires I/O to the data on that tape. (This is often the case with such applications as CICS, which can perform asynchronous I/O.) Under these conditions, the job continues running while the tape mount pending condition is in effect, with no degradation to that job.

Remember also that the tape mount pending condition is in effect from the time that the tape mount request is issued to the operator console to the time that the tape is actually mounted and the tape drive is made READY. For those installations that use them, this time may actually be spent waiting for a tape management system, not a system operator.



n TERMIN (or TIN). Delay due to swaps caused by waiting for terminal input.

n TERMOUT (or TOU). Delay due to swaps caused by a TSO session that is waiting for an output buffer or waiting for the user to press Enter after “***” is displayed in line output mode.

n TRANSWAP (or TSW). Delay due to swap-outs that occur because an address space was made non-swappable. (When an address space is made non-swappable, it has to be swapped out and then swapped back in with non-swappable status.)

n UNILATERAL (or UNI). Delay due to swaps that occur because the MPL for a domain exceeded the target MPL.

n VIOPAGIN (or VIO). A VIO page delay.

n WTORWAIT (or WTO). Delay due to a long or detected wait swap with WTOR pending.

n XMEMPGIN (or XME). A cross memory page delay.



F Commands and Keywords 105

F Commands and Keywords

Chapter ContentsCommands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

FOLDOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106FOLDON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

7




FOLDOFType: EPILOG Keyword

Description: Causes output to be written in upper and lower case characters, both on the screen and in the log file. This is the default. There are no operands.

Related Information: Keyword of: CONTROL, DISPLAY, EXTRACT, and OBTAIN


See FOLDON.

FOLDONType: EPILOG Keyword

Description: Used to fold output to the terminal and to the log file. Output is written entirely in uppercase characters. There are no operands.

Related Information: Keyword of: CONTROL, DISPLAY, EXTRACT, and OBTAIN


See FOLDOFF.

FORMATType: EPILOG Keyword

Description: FORMAT specifies the format of the data to be written to the output file. Three options are available for the FORMAT keyword: INT, COL, and PC. INT is the default format.

FORMAT(format)

INT writes binary data. The INT option is advisable if you will be writing your own programs to read the OBTAIN output file.

COL writes printable EBCDIC data arranged in columns. The COL option is advisable if the output file will be used as input to a mainframe graphics or statistics package, such as GDDM/ICU™, or if the output file will be downloaded and used as input to a PC software package such as Lotus® 1-2-3®. Your installation’s download utility will handle the EBCDIC-to-ASCII conversion.

PC writes printable EBCDIC data arranged in columns. The PC format is the same as the COL format, except that data elements in the COL format are arranged in columns, and data elements in the PC format are delimited with double-quotation marks (for character strings) and blanks (for numbers). Use the format that is best suited for the software application you will be using to process the exported data.

F Commands and Keywords 107


See the OBTAIN command for complete information about output file contents, record types, and record structures for each data format.


G-H Commands and Keywords 109

G-H Commands and Keywords


HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

8




HELPType: EPILOG Reporter Command

Description: Invokes the online help facility. Online help is available for all EPILOG commands and topics. When you enter HELP or H without any operands, you will get a list of valid commands and topic names. When you enter HELP commandname or HELP topic, the requested HELP information will be displayed.

You can enter the HELP command at any time, even while you have the output of a DISPLAY command on the screen. When you are finished with the help facility, press Enter to return to the interrupted display.

You can also request help by entering the command or topic name on the input line and pressing F1 or F13 instead of Enter. This activates the specified help facility.

EPILOG comes with an online help PDS which must be allocated to ddname EPHELP. (The sample CLIST distributed with the product takes care of this for you.)


I Commands and Keywords 111

I Commands and Keywords


INQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112INQUIRE or INQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112INT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113INTERVAL or INT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113IODEV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114IODEVICE or IODEV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

9




INQType: EPILOG Reporter Command

Description: See INQUIRE.


INQUIRE or INQType: EPILOG Reporter Command

Description: This command lets you make online inquiries about the status of your EPILOG and Profile datastores.

INQUIRE [workload [PROFNAME]] -

[resource] -

[SUMMARY]

[SYSID(cccc,...)] -

[EDS | PRDS]

If you enter the INQUIRE command without a keyword, the reporter displays VSAM file characteristics about the EPILOG and Profile datastores.

workload If you include a workload name, the display shows how much space is being taken up by records of that type in the indicated datastore.

For a list of valid workload or resource keywords, see Workload Keywords or Resource Display Keywords in “Command Groupings” on page 19.

Note: When making inquiries against the Profile datastore, do not specify multiple criteria for batch workloads (for example, JOB(*) CLASS(A)).

resource The resource keywords display information about the types of system resources that are monitored by EPILOG For a list of resource keywords, see Resource Display Keywords in “Command Groupings” on page 19.

PROFNAME If you enter a workload and a profile name, the display shows how much space in the Profile datastore is being used by profile records of that type.

SUMMARY Displays a summary status report for all datastores defined in the current reporter session.

SYSID(cccc,...) Specifies an SMF system ID for the datastore.

EDS Specifies an EPILOG datastore. This is the workload default in the absence of the PROFNAME keyword.

PRDS Specifies an Profile datastore.

I Commands and Keywords 113


Related Information: Command of: Workload Keywords and Resource Keywords in “Command Groupings” on page 19.

INTType: EPILOG Keyword

Description: See INTERVAL.


INTERVAL or INTType: EPILOG Keyword

Description: Specifies that the data should be displayed at RMF-based intervals. (That is, a separate display panel is generated for each interval of data.) There are no operands.

The default, if you have been collecting data by intervals, is to display degradation data at the level of the job, started task, or TSO user session; a single display panel is generated for each batch job, started task, or TSO user session meeting the selection criteria that was running during the time period specified on the command. If RMF is not active on your system, the reporter uses the collection interval during the customization of OMEGAMON II for MVS.

INTERVAL and COMBINE are mutually exclusive.

For example,

DISPLAY JOB(PRINT01) YDAY STIME(8) ETIME(13) INTERVAL

generates the following typical interval display.

Important

You cannot use the INTERVAL keyword unless you have been collecting data at the interval level. See the discussion of collector options in the OMEGAMON II for MVS Configuration and Customization Guide.



Related Information: Keyword of: DISPLAY, EXTRACT, INQUIRE, OBTAIN, PROFILE, and SETP


IODEVType: EPILOG Keyword

Description: See IODEVICE.


IODEVICE or IODEVType: EPILOG Keyword

Description: Displays the unit addresses or volsers for the I/O devices under their associated wait reasons. In some workload profiles, many I/O devices may be associated with the various wait reasons. Therefore, specifying IODEVICE may produce a rather lengthy report. To limit the display to the most significant wait reasons, we recommend that you use the LINECNT keyword in the COMPARE command and the PLOTMIN keyword in the DISPLAY command.

Related Information: Keyword of: COMPARE, COMPEXT, DISPLAY, EXTRACT, and OBTAIN

+=============================================================================+ | Job = PRINT01 JES Number = 3147 Program = RATECALC | | Job Class = T Acct No = 41277 BATCHINT = 2 | | Step = S14X Procstep = CALCULAT Step Number = 2 | | From 08:00 To 08:30 On 08/01/99 Elap = 30:24 M SYSA | +-----------------------------------------------------------------------------+ |Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0| |Using CPU 8:26 M 27.6|----------> . . . . . . . .| |Waiting For CPU 4:58 M 16.3|------> . . . . . . . . .| |Tape 521 Act 4:04 M 13.4|-----> . . . . . . . . .| |Control Unit 52X Que 3:46 M 12.4|----> . . . . . . . . .| |Tape 001724 522 Act 2:36 M 8.6|--->. . . . . . . . . .| |Tape Mount Pending 2:28 M 8.1|--->. . . . . . . . . .| |Disk BLNG28 156 Act 1:53 M 6.2|--> . . . . . . . . . .| |Job Elapsed Time 30:24 M | |Productivity Index 60% | +=============================================================================+

J Commands and Keywords 115

J Commands and Keywords

Chapter ContentsJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116JDAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116JOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117JOBNAME or JOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

10


JType: EPILOG Navigational Command

Description: Navigates you from the DASD Resource or the Workload Degradation display to the Shared-DASD Degradation (by Workload) display in a multi-system configuration.

Related Information: Other Fast Path Navigation Commands: D, P, R, S, V, W, and X

JDASType: EPILOG Keyword

Description: Displays shared-DASD usage by workload, including jobs, started tasks, and TSO users in a multiple system configuration. Use the following syntax for the JDAS keyword.

Display {JDAS(volser)} -

[time period]

For example,

DISPLAY JDAS(COM002) YDAY STIME(14:15) ETIME(14:30)

generates displays similar to the following sample report.

The Shared-DASD Degradation Display shows cross-system usage by workload of the specified DASD device.

In the sample display, the Active I/O and Queued I/O status percentages each add up to 100%. You can see both the heavily active and the heavily inactive workloads accessing the Volume on a comparative basis.

Volser Volume to be analyzed. This operand is 6 characters long.

time period Time period to be analyzed, using the date and time keywords listed in Date and Time Keywords in “Command Groupings” on page 19.

+==============================================================================+ | Volume = COM002 Period = 02:15 to 02:30 on 02/16/99 | +------------------------------------------------------------------------------+ | Relative Usage of selected DASD device for Cross-system ACTIVE I-O | +------------------------------------------------------------------------------+ | Workload_JES #_Sysid_Time_______%__|0___1___2___3___4___5___6___7___8___9___0| | ASMPBKUP J4661 SYSA 5:32 M 82.1 |------------============>>>>>>>>>> . .| | $AOASMP2 S4533 SYSF 45:98 S 11.4 |-----> . . . . . . . . .| | TDNY30 T4014 SYSA 26:22 S 6.5 |--> . . . . . . . . . .| +------------------------------------------------------------------------------+ | Relative Usage of selected DASD device for Cross-system QUEUED I-O | +------------------------------------------------------------------------------+ | Workload_JES #_Sysid_Time_______%__|0___1___2___3___4___5___6___7___8___9___0| | $AOASMP1 S4243 SYSF 29:64 S 66.7 |------------============>>> . . . .| | ASMPBKUP J8812 SYSA 13:94 S 31.4 |------------==> . . . . . . .| | $AOASMP2 S4533 SYSF :84 S 1.9 |> . . . . . . . . . .| +==============================================================================+

J Commands and Keywords 117

Related Information: Keyword of: DISPLAY, EXTRACT, and OBTAIN :p.Other Shared-DASD Degradation Display Keyword: PDAS

JOBType: EPILOG Keyword

Description: See JOBNAME.


JOBNAME or JOBType: EPILOG Keyword

Description: Selects batch job degradation data by job name. The job name can be further qualified by JES job number. The operand for this keyword is 1–8 characters long. This keyword accepts a wildcard (*) character. For example,

Display JOB(PRINT01) YESTERDAY

Displays degradation data for job PRINT01 yesterday. A separate display panel is generated for each run of the job. If the job consists of multiple steps, all steps are combined into a single display panel. The following example shows how to qualify the job name using the JES job number.

Display JOB(PRINT01(J2544))

This command displays a single display panel for the run of job PRINT01 with JES job number 2544. Notice that the job number follows the job name and is prefixed with a J.








K-L Commands and Keywords 119

K-L Commands and Keywords

Chapter ContentsCommands and Keywords

LASTMONTH or LMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120LASTWEEK or LWK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120LASTYEAR or LYR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120LCNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120LIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120LIMIT or LIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121LINECNT or LCNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121LISTM or LMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121LMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122LMN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122LOGOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122LOGON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122LWK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123LYR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

11




LASTMONTH or LMNType: EPILOG Keyword

Description: Displays data from the first day to the last day of the previous month.



LASTWEEK or LWKType: EPILOG Keyword

Description: Displays data from Monday to Sunday of the previous week.



LASTYEAR or LYRType: EPILOG Keyword

Description: Displays data from the first day to the last day of the previous year. LASTYEAR covers long time periods and therefore may take a long time to process when used with the DISPLAY command.



LCNTType: EPILOG Keyword

Description: See LINECNT.


LIMType: EPILOG Keyword

Description: See LIMIT.




LIMIT or LIMType: EPILOG Keyword

Description: Sets the limit for the number of display panels in the command output. The operand for this keyword is 0 to 32767. (An operand of 0 specifies that no limit should be placed on command output. In batch mode, the default is 10. In online mode, the only limit to the number of display panels that can be generated by a single DISPLAY command is the amount of storage available.)

One of the reporter functions that is especially useful in batch mode is the LIMIT keyword. When used with the DISPLAY command, the LIMIT keyword determines the maximum number of panels in the output report for a given DISPLAY command. For example, if you enter:

DISPLAY PGN(2) SIF(RESP >2S) LASTWEEK LIMIT(20)

you may not know beforehand how many intervals will meet the SIF exception criteria. However, because the LIMIT keyword is set to 20, up to twenty intervals (the first twenty intervals) will be included in the output. The default for this keyword puts a very tight safety net on commands that have the potential to produce voluminous unwanted output. If you want to see more than 10 display panels in your batch mode output, you must use the LIMIT keyword to override the default.

Related Information: Keyword of: COMPARE, COMPEXT, DISPLAY, EXTRACT, OBTAIN, and SET


LINECNT or LCNTType: EPILOG Keyword

Description: Specifies the maximum number of wait-reason lines that you want to display.

LINECNT(nnnnn)

When specified together with SUMMARY, LINECNT (or LCNT(nnnnn)) limits the number of records to be displayed. You may specify any number from 0 to 32767. The default is LINECNT(20). Note that Using CPU and the averaged response- or elapsed-time lines will always be displayed and are not counted as wait reasons.

Related Information: Keyword of: COMPARE

LISTM or LMATType: EPILOG Reporter Command

Description: The LISTM command lists an existing automatic rhilev.midlev.RKANPAR analysis member from the dataset. The only operand is a 1- to 7-character A-matrix name.

LMAT A-matrix-ID




LMATType: EPILOG Reporter Command

Description: See LISTM.


LMNType: EPILOG Keyword

Description: See LASTMONTH.


LOGOFFType: EPILOG Keyword

Description: Turns off logging to the log file defined by the ddname RKM2LOG. (This is the default.) If you issue SET LOGON and later want to display information that you do not want logged, include the LOGOFF keyword in the DISPLAY command. This keyword suppresses logging for that particular use of the DISPLAY command, but leaves the default logging intact.

Related Information: Keyword of: DISPLAY, EXTRACT, INQUIRE, OBTAIN, and SET


See also LOGON.

LOGONType: EPILOG Keyword

Description: The LOGON keyword writes out reporter displays to a log file. This file is defined by the ddname RKM2LOG, and is automatically allocated to SYSOUT=A by the sample CLIST used to invoke the reporter.

When a display is logged, all display panels generated by the command are written out, not just those currently displayed on the screen. Also, a title block that describes the command is included with the logged display. You can log displays in three ways:

n You can log the output of a single command by entering LOGON as a keyword with the command.

n You can turn on default screen logging by entering the SET LOGON command. All reporter output generated after this command is automatically logged. If you then want to display information that you do not want logged, include the LOGOFF keyword in the DISPLAY command. This keyword suppresses logging for that particular use of the DISPLAY command, but leaves the default logging intact.

n You can log a display that is already on the screen by pressing F9 or F21. These keys are preset to issue the CNTL LOG command.



If your printer does not have lowercase characters, use the FOLDON keyword to log your displays in uppercase characters only.

Related Information: Keyword of: DISPLAY, EXTRACT, INQUIRE, OBTAIN, and SET


See also LOGOFF.

LWKType: EPILOG Keyword

Description: See LASTWEEK.


LYRType: EPILOG Keyword

Description: See LASTYEAR.


M Commands and Keywords 125

M Commands and Keywords


Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126MAXSCALE or MAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126MERGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

12




MAXType: EPILOG Keyword

Description: See MAXSCALE.


MAXSCALE or MAXType: EPILOG Keyword

Description: Sets the scale for the graphic section of the summary degradation display.

MAXSCALE(time)

The operand for MAXSCALE is a time in seconds, minutes, or hours (for example, 1S, 30M, or 1H). For example, if one interval on a display has a much larger wait reason than other intervals, the scale of the display is automatically set to show that interval. This setting, however, may make the other intervals difficult to read. For example, consider the following summary display.

Three intervals are much longer than the rest, and have extended the graphic section of the display. As a result, the resolution of the other intervals on the scale is poor, and it is difficult to evaluate them accurately. If we issue the following command, the maximum scale is set to one second:

DISPLAY PGN(2) SDATE(6/22) EDATE(6/22) SUM MAXSCALE(1S)

The resulting display is :

+=============================================================================+ | Performance Group = 2 Symbolic Name = DEV TSO | | From 18:02 To 24:00 On 06/02/99 SYSA | +-----------------------------------------------------------------------------+ |DATE__START_END___MAIN_REASON(*)_TIME(-)|0S_____1______2______3______4______5| |06/02 18:02 18:15 Using CPU 0.62 S|*--> . . . . .| | 18:15 18:30 Swap Page-In 0.50 S|*--> . . . . .| | 20:06 20:15 Using CPU 0.50 S|*--> . . . . .| | 21:30 21:45 Da 146 SPOOL1 0.56 S|*--> . . . . .| | 21:45 22:00 Swap Page-In 0.07 S|> . . . . .| | 22:00 22:15 Swap Page-In 0.46 S|--> . . . . .| | 22:15 22:30 Long Wait Swp 3.28 S|************----------> . .| | 22:30 22:45 Long Wait Swp 3.38 S|*****************------> . .| | 22:45 23:00 Detected Wait 0.51 S|*--> . . . . .| | 23:00 23:15 Using CPU 1.01 S|*----->. . . . .| | 23:15 23:30 Long Wait Swp 0.83 S|***--> . . . . .| | 23:30 23:45 Long Wait Swp 2.75 S|***************---> . . .| | 23:45 24:00 Long Wait Swp 0.48 S|*-> . . . . .| |---------------------------------------- | |Average For This Workload Display 1.15 S | |Productivity Index 22% | +=============================================================================+

M Commands and Keywords 127


By reducing the scale, the resolution of the other intervals on the display is much greater. Notice how the arrows for the four intervals that now extend beyond the graph end with a plus sign.

By default, the scale range is based on the highest interval in the display. The units of the display are set to seconds, minutes, or hours, and the range of the display is set by rounding up to the next highest multiple of five. For example, if the highest value in the display is 2.2 seconds, the scale range is rounded up to five seconds. The only exception to this is when the highest value is less than one. In this case, the scale range is set to one.

You override this setting in a very similar way with the MAXSCALE keyword. You set the units of the display by including an s, m, or h suffix with the operand. The numeric part of the operand is processed the same way as the highest interval value. If it is greater than one, it is rounded up to the nearest even multiple of five. If it is less than or equal to one, it is set to one. For example, if you set MAXSCALE(2M), the scale range is rounded up to five minutes. If you specify MAXSCALE(1S), the range is set to one second.

The MAXSCALE keyword is valid with summary displays only; if you enter it for a detail display, it is ignored.



MERGEType: EPILOG Operand

Description: See SYSID.


+=============================================================================+ | Performance Group = 2 Symbolic Name = DEV TSO | | From 18:02 To 24:00 On 06/02/99 SYSA | +-----------------------------------------------------------------------------+ |DATE__START_END___MAIN_REASON(*)_TIME(-)|0S____0.2____0.4____0.6____0.8_____1| |06/02 18:02 18:15 Using CPU 0.62 S|*****--------------->. . .| | 18:15 18:30 Swap Page-In 0.50 S|***-------------> . . .| | 20:06 20:15 Using CPU 0.50 S|****-------------> . . .| | 21:30 21:45 Da 146 SPOOL1 0.56 S|***---------------> . . .| | 21:45 22:00 Swap Page-In 0.07 S|*-> . . . . .| | 22:00 22:15 Swap Page-In 0.46 S|***------------> . . .| | 22:15 22:30 Long Wait Swp 3.28 S|*******************--------------->+| | 22:30 22:45 Long Wait Swp 3.38 S|**************************-------->+| | 22:45 23:00 Detected Wait 0.51 S|******-----------> . . .| | 23:00 23:15 Using CPU 1.01 S|*****----------------------------->+| | 23:15 23:30 Long Wait Swp 0.83 S|***************-------------> .| | 23:30 23:45 Long Wait Swp 2.75 S|****************************------>+| | 23:45 24:00 Long Wait Swp 0.48 S|**********------> . . .| |---------------------------------------- | |Average For This Workload Display 1.15 S | |Productivity Index 22% | +=============================================================================+

N-O Commands and Keywords 129

N-O Commands and Keywords


NOOUTLIER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130NOPLOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130NOPRDX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130NOPRODIDX or NOPRDX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130OBT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130OBTAIN or OBT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130OUTFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138OUTL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138OUTLIER or OUTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

13




NOOUTLIERType: EPILOG Keyword

Description: If you do not specify an OUTLIER value on the PROFILE command, the default is NOOUTLIER and no data records will be excluded from the profile.

Related Information: Keyword of: PROFILE

NOPLOTType: EPILOG Keyword

Description: Suppresses the graphic display that is designed to assist you in selecting an appropriate OUTLIER value for your profile. For more information on this graph, see PLOT.


NOPRDXType: EPILOG Keyword

Description: See NOPRODIDX.


NOPRODIDX or NOPRDXType: EPILOG Keyword

Description: Turns off the productivity index display. This is the default. The keywords PRODIDX and NOPRODIDX are mutually exclusive.



OBTType: EPILOG Command

Description: See OBTAIN.


OBTAIN or OBTType: EPILOG Command

Description: Used to export data from the EPILOG datastore to user-defined output datasets. To export data, you must submit a batch job or execute a CLIST. Two sample files



are included on the product tape to facilitate this process. One file, rhilev.midlev.RKANSAM(KEPOBT), contains sample JCL to submit an OBTAIN job; the other, rhilev.midlev.RKANSAM(KEPOBTC), contains a sample CLIST. The JCL or CLIST must be modified to identify your output datasets. The data to be exported is identified by EPILOG and OBTAIN commands and keywords for the OBTAIN utility in the dataset referenced by the RKM2IN ddname.

OBTAIN {workload|resource}

{FORMAT(COL|INT|PC}

[ELEMENTS(field-name, ...)]

[OUTFILE(ddname)]

[REPLACE|APPEND]

[any DISPLAY keyword]

workload|resource keyword

These keywords identify the resource and workload reports from which data is to be exported. For a list of the resource keywords that you can use with the OBTAIN command, see “Resource display keywords” on page 42. For a list of the workload keywords that you can use, see “Workload keywords” on page 46.

Notes:

1. You must specify at least one workload or resource keyword in each OBTAIN command.

2. The short form of the resource or workload must be used.

3. If you specify more than one resource keyword in an OBTAIN command, you must enclose the keywords in parentheses; then the data from the reports will be joined on their common fields. In most cases, reports will be joined on starting date and time.

4. Some EPILOG reports (such as RCPU) generate one record per interval; others (such as RDAS) generate multiple records per interval. If you use more than one resource keyword with an OBTAIN command and the keywords mix single-record-per-interval reports and multiple-record-per-interval reports, single-record-per-interval elements will be repeated until the interval changes.

5. Joining resource reports and workload reports in an OBTAIN command is not recommended; in most cases, the resulting OBTAIN command will not export any data.

FORMAT(INT|COL|PC)



This keyword specifies the format of the data to be written to the output file. Three options are available for the FORMAT keyword: INT, COL, and PC. INT is the default format.

INT writes binary data. The INT option is advisable if you will be writing your own programs to read the OBTAIN output file.

COL writes printable EBCDIC data arranged in columns. The COL option is advisable if the output file will be used as input to a mainframe graphics or statistics package, such as GDDM/ICU™, or if the output file will be downloaded and used as input to a PC software package such as Lotus 1-2-3. Your installation’s download utility will handle the EBCDIC-to-ASCII conversion.

PC writes printable EBCDIC data arranged in columns. The PC format is the same as the COL format, except that data elements in the COL format are arranged in columns, and data elements in the PC format are delimited with double-quotation marks (for character strings) and blanks (for numbers). Use the format that is best suited for the software application you will be using to process the exported data.

ELEMENTS(field-name,...)

Identifies the elements to be selected from the specified reports. Each EPILOG field name is associated with an element name; in addition, there are data fields that are not displayed on EPILOG reports, but which are available for OBTAIN processing.

If ELEMENT (ELEM for short) is omitted or ELEMENT(*) is specified, all elements for the named reports are selected.

Field names specified by ELEM on an OBTAIN command are extracted only for that command. Field names specified by ELEM on one or more SET commands are cumulative. They will be extracted on all subsequent OBTAIN commands for reports that contain them. SET ELEM(*) or SET ELEM() clears previous elements activated by SET commands.

OUTFILE(ddname) Specifies the name on a DD or FILE statement that defines the dataset to be used as the output file for the OBTAIN command. Use this keyword if you want to override the default name OUTFILE or to export data to more than one dataset during the execution of an OBTAIN command stream.

For example, suppose that you want to export data to two datasets, DSN1 and DSN2. You can do this by creating two DD statements, DSN1 and DSN2, that define the datasets DSN1 and DSN2. You must also add the keywords OUTFILE(DSN1) and OUTFILE(DSN2) to the corresponding OBTAIN commands. (Important: Each OBTAIN command can define only one OUTFILE.)

If you do not use the OUTFILE keyword, OBTAIN uses the dataset that is defined in the RKM2OUTD DD statement as the output file.

REPLACE|APPEND



Output File Contents

Depending upon the output FORMAT, your output file contains up to three record types: the comment record (for binary FORMAT (INT) only), the attribute record, and the observation record(s). The comment records (binary FORMAT (INT) only) contain the text of the OBTAIN command(s) in the command stream; the attribute record defines the elements being selected; and the observation record(s) contain the element values selected from the datastore.

Output File Size

The number of observation records depends on what workload or resource keyword you’re using. A workload keyword like JOBNAME, for example, may generate several observation records (one for each wait reason) per collection interval. You can reduce the number of observation records with the COMBINE keyword, which acts to combine data cross collection intervals. Other keywords that may affect the number of observation records are PLOTMIN, REPORTIF, and SELECTIF.

Because it is difficult to estimate the number of observation records to expect, we recommend that you use generous secondary space allocations for your output file.

Sample Command Stream: FORMAT (COL)

The following sample command stream generated one attribute record and eight observation records.

SET FORMAT(COL)

SET OUTFILE(RINFOUT) REPLACE

SET ELEMENTS(SMFID)

OBT RINF STIME(9) ETIME(11) SDATE(8/2) EDATE(8/2) -

ELEMENTS(IPS,ICS,RMF)

END

The first two SET commands in this example specify the default format, name, and disposition of all output files created by subsequent OBTAIN commands in this job. The first SET command causes all output files to be written in COL format, unless specified otherwise. The second SET command specifies that the output file will be written to the dataset that is defined in the DD or FILE statement RINFOUT. The third SET command requests that all subsequent OBTAIN commands in the command stream extract the element SMFID along with any other elements specified.

Specifies whether obtained data should overwrite (REPLACE) records in an existing output file with the same name, or add (APPEND) records to the end of the file.

When REPLACE is used on an output file with DISP=MOD, the obtained data is added to the end of the file and the existing data is not overwritten.

any DISPLAY keyword

In addition to the keywords described here, you can use all of the usual DISPLAY keywords with the OBTAIN command. See the DISPLAY entry on “DISPLAY or DIS” on page 88 for more information.



A sample of the output file appears below. The records displayed in the figure are in the same format as they would appear if you listed the file at a terminal or printer. Note that since the default sampling interval is 15 minutes and the requested reporting interval is 2 hours (9 to ll), eight observation records are produced.

*SDATE 00 008 N *STIME 08 008 N *SMFID 10 004 C *IPS 14 002 C

*ICS 16 002 C *RMF 18 020 C

008921409:00:04SYSAAAAARMF 4.1.1

008921409:15:02SYSAAAAARMF 4.1.1

008921409:30:04SYSAAAAARMF 4.1.1

008921409:45:01SYSAAAAARMF 4.1.1

008921410:00:00SYSAAAAARMF 4.1.1

008921410:15:01SYSAAAAARMF 4.1.1

008921410:30:02SYSAAAAARMF 4.1.1

008921410:45:01SYSAAAAARMF 4.1.1

This output file will be written to the dataset defined by the RINF DD statement, as specified on the OUTFILE keyword.

Record Structure of Attribute Records in Output Files Generated with FORMAT (COL)

The output file for FORMAT (COL) contains one attribute record for each OBTAIN command in the command stream. The record consists of a list of descriptions, one description for each data element you requested. Each description contains the the following fields:

n 9 byte field, giving the element name, in character representation, preceded by an asterisk (*).

n 3 byte field, giving the offset from the beginning of the record in integer representation.

n 3 byte field, giving the length of the element in bytes, in integer representation.

n 1 byte field, giving the data type (N=numeric signed integer, C=character, H=hexadecimal, or P=packed decimal).

The asterisk acts as a delimiter, flagging the beginning of the description of the next data element.

Output files generated with FORMAT (COL) do not contain comment records.

Sample Command Stream: FORMAT (INT)

The following sample command stream generated five comment records, one attribute record, and eight observation records.

SET FORMAT(INT)

SET OUTFILE(RINFOUT) REPLACE

SET ELEMENTS(SMFID)

OBT RINF STIME(9) ETIME(11) SDATE(8/2) EDATE(8/2) -



ELEMENTS(IPS,ICS,RMF)

END

The first two SET commands in this example specify the default format, name, and disposition of all output files created by subsequent OBTAIN commands in this job. The first SET command causes all output files to be written in INT format, unless specified otherwise. The second SET command specifies that the output file will be written to the dataset that is defined in the DD or FILE statement RINFOUT. The third SET command requests that all subsequent OBTAIN commands in the command stream extract the element SMFID along with any other elements specified.

A sample of the output file appears below. The records displayed in the figure have been interpreted into readable format. If you were to list the contents of an OBTAIN output file generated with FORMAT(INT), much of the data would be non-readable, binary data.

0089216F 0083413F * OBT RINF STIME(9) ETIME(11) SDATE(8/2) EDATE(8/2) -

0089216F 0083413F * DATEFORM(MMDDYY)

0089216F 0083413F * ELEMENTS(IPS,ICS,RMF)

0089216F 0083413F A 06 SDATE P 4 0 00A STIME T 4 0 00E SMFID C 4 0 012

IPS C 2 0 016 ICS C 2 0 018 RMF C20 0 01A

0089216F 0083413F O 0089214F 090004 SYSA AA AA RMF 4.1.1








This output file will be written to the dataset defined by the RINFOUT DD statement, as specified on the OUTFILE keyword.

Record Structures for Output Files Generated with FORMAT (INT)

The output file for FORMAT (INT) contains one or more comment records for each OBTAIN command in the command stream. Each record contains the following fields:

n 4 byte Julian date on which the data was extracted. Shown in packed decimal format.

n 4 byte time stamp showing the time of day that the data was extracted.

n 1 byte record-type indicator of *, indicating that this is a comment record.

n 1 byte reserved field.

n variable length field, giving the text of the OBTAIN command. The first record starts with SDATE and STIME, followed by elements listed in the order you requested them. This field also contains the current settings of any valid keywords that are used for data filtering (such as DATE, TIME, BAND, RANGE, RIF, or SIF).



The output file for FORMAT (INT) further contains one attribute record for each OBTAIN command in the command stream. Each attribute record contains the following fields:

n 4 byte Julian date on which the data was extracted, shown in packed decimal representation.


n 1 byte record-type indicator of A, indicating that this is an attribute record.


n 2 byte field, giving the number of elements being OBTAINed (that is, the number of value fields that will appear in each observation record), shown in integer representation.

n 15 byte field per data element requested, giving the element definition in character representation. The requested data elements are listed in the order in which you requested them.

The element definition section of the attribute record includes 15 bytes of explanatory data for each data element requested. These 15 bytes are divided into the following fields:

n 8 byte element name, in character format.

n 1 byte data type (I=numeric signed integer, U=unsigned integer, P=packed decimal, C=character, D=floating-point, X=hexadecimal, and T=time).

n 1 byte element length in bytes, in integer format.

n 1 byte decimal point displacement (number of positions to the right of the decimal; for example, CPU seconds may be shown to the nearest tenth of a second for a decimal point displacement of 1), in integer format.

n 4 byte field offset (location of the field from the beginning of the observation record, in bytes), in integer format.

Every observation record contains the following fields:

n 4 byte Julian date on which the data was extracted. Shown in packed decimal representation.


n 1 byte record-type indicator of O, indicating that this is an observation record.


n 4 byte field SDATE, which shows the Julian date on which the data was recorded. Shown in packed decimal representation.

n 4 byte field STIME, which shows the start time of the interval for which the data was recorded.

n variable length value field for each element you selected, in the order listed in the attribute record.



Sample Command Sequence: FORMAT (PC)

The following sample command stream generated one attribute record and nine observation records.

SET FORMAT(PC)

OBT RINF STIME(8) ETIME(17) SDATE(8/2) EDATE(8/2)-

COMBINE(1H) ELEMENTS(IPS,ICS,RMF)

END

A sample of the output file appears below. The records displayed in the figure are in the same readable format as they would appear if you listed the file at a terminal or printer. Since the requested combine period was one hour on this OBTAIN command and the requested reporting interval is nine hours, nine observation records are produced.

“SDATE “ “STIME “ “SMFID “ “IPS “ “ICS “ “RMF “

“0089214” “08:00:01” “SYSA” “AA” “AA” “RMF 4.1.1 “

“0089214” “09:00:01” “SYSA” “AA” “AA” “RMF 4.1.1 “

“0089214” “10:00:01” “SYSA” “AA” “AA” “RMF 4.1.1 “

“0089214” “11:00:01” “SYSA” “AA” “AA” “RMF 4.1.1 “

“0089214” “12:00:04” “SYSA” “AA” “AA” “RMF 4.1.1 “

“0089214” “13:00:02” “SYSA” “AA” “AA” “RMF 4.1.1 “

“0089214” “14:04:28” “SYSA” “AA” “AA” “RMF 4.1.1 “

“0089214” “15:00:01” “SYSA” “AA” “AA” “RMF 4.1.1 “

“0089214” “16:00:01” “SYSA” “AA” “AA” “RMF 4.1.1 “

The fourth and fifth fields of each observation record appear in double quotes, whether their values are represented in character or hexadecimal format. In this example, “AA” is a hexadecimal representation.

OBTAIN

Record Structures for Output Files Generated with FORMAT (PC)

The output file for FORMAT(PC) contains one attribute record for each OBTAIN command in the command stream. An example of an attribute record is shown below.

“SDATE “ “STIME “ “SMFID “ “IPS “ “ICS “ “RMF “

The record contains the element names that have been selected, delimited by double quotes.

Every observation record contains the following fields:

n 8 byte field SDATE, which shows the Julian date on which the data was recorded. Shown in packed decimal format.

n 8 byte field STIME, which shows the start time of the interval for which the data was recorded.



n variable length value field for each element you selected, in the order listed on the attribute record. If the value is in character, time, or hexadecimal format, it will be enclosed in double quotes.


OUTFILEType: EPILOG Keyword

Description: Specifies the name on a DD or FILE statement that defines the dataset to be used as the output file for the data exported by the OBTAIN command. Use this keyword if you want to override the default name OUTFILE or to export data to more than one dataset during the execution of an OBTAIN command stream.

For example, suppose that you want to export data to two datasets, DSN1 and DSN2. You can do this by creating two DD statements, DSN1 and DSN2, that define the datasets DSN1 and DSN2. You must also add the keywords OUTFILE(DSN1) and OUTFILE(DSN2) to the corresponding OBTAIN commands. (Important: Each OBTAIN command can define only one OUTFILE.) If you do not use the OUTFILE keyword, OBTAIN uses the dataset that is defined in the RKM2OUTD DD statement as the output file.


OUTLType: EPILOG Keyword

Description: See OUTLIER.


OUTLIER or OUTLType: EPILOG Keyword

Description: Excludes degradation records from the profile that are not representative of the sample. For example, records for jobs that went into a loop or that were cancelled prematurely. Such records generally lie outside the representative elapsed- or response-time range (that is, the range of times that are most typical of the sample). These records are called outliers.

OUTLIER(n)

Your OUTLIER value (0, 1, 2, or 3) determines which outliers are excluded. It specifies a number of QSTEPS above and below the representative time range. (A QSTEP is the difference between the lowest and highest time value in this representative range.) Any outlier that lies beyond this range of QSTEPS above and/or below the representative range is excluded.

For example, if your representative range has a low record of 6 minutes and a high record of 8 minutes, the QSTEP is 2 minutes. Thus, if you were to specify OUTLIER(1), any outlier that had an elapsed time less than 4 minutes or greater than 10 minutes would be excluded.



OUTLIER(0) is the most conservative position you can take: it excludes the greatest number of degradation records from the profile. As the OUTLIER value increases from 0 to 3, the definition of what is representative of the sample is broadened, possibly embracing more degradation records. If you do not specify an OUTLIER value, the default is NOOUTLIER and no data records will be excluded.

To simplify your choice of OUTLIER value, the PLOT default generates a graph of the sample and shows the different ranges of OUTLIER values. Following is a sample elapsed time plot.


+------------------------------ELAPSED TIME PLOT------------------------------+| Job = SMFANAT Profname = SMFANAT || |+-----------------------------------------------------------------------------+| || || F 10+ || R | || E | || Q | || U | || E 5+ || N | || C | * || Y | * || |* * *** ** * || +---------+----------+---------+---------+---------+ || 35.79 S 58.75 S 1:21 M 1:44 M 2:07 M 2:30 M || OUTLIER(0) RANGE ( 1:10 M , 1:33 M ) INCLUSIVE. || OUTLIER(1) RANGE (47.32 S , 1:56 M ) INCLUSIVE. || OUTLIER(2) RANGE (37.68 S , 2:19 M ) INCLUSIVE. || OUTLIER(3) RANGE (37.68 S , 2:42 M ) INCLUSIVE. || |+-----------------------------------------------------------------------------+

P-Q Commands and Keywords 141

P-Q Commands and Keywords


Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142PAGESEP or PSEP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142PDAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143PER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144PERFGROUP or PGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144PFK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146PGM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148PGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148PGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149PGPERIOD or PGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149PLOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150PLOTMIN or PMIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150PMIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151PNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151PRDD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151PRDX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151PRDXDEF or PRDD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151PRODIDX or PRDX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153PRODUCTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153PROF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153PROFILE or PROF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153PROFNAME or PNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156PROGRAM or PGM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157PSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158QUEUEDIO or QIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158QIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160QUIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

14




PType: EPILOG Navigational Command

Description: Navigates you from the DASD Resource or the Workload Degradation display to the Shared-DASD Degradation (by Performance Group) display in a multi-system configuration.

Related Information: Other Fast Path Navigation Commands: D, J, R, S, V, W, and X

PAGESEP or PSEPType: EPILOG Command

Description: Formats separator pages between batch reports. This command is only used in batch mode.

PSEP [BLOCK(cccc)] -

[DUPLICATE(n)] -

[TITLE(cccc)] -

[TITLE2(cccc)] -

[TITLE3(cccc)]

The following example illustrates how the PAGESEP command is used to set up a title page.



Note that TITLE, TITLE2, TITLE3 and BLOCK may be used on the same command.

The PAGESEP command above produces the following page separator three times on the dataset identified by the RKM2OUTR DD statement.




Related Information: Command of: BLOCK, DUPLICATE, TITLE, TITLE2, and TITLE3


See also LIMIT.

PDASType: EPILOG Keyword

Description: Displays shared-DASD degradation for the indicated device, showing relative usage by performance group in a multiple-system configuration. Use the following syntax for the PDAS keyword.

Display {PDAS(volser)} -

[time period]

For example,

DISPLAY PDAS(COM002) YDAY STIME(14:15) ETIME(14:30)

generates displays similar to the sample report below.

The display uses the symbolic names defined for each performance group. If these names have not been defined, PERFnnn is used, where nnn is the performance group number. In this example, the jobs $AOASMP1 and $AOASMP2 have been defined in the same performance group, REGBATCH. The Queued I/O portion of the display contains a rolled up percentage for REGBATCH for these two jobs, which would appear separately in a JDAS display.

volser Volume to be analyzed. The operand is 6 characters long.

time period Time period to be analyzed, using the date and time keywords listed in Date and Time Keywords in “Command Groupings” on page 19.

+==============================================================================+ | Volume = COM002 Period = 02:15 to 02:30 on 02/16/99 | +------------------------------------------------------------------------------+ | Relative Usage of selected DASD device for Cross-system ACTIVE I-O | +------------------------------------------------------------------------------+ | Perf Grp______Sysid_Time________%__|0___1___2___3___4___5___6___7___8___9___0| | HOTBATCH SYSA 5:32 M 82.1 |------------============>>>>>>>>>> . .| | REGBATCH SYSF 45:98 S 11.4 |-----> . . . . . . . . .| | PERF121 SYSA 26:22 S 6.5 |--> . . . . . . . . . .| +------------------------------------------------------------------------------+ | Relative Usage of selected DASD device for Cross-system QUEUED I-O | +------------------------------------------------------------------------------+ | Perf Grp______Sysid_Time________%__|0___1___2___3___4___5___6___7___8___9___0| | REGBATCH SYSF 30:48 S 68.6 |------------============>>>>. . . .| | HOTBATCH SYSA 13:94 S 31.4 |------------==> . . . . . . .| +==============================================================================+




Other Shared-DASD Degradation Display Keyword: JDAS

PERType: EPILOG Keyword

Description: Selects one or more service class periods for one or more service classes. This keyword must be used in conjunction with the SERVCLAS keyword. The operand for this keyword is one or more service class periods.

Service classes are often defined with multiple periods to help manage workloads in the same service class that have different processing requirements. In particular, first period TSO is often of interest because it is generally used as a critical measure of overall TSO performance. For example, to obtain period 1 information about service class TSOSERV, enter:

OBTAIN SERVCLAS(TSOSERV) PER(1)

If you enter multiple periods, the data is combined together. For example, to specify periods 1 and 2 of service class TSOSERV, enter:

OBTAIN SERVCLAS(TSOSERV) PER(1,2)

This keyword is only valid when the system is running in WLM goal mode.

Related Information: Keyword of: EXTRACT, INQUIRE, and OBTAIN


PERFGROUP or PGNType: EPILOG Keyword

Description: Allows you to select one or more performance groups for degradation analysis. The operand for this keyword is 0-9999 characters long.

To select a specific performance group, include the performance group number as an operand. For example, the command

Display PGN(2) YDAY STIME(15) ETIME(17)



might result in a display that includes the following panel:

There are several additional options for refining your performance group selection:

n If you have defined symbolic names for certain performance groups during collector startup, you can refer to those performance groups by their symbolic names using the SYMBOLIC keyword.

n For performance groups defined with multiple periods, you can Display degradation data for one or more performance periods by adding the PGPERIOD keyword to the PGN keyword.

n You can display systemwide degradation across performance groups using the XPG keyword.

At times you may want to combine data from several performance groups and treat them as a single workload. For example, suppose you have three TSO performance groups defined at your installation (2, 4 and 12). These three groups may be combined by specifying them all as operands to the PGN keyword. For example, the command

Display PGN (2,4,12) YDAY STIME(15) ETIME(17)

might result in the following multiple performance group degradation display:

+=============================================================================+| Performance Group = 2 Symbolic Name = DEV TSO || From 15:16 To 15:30 On 10/01/99 Elap = 13:44 M SYSA | +-----------------------------------------------------------------------------+ |Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0||Using CPU 0.10 S 3.6|-> . . . . . . . . . .||Waiting For CPU 0.95 S 36.0|------------==> . . . . . . .||Terminal Output Wait 0.41 S 15.3|------> . . . . . . . . .||Swap Page-In Wait 0.20 S 7.5|--->. . . . . . . . . .||SRM Delay (MPL) 0.18 S 6.8|--> . . . . . . . . . .||Private Page-In Wait 0.17 S 6.5|--> . . . . . . . . . .|

+=============================================================================+ | Performance Groups = (2,4,12) | | From 15:16 To 15:30 On 10/01/99 Elap = 13:44 M SYSA | +-----------------------------------------------------------------------------+ |Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0| |Using CPU 0.04 S 1.4|. . . . . . . . . . .| |ECB Wait 0.89 S 33.4|------------=> . . . . . . .| |Waiting For CPU 0.45 S 16.8|------> . . . . . . . . .| |ECB Wait (W/ STIMER) 0.40 S 15.1|------> . . . . . . . . .| |STIMER Wait 0.28 S 10.4|----> . . . . . . . . .| |Terminal Output Wait 0.16 S 5.9|--> . . . . . . . . . .| |Average Trans Time 2.65 S 2348 MVS Transactions Ended | |Productivity Index 15% | +=============================================================================+



It produces the same results as if a report performance group containing these three control groups had been defined in the ICS and specified in the Display command.



n Performance group degradation data (SAS dataset PGNDETL): DEVADD, EDATE, EDATTIME, ETIME, ENQNAME, EXTDTIME, NUMICMB, NUMTRX, PGN, PGNTYPE, PGP, PRODIDX, SDATE, SDATTIME, STIME, SMFID, SYMBNAME, TOTCPUTM, TRXELAP, TRXRESP, TRXTHINK, VOLSER, WAITNAME, WAITPCT, WAITTIME, and WKLNAME.

n Performance group degradation data (SAS dataset PGNCOMP): DEVADD, DPRODIDX, DTRXRESP, DWAITTME, EDATTIME, ENQNAME, PAVGTRX, PDATTIME, PEDATTIM, PGN, PGNTYPE, PGP, PPGN, PPGNTYPE, PPGP, PPRODIDX, PRODIDX, PROFNAME, PSDATTIM, PSMFID, PSYMBNAM, PWAITPCT, PWAITTME, PWKLNAME, SDATTIME, SMFID, SYMBNAME, TRXRESP, VOLSER, WAITNAME, WAITTIME, WAITPCT, and WKLNAME.




Other Performance Group Keywords: See Performance Group Keywords in “Command Groupings” on page 19.

PFKType: EPILOG Reporter Command

Description: Allows you to display and modify current PF key definitions. The default PF key definitions are contained in the KEPDEFEO member of the rhilev.midlev.RKANPAR dataset. The PFK command allows you to change this default member, or to create a new one which you can invoke during the reporter session.

When the PFK command is processed, the syntax of the PF key definition is checked, and any errors are flagged with an appropriate message. If you use an external editor to create or modify these members, syntax checking will be done when the PFK function is executed, and it may not always be obvious that the error was caused by the faulty PF key definition. For this reason, we recommend that you use the PFK command rather than an external editor to create and maintain PF key definitions.

The PFK command accepts a 1- to 7-character member name as an operand. The member name you enter is then prefixed with a dollar sign ($) to generate the actual member name in rhilev.midlev.RKANPAR. For example, if you enter:



PFK SAVE (MYPFKS) . . .

The name of the member created in rhilev.midlev.RKANPAR. is $MYPFKS.

The PFK command allows you to perform four basic functions:

n modify a PF key definition

n create a pseudo-PF key definition

n save new PF key definitions in a member of rhilev.midlev.RKANPAR.

n load a set of PF key definitions from a member of rhilev.midlev.RKANPAR.

The syntax of the command is shown below.

PFK [nn ‘command’]

or

PFK [SAVE(ccccccc)]

or

PFK [READ(ccccccc)]

where nn = a PF key number (1-99) and ccccccc = a PFK member name.

If the command is entered without any keywords, the current PF key definitions are displayed. The default PF key assignments are as follows.

nn ‘command’ If the PF key number is entered with a command, the command function is assigned to that PF key. You can create up to 99 pseudo-PF key definitions in this way. For example,

PFK 22 ‘DISPLAY PGN(2) TODAY’assigns the specified command to PF22.

nn If the pseudo-PF key number is entered by itself, the command associated with that PF key is executed. For example,

7executes the command associated with PF7 (by default, ‘CONTROL SCROLL UP’).

SAVE(ccccccc) Saves the changes in the specified PFK member. For example,

PFK SAVE(MYPFKS)saves the current PF key definitions in the $MYPFKS member of the rhilev.midlev.RKANPAR partitioned dataset. (Note that the name you specify is prefixed with a dollar sign ($) to name the member in rhilev.midlev.RKANPAR.)

READ(ccccccc) Reads in the specified PFK member, and uses those PF key definitions for the current reporter session. For example,

PFK READ(MYPFKS)reads in the $MYPFKS member of rhilev.midlev.RKANPAR and uses it as the current PF key definitions.



Related Information: Command of: READ and SAVE

Other Reporter Commmands: See Reporter Commands in “Command Groupings” on page 19.

PGMType: EPILOG Keyword

Description: See PROGRAM.


PGNType: EPILOG Keyword

Description: See PERFGROUP.


PF1/PF13 HELP (no operands)

PF2 RESERVED FOR ISPF SPLIT SCREEN -To modify this assignment, you must return to the Split Screen Options Menu.

PF3/PF15 BACK - Return to the previous display.

PF4/PF16 CONTROL RECALL - Display the last command issued.

PF5/PF17 CONTROL TITLE - Display the report title block.

PF6/18 DISPLAY - Sample command to display all resource panels for today, averaged together from 09:00 to 17:00.

PF7/PF19 CONTROL SCROLL UP - Scroll back, toward the top, one report or screen at a time.

PF8/PF20 CONTROL SCROLL DOWN - Scroll forward, toward the bottom, one report or screen at a time.

PF9 RESERVED FOR ISPF SWAP SCREEN - To modify this assignment, you must return to the Split Screen Options Menu.

PF10/22 DISPLAY - Sample command to display an hourly summary of today’s degradation for performance group 2.

PF11/23 DISPLAY - Sample command to display all intervals today when the TSO response time of performance group 2 was greater than one second.

PF12/PF24 PFK - Display the current PFK definitions.

PF14 CONTROL MODE - Advances through display modes (PAGE, ROLL, HOLD, ONE). Each depression of the PF key advances to the next mode.

PF21 CONTROL LOG - Logs the current screen to the dataset referenced by the RKM2LOG ddname.



PGPType: EPILOG Keyword

Description: See PGPERIOD.


PGPERIOD or PGPType: EPILOG Keyword

Description: Selects one or more performance periods for one or more performance groups. This keyword must be used in conjunction with the PGN or RPGN keyword, and is not allowed with the SYMBOLIC keyword. The operand for this keyword is one or more performance periods.

Performance groups are often defined with multiple periods to help manage workloads in the same performance group that have different processing requirements. In particular, first period TSO is often of interest because it is generally used as a critical measure of overall TSO performance. For example, to Display period 1 information about performance group 2, enter:

DISPLAY PGN(2) PGP(1)

The result might look like the following:

If you enter multiple periods, the data is combined together into a single display panel. For example, to specify periods 1 and 2 of performance group 2, enter:

DISPLAY PGN(2) PGP(1,2)

Note that the PGPERIOD keyword is also valid with the RPGN keyword, which Displays resource utilization information for performance groups.




+=============================================================================+ | Performance Group = (2) Period = (1) | | From 09:00 To 09:15 On 08/15/99 Elap = 13:44 M SYSA | +-----------------------------------------------------------------------------+ |Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0| |Using CPU 0.02 S 3.9|-> . . . . . . . . . .| |Terminal Output Wait 0.19 S 30.0|------------> . . . . . . .| |Waiting For CPU 0.12 S 18.5|------->. . . . . . . . .| |Swap Page-In Wait 0.09 S 14.1|-----> . . . . . . . . .| |Private Page-In Wait 0.04 S 5.9|--> . . . . . . . . . .| |Average Response Time 0.67 S 25230 MVS Transactions Ended | |Productivity Index 5% | +=============================================================================+



PLOTType: EPILOG Keyword

Description: Generates a graph with the workload’s elapsed or response times plotted on the horizontal axis and their frequency on the vertical axis in order to assist you in selecting an appropriate OUTLIER value. PLOT generates a graph of the sample and shows the range of data values associated with each OUTLIER value (0, 1, 2, and 3). Below is a sample elapsed time plot.

PLOT is the default. To overide it, specify NOPLOT.


PLOTMIN or PMINType: EPILOG Keyword

Description: Limits the display by excluding wait reasons that cause less than a certain percentage of the total wait time. The default is 5%. The operand for PLOTMIN is a percentage (0 to 99). For example,

DISPLAY PGN(2) PLOTMIN(10)

specifies that only wait reasons that account for 10% or more of the overall wait time are to be included in the display.

By default, the reporter excludes wait reasons that account for less than 5% of the wait time. Adjusting this figure downwards shows more wait reasons; setting the figure at zero (0) shows all wait reasons.

+------------------------------ELAPSED TIME PLOT------------------------------+| Job = SMFANAT Profname = SMFANAT || |+-----------------------------------------------------------------------------+| || || F 10+ || R | || E | || Q | || U | || E 5+ || N | || C | * || Y | * || |* * *** ** * || +---------+----------+---------+---------+---------+ || 35.79 S 58.75 S 1:21 M 1:44 M 2:07 M 2:30 M || OUTLIER(0) RANGE ( 1:10 M , 1:33 M ) INCLUSIVE. || OUTLIER(1) RANGE (47.32 S , 1:56 M ) INCLUSIVE. || OUTLIER(2) RANGE (37.68 S , 2:19 M ) INCLUSIVE. || OUTLIER(3) RANGE (37.68 S , 2:42 M ) INCLUSIVE. || |+-----------------------------------------------------------------------------+



By including the PLOTMIN (or PMIN) keyword in a DISPLAY command, you set the minimum wait reason percentage for that command only. Alternatively, you can set a PLOTMIN default for all successive DISPLAY commands by using the SET command.



PMINType: EPILOG Keyword

Description: See PLOTMIN.


PNAMEType: EPILOG Keyword

Description: See PROFNAME.


PRDDType: EPILOG Keyword

Description: See PRDXDEF.


PRDXType: EPILOG Keyword

Description: See PRODIDX.


PRDXDEF or PRDDType: EPILOG Keyword

Description: Specifies a productivity index definition member of rhilev.midlev.RKANPAR. (The productivity index definition is used to calculate the productivity index shown on workload degradation displays, and the member is invoked whenever a degradation display is requested.) By default, degradation displays use the KEPDEFP member of rhilev.midlev.RKANPAR; the SET command allows you to specify another member.



The operand for PRDXDEF is 1–7 characters. The definitions in the KEPDEFP member group detail wait reasons into three categories:

Each line in the productivity index member associates a detail wait reason with one of these categories. Remember, if a wait reason is not defined, it is considered unproductive by default.

If you wish to set up your own set of productivity index definitions, copy the KEPDEFP member into another member of rhilev.midlev.RKANPAR; and then modify your own definition member. Observe the following guidelines:

1. Each line in the definition member associates a detail wait reason code with one of two categories (PROD and IDLE). Valid detail wait reason codes are listed in Wait Reason Codes, Detail in “Command Groupings” on page 19.

2. Both the detail wait reason code and the category must be enclosed in single quotes. (The equal sign between them is optional.)

The productivity index shown on the display screen is calculated by dividing the time spent doing productive work by the time spent productively and unproductively:

Productivity Index = Productive reasons

(Productive + Non-productive reasons)

Time spent in idle states is not relevant to degradation, and is disregarded in the calculation of the productivity index.

You invoke the new definitions with the PRDXDEF keyword and the DISPLAY or SET commands. For example, if you copied KEPDEFP to a member called MYINDEX in rhilev.midlev.RKANPAR, and then modified the productivity index definitions in it, you could invoke it during a reporter session by issuing the following command:

SET PRDXDEF(MYINDEX)

The definitions in MYINDEX would then be used to calculate the productivity index anytime a workload degradation display was generated. To reset the definitions back to the defaults, simply enter:

SET PRDXDEF(KEPDEFP)


Productive states are those in which the workload is executing in some fashion, and are not considered degradation. By default, Using CPU, Active I/O, and STIMER waits are considered productive states.

Unproductive states are those in which the workload is waiting to execute, but is being prevented from doing so because a resource is not available. All detail wait reasons are considered unproductive unless they are specifically defined otherwise.

Idle states are those in which the workload is not doing productive work, but is also not being prevented from doing so. By default, terminal input waits are considered an idle state.




PRODIDX or PRDXType: EPILOG Keyword

Description: Turns on the productivity index display.

The keywords PRODIDX and NOPRODIDX are mutually exclusive. The default is NOPRODIDX.



PRODUCTSType: EPILOG Reporter Command

Description: Displays the version numbers and expiration dates of all Candle background monitors currently installed. There are no operands. The output of the command looks like this:


PROFType: EPILOG Reporter Command

Description: See PROFILE.


PROFILE or PROFType: EPILOG Reporter Command

Description: Creates a profile by averaging degradation data for a specified workload.

PROFILE {workload} -


[time period] -

[SYSID(cccc,...)] -

C U R R E N T P R O D U C T S ------------- --------------- EPILOG/MVS VERSION 350 EXPIRES 9/15/99



[OUTLIER(n) | NOOUTLIER]

[SELECTIF(filter)]

[PLOT | NOPLOT]

[TEST]

The only required keywords for this command are a workload identifier and a profile name.

workload The workload keywords identify the batch job, performance group, started task, or TSO user session for which you are creating a profile. In addition to these workload keywords, you can use the SYSTEM keyword to profile degradation data for all workloads on the system. For a list of workload keywords, see Workload Keywords in “Command Groupings” on page 19. All of these keywords are valid on the PROFILE command except STEP and INTERVAL. Multiple workload keywords are only permitted if they are of the same type.

If you specify two or more workloads of the same type, WPF generates a profile for each workload specified; if you specify an asterisk (*) for a workload, WPF generates a profile for each workload that qualifies.

PROFNAME(cc...cc)

Lets you assign a profile name, 1 - 16 characters, to the workload. Use quotation marks to enclose blanks and special characters. If you do not enter an operand, WPF assigns the profile the PNAME default (automatic). This default is used to create profiles of multiple workloads of one type, such as JOB(*).

time period Specifies the date and time interval for which you want WPF to select data. To find more information, see Date and Time Keywords in “Command Groupings” on page 19.

SYSID(cccc,...) Specifies an SMF system ID for the workload. Required only when the records in your EPILOG datastore have different SYSIDs and you want to create a profile for a workload running under a specific SYSID. If you specify multiple SYSIDs, for example (SYSA,SYSB), you generate a separate profile for each SYSID. If you do not specify a SYSID, your other selection criteria determine which records, regardless of their SYSIDs, go into the profile.



For example,

PROFILE TSO(USER04) -

PNAME(‘PRIME SHIFT’) -

LASTWEEK BAND STIME(0900) ETIME(1700) -

SIF(ELAPSED(>30m)) -

OUTLIER(3)

OUTLIER(n) Excludes, from the workload profile, degradation records that do not represent the sample, such as (for example), records for jobs that have gone into loops or that have been cancelled prematurely. Such records are called outliers because such records lie outside the sample’s representative range of elapsed or response times.

In the sample’s representative range, the difference between the lowest and highest times is a QSTEP. You exclude outliers by specifying an OUTLIER value (0, 1, 2, 3) that is the number of QSTEPs away from this representative range. For example, if your representative range has a low record of 6 minutes and a high record of 8 minutes, the QSTEP is 2 minutes. Therefore, if you specify OUTLIER(1), EPILOG excludes all degradation records that have elapsed times less than 4 minutes or greater than 10 minutes.

OUTLIER(0) is the most conservative position you can take: it excludes the greatest number of degradation records from the profile. As the OUTLIER value increases from 0 to 3, the definition of what is representative of the sample is broadened, possibly embracing more degradation records.

If you do not specify an OUTLIER value, NOOUTLIER is the default, and no degradation records are excluded.

SELECTIF(filter)

Specifies your criteria for filtering workload records from the EPILOG datastore. Valid workload exception filters can be:n Elapsed time (ELAPSED or ELAP) for batch jobs, started tasks, or TSO

user sessions.n Response time (RESPONSE or RESP) for performance groups.n Detail wait reason codes, as defined in the description of the EXWAIT

keyword.For more information, see the SELECTIF entry.

PLOT Generates a graph with the workload’s elapsed or response times plotted on a horizontal axis and their frequency on a vertical vertical axis. To help you select an appropriate OUTLIER value, the horizontal axis also indicates outlier ranges. PLOT is the default. To override it, specify NOPLOT.

TEST Instructs WPF not to write the profile it has generated to the profile datastore. You can then create and display profiles while testing for the most appropriate OUTLIER value without wasting datastore space.

We recommend that you specify the PLOT keyword, or leave it as the default when using TEST so you can see all ranges of outliers generated by your test profile.



generates a profile that contains the averaged degradation data for all TSO sessions with user ID USER04 that ran last week between 9 a.m. and 5 p.m. and that had an elapsed time greater than 30 minutes. PNAME assigns the profile the name PRIME SHIFT. Before the data is averaged, OUTLIER(3) excludes any job that falls outside the third range of outliers.

The following command is equivalent to two separate PROFILE commands:

PROFILE PGN(2,12) -

PNAME(TSO) -

LASTWEEK BAND STIME(0900) ETIME(1700) -


OUTLIER(3)

creating two profiles. Each profile contains the averaged degradation data for one of the specified performance groups for last week between 9 a.m. and 5 p.m., where the elapsed time exceeded 30 minutes. PNAME assigns the profiles the name TSO. Before the data is averaged, OUTLIER(3) excludes any transaction record that falls outside the third range of outliers.

Finally,

PROFILE JOB(*) -

PNAME -

LASTWEEK -


OUTLIER(3)

creates a profile for each job in the system that ran last week where the elapsed time was greater than 30 minutes. Since the user has not specified a value for PNAME, WPF assigns the PNAME default in lieu of a specific profile name. To identify profiles created with the PNAME default in other WPF commands, simply specify the PNAME keyword without any operand. Using the PNAME default simplifies the creation of profiles for generic workloads. As in our previous example, OUTLIER(3) excludes from the data sample any records that fall outside the third outlier interval.

Related Information: Command of: Workload Keywords in “Command Groupings” on page 19.

PROFNAME or PNAMEType: EPILOG Keyword

Description: Specifies the 1- to 16-character profile name assigned to the profile.

PROFNAME(cc...cc)

If your profile name contains any blanks or special characters, you must enclose it within quotation marks. You cannot use the asterisk as a substitute for a profile name or for any part of a profile name. Keep in mind that the profile is identified by a unique combination of profile name, workload, time period, and SYSID. Thus, when you use PROFNAME on the PROFILE command, you should select a name that is meaningful and easy to remember.



If you enter PNAME without an operand on the PROFILE operand, WPF assigns the profile the PNAME default (that is, automatic). This default is used when creating profiles for multiple workloads of one type, such as JOB(*). If you created a profile with the PNAME default, then you must specify PNAME without an operand whenever you want to refer to that profile with COMPARE and COMPEXT.

Related Information: Keyword of: COMPARE, COMPEXT, EXTRACT, INQUIRE, OBTAIN, and PROFILE

PROGRAM or PGMType: EPILOG Keyword

Description: Selects batch job, started task, or TSO session degradation data by program name. The operand for this keyword is 1–8 characters; it also accepts a wildcard (*) character.

If the JOB, STC, or TSO keyword is included with the command, one display panel is generated for each job run, started task, or TSO session that met the criteria. If none of these keywords is included, a separate display panel is generated for each job, task, or session step that executed the specified program. For example,

DISPLAY PGM(IEB*)

Displays degradation data for all workloads that executed programs beginning with IEB. A separate display panel is generated for each step that meets the PGM criteria. If data was collected at intervals, all interval records within the step are combined into a single display panel.


Since PROGRAM can be used to select batch jobs, started tasks, and TSO user sessions, you might write to several SAS datasets with a single EXTRACT command using PROGRAM. Depending upon the type of degradation data being exported, EXTRACT...PROGRAM... or COMPEXT...PROGRAM... writes the following data elements to the respective SAS report:











Related Information: Keyword of: COMPARE, COMPEXT, DISPLAY, EXTRACT, INQUIRE, OBTAIN, and SETP


PSEPType: EPILOG Command

Description: See PAGESEP.


QUEUEDIO or QIOType: EPILOG Detail Wait Reason Code

Description: Used in exception analysis to exclude or select delays due to waiting for queued I/O. The valid device and enqueue operands are:






Exception applies only to the specified DASD device (cuu = the device address in MVS/370; nnnn = the device number in MVS/XA and above). (This option is allowed with the NO prefix; the NODASD exception applies if no DASD waits were seen.)


Exception applies only to the specified DASD device (cuu = the device address in MVS/370; nnnn = the device number in MVS/XA and above). (This option permits the NO prefix; the NODISK exception applies only if no DASD waits were seen.)



Exception applies only to the specified tape device (cuu = the device address in MVS/370; nnnn = the device number in MVS/XA and above). (This option is allowed with the NO prefix; the NOTAPE exception applies only if no tape waits were seen.)


Exception applies only to the specified disk or tape device (cuu = the device address in MVS/370; nnnn = the device number in MVS/XA and above). (This option is allowed with the NO prefix; the NOUNIT exception applies only if no disk or tape waits were seen.)










For example,

DISPLAY STC(IMSCNTL) SIF(QIO(ANY >10%)) INTERVAL YDAY

displays all intervals in which started task IMSCNTL waited for queued I/O to any device more than 10% of the time.


QIOType: EPILOG Detail Wait Reason Code

Description: See QUEUEDIO.


QUITType: EPILOG Reporter Command

Description: See END.













R Commands and Keywords 161

R Commands and Keywords


Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163RALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163RANGE or RNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163RCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163RCHN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164RPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164RCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164RDAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165RDOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166REOPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166REPLACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167REPLACEM or RMAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167REPORTIF or RIF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168REPTCLAS or RPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175RESOURCE or RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176RESP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177RESPONSE or RESP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177RIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177RINF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178RLCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178RMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180RNG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180RPAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180RPDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180RPGN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181RSCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181RSDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

14


RSRM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182RSWA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182RSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183RVLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183




RType: EPILOG Navigational Command

Description: Navigates you from the Degradation display to the Resource display.

Related Information: Other Fast Path Navigation Commands: D, J, P, S, V, W, and X

RALLType: EPILOG Keyword

Description: Generates information about all resource types. RALL is the equivalent of the command with every resource keyword.

Related Information: Keyword of: DISPLAY, EXTRACT, INQUIRE, and OBTAIN

Other Resource Keywords: RCCH, RCHN, RCPU, RDAS, RDOM, RINF, RLCU, RPAG, RPDS, RPGN, RSCL, RSDS, RSRM, RSWA, RSWR, RVLF

RANGE or RNGType: EPILOG Keyword

Description: Displays data from the start time and date to the end time and date. For example, if you enter:

DISPLAY... STARTDATE(9/5/99) STARTTIME(0900) -

ENDDATE(9/10/99) ENDTIME(1700) RANGE

the data DISPLAY will begin at 9:00 AM on 9/5/99 and end at 5:00 PM on 9/10/99. If you had specified BAND instead of RANGE, the DISPLAY would only contain data gathered between the hours of 9:00 AM - 5:00 PM on the specified days. BAND is the default value. The keywords BAND and RANGE are mutually exclusive.



RCCHType: EPILOG Keyword

Description: Generates information about cache subsystem activity.

When Exporting Data

When exporting data, RCCH writes the following data elements: VOLSER, DEVADD, CNTRLMOD, SUBSYSID, STGDIR1, STGDIR2, CACHSTT1, CACHSTT2, RDHITTOT, RDHITSQ1, RDHITSQ2, RDHITNM1, RDHITNM2, WRHITTOT, WRHITSEQ, WRHITNM1, WRHITNM2, WRHITCFW, DASDFWST, WRHITDFS, WRHITDFN, RDHITCFW, RDWRTRT,



INHBCCH1, INHBCCH2, BPSSCCH1, BPSSCCH2, DFWBYPSS, DASDCCHS, DASDCCHN, CCHDASDN, WRITENM1, WRITENM2, WRITESQ1, WRITESQ2



Other Resource Keywords: RALL, RCHN, RCPU, RDAS, RDOM, RINF, RLCU, RPAG, RPDS, RPGN, RSCL, RSDS, RSRM, RSWA, RSWR, RVLF

RCHNType: EPILOG Keyword

Description: Generates information about physical channel activity. One record (or SAS observation) is generated for each channel on your system.

When Exporting Data

When exporting data, RCHN writes the following data elements: CHPID, CHNTYPE, CPBUSUSE, CPCTBUSY, CPLRRATE, CPLTBUSY, CPLWRATE, CPCRRATE, CPCWRATE, DSXAFLAG, EDATE, EDATTIME, ETIME, EXTDTIME, NUMICMB, OSLEVEL, SDATE, SDATTIME, STIME, SMFID,



Other Resource Keywords: RALL, RCCH, RCPU, RDAS, RDOM, RINF, RLCU, RPAG, RPDS, RPGN, RSCL, RSDS, RSRM, RSWA, RSWR, RVLF

RPCType: EPILOG Keyword

Description: See REPTCLAS.


RCPUType: EPILOG Keyword

Description: Generates information about CPU activity. For multi-CPU systems, there is one record for each CPU, and the common system-wide variables such as BATMINAS and READYIN are repeated.

When Using RCPU with REPORTIF



RCPU panels contain both tabular and panel-level data. A sample RCPU panel is shown below.

Notice that most of this panel fits the definition of being panel-oriented. However, the right side of the display contains a list of processors, showing the percent utilization, interrupts, and TPI instructions for each. This is a tabular kind of organization, and the data cannot be handled adequately by simple panel-level selection.

In this case, you can specify CPU utilization, interrupts, or TPI instructions on the REPORTIF command, and display the panel if any of the processors satisfies the condition.

When Exporting Data

When exporting data, RCPU writes the following data elements: BATMINAS, BATMAXAS, BATAVGAS, STCMINAS, STCMAXAS, STCAVGAS, TSOMINAS, TSOMAXAS, TSOAVGAS, READYIN, READYOUT, OSLEVEL, PCTCPSRB, PCTCPTCB, PCTCPMVS, CPUID, PCTCPU, IOINTRPT, PCTTPI, PCTPARTA, PCTPRTCP, PCTPRMCP, CPUFLAG, DSXAFLAG, EDATE, EDATTIME, ETIME, EXTDTIME, NUMICMB, OSLEVEL, SDATE, SDATTIME, STIME, SMFID



Other Resource Keywords: RALL, RCCH, RCHN, RDAS, RDOM, RINF, RLCU, RPAG, RPDS, RPGN, RSCL, RSDS, RSRM, RSWA, RSWR, RVLF

RDASType: EPILOG Keyword

Description: Generates information about DASD device activity. One record is generated for each DASD device on your system.

When Exporting Data

When exporting data, RDAS writes the following data elements: DEVADD, VOLSER, DLCUID, DIOPRSEC, TOTIOTME, DPCTBUSY, IOSQTIME, PENDTIME, CONNTIME, DISCTIME, DCUBSY, DDEVBSY, OPENDSN, DSXAFLAG, EDATE, EDATTIME, ETIME, EXTDTIME, MACHFLAG, NUMICMB, OSLEVEL, SDATE, SDATTIME, STIME, SMFID


+============================== CPU Activity =================================+| From 13:45 to 14:00 on 07/19/99 Elap =15:00 M SYSX |+-----------------------------------------------------------------------------+| Interrupt || || Min Max Avg Ready Users Logical CPU Utilization Rate %TPI || --- --- ---- ----------- ------------------------- --------- ---- || Batch 18 23 20.3 In = 1.2 SRB= 10.2% CPU1 = 48.7% 144.1 3.95 || STC 54 59 56.6 Out = .0 TCB= 63.1% CPU2 = 47.8% 279.9 4.86 || TSO 8 8 8.0 MVS= 23.3% || || Average Logical Processor Utilization = 48.3% || Physical CPU Utilization For This Partition = 48.3% |+=============================================================================+




Other Resource Keywords: RALL, RCCH, RCHN, RCPU, RDOM, RINF, RLCU, RPAG, RPDS, RPGN, RSCL, RSDS, RSRM, RSWA, RSWR, RVLF

RDOMType: EPILOG Keyword

Description: Generates information about SRM domain activity. One record is generated for each domain defined on your system.

When Exporting Data

When exporting data, RDOM writes the following data elements: DOMNUM, MINMPL, MAXMPL, TARGMPL, CURMPL, CONTIDX, AVGURDY, AVGUIN, AVGUOUT, AVGUGOUT, AVGNSWAP, INTVLSRV, EDATE, EDATTIME, ETIME, EXTDTIME, NUMICMB, OSLEVEL, SDATE, SDATTIME, STIME, SMFID



Other Resource Keywords: RALL, RCCH, RCHN, RCPU, RDAS, RINF, RLCU, RPAG, RPDS, RPGN, RSCL, RSDS, RSRM, RSWA, RSWR, RVLF

REOPENType: EPILOG Reporter Command

Description: Modifies the number of index or data buffers used by RTA™ to read the EPILOG datastore. (By default, RTA opens the datastore with two index buffers and three data buffers.)

REOPEN [BUFND(n)] [BUFNI(n)]

If, for example, I/O waits are degrading reporter performance, you can reduce the number of physical I/Os required by increasing the number of buffers. For example, to increase the number of data and index buffers to 5 and 7, respectively, enter:

REOPEN BUFND(5) BUFNI(7)

The reporter closes the EPILOG datastore and reopens it with the new number of buffers. This command affects the EPILOG datastore only.

Related Information: Command of: BUFND and BUFNI


BUFND number of data buffers

BUFNI number of index buffers



REPLACEType: EPILOG Keyword

Description: Specifies that the data exported with OBTAIN should overwrite records in an existing output file with the same name.

Note: When REPLACE is used on an output file with DISP=MOD, the exported data is added to the end of the file and the existing data is not overwritten.


REPLACEM or RMATType: EPILOG command.

Description: Used to add, modify, or delete wait reasons from a specified A-matrix. You can only modify or add resource keywords for one wait reason at a time. To change more than one wait reason, you must enter multiple REPLACEM commands.

RMAT A-matrix-ID wait-reason(resource keywords...)

The syntax of the command requires a 1- to 7-character A-matrix name and a valid detail wait reason code:

n If a resource keyword is included with the wait reason code, the wait reason is added to the matrix.

n If the wait reason is already defined in the matrix, the definition is replaced.

n If the wait reason code is entered without a resource keyword, it is deleted from the matrix.

Notice that you can specify multiple resource keywords for a given wait reason. The 3-character IDs which represent all the possible detail wait reason codes can be found at the end of the EXWAIT entry. The resource keywords are listed under Resource Keywords in “Command Groupings” on page 19.

For example,

RMAT MYMAT CPW(RCPU)

associates the resource keyword RCPU with the CPW (waiting for CPU) wait reason in A-matrix MYMAT. (If there was already a definition for the CPW wait reason in MYMAT, it is replaced.) Any existing entries within MYMAT will be left unchanged (except for CPW, which will be completely replaced by the new specification).

Note: You cannot use REPLACEM to modify the only wait reason in a matrix. To get around this, you can either add a temporary wait reason to the matrix and then delete it when you are finished, or delete and create a new matrix with the DELETEM and CREATEM commands.




REPORTIF or RIFType: EPILOG Keyword

Description: Used to specify workload or resource exception filters.

REPORTIF (keyword1(pnnq),keyword2(pnnq) ...)

As indicated in this format statement, REPORTIF supports multiple expressions within the parentheses. These expressions are separated by any of the standard EPILOG delimiters (commas, blanks, and so on), and are logically ANDed together during processing. Multiple RIF expressions on a command are also allowed, and are logically ANDed as well.

Whether REPORTIF is being used for workload or resource exception filtering, the same basic syntax applies:

The differences are in the details, which are significant enough to make separate discussion of workload vs. resource exception filtering worthwhile.

Using REPORTIF for Workload Exception Filtering

keyword Defines the exception filter.

pnnq Sets the quantity at which the exception is reached.

p the comparator to be used

nn the value to be matched or used as a threshold

q units

keyword Defines the workload exception filter. Valid workload exception filters can be:n Elapsed time (ELAPSED or ELAP) for batch jobs, started

tasks, or TSO user sessions.n Response time (RESPONSE or RESP) for performance

groups.n Detail wait reason codes, as defined in the description of

the EXWAIT keyword.n Summary wait categories, as defined in the description of

the SUMWAIT keyword.

pnnq Sets the quantity at which the exception is reached. Note that this expression must be enclosed by parentheses (as shown) or preceded by a blank space.



Using RESPONSE and ELAPSED

The RESPONSE (RESP) and ELAPSED (ELAP) keywords allow you to cd select performance group records by response time, and other workloads (batch jobs, started tasks, and TSO sessions) by elapsed time. These keywords cannot be entered with a percentage operand on DISPLAY; they require a specific time, such as 2S, 30M, or 1H. They can, however, be used with a percentage operand on COMPARE, in which case both the profile record and the workload record are used to make the selection.

Examples: Workload Exception Filtering

For example,

DISPLAY JOB(PAYROLL) STEP RIF(ELAP(>45M)) LASTWEEK

displays only those steps of the PAYROLL jobs last week that ran longer than 45 minutes.

DISPLAY TSO(*) RIF(ELAP(>1H)) LASTWEEK

displays only those TSO sessions that ran longer than 1 hour.

DISPLAY PNAME(SHIFT1) JOB(*) RIF(ELAP(>1H)) LASTWEEK

displays only those batch job profile records with a PNAME (profile name) of SHIFT1 for which the elapsed time exceeded 1 hour.

COMPARE PGN(2) PNAME(SHIFT1) RIF(RESP(>2S)) LWK DAY(WED)

compares workload degradation of performance group 2 last week on Wednesday to the most recent profile record for performance group 2 with PNAME (profile name) SHIFT1. Only those intervals in which the response time of performance group 2 exceeded 2 seconds are selected for comparison.

The following command, in contrast to the previous example, selects for comparison only those intervals in which the response time of the workload is 25% greater than that of the most recent profile record.

COMPARE PGN(2) PNAME(SHIFT1) RIF(RESP(>25%)) LWK

p The comparator to be used. Valid comparators for workload exception filtering are:

> for greater than

< for less than.

nn The value at which the exception is reached, expressed as a decimal number (25, .5, 37.5), for workload exception filtering.

q The units for the exception value. Valid units for workload exception filtering are:

% percent. This is the default.

S seconds

M minutes

H hours



DAY(WED)

REPORTIF can also be used with summary wait categories. For example,

DISPLAY STC(CICS*) YDAY RIF(I/O(>10))

displays degradation data for all started tasks beginning with CICS in which I/O waits accounted for more than 10% of the total degradation; I/O is a summary wait category defined in the default summary wait member of the rhilev.midlev.RKANPAR partitioned dataset.

Using the No Prefix on Detail Wait Reason Codes

If you want to display all periods for which no waits of a certain type are recorded, add the prefix NO to the detail wait reason code. For example,

NOSWI

eliminates degradation caused by Waiting to be swapped in from the display. (SWI is the short name for the detail wait reason code SWAPIN.) The new argument NOSWI is the equivalent of

SWI(<1%)

because EPILOG rounds a wait percentage of less than 1 to 0.

NO is not valid when used with the ELAPSED, RESPONSE, and CPUTIL keywords.

I/O and Enqueue Exceptions

When the detail wait reason code is ACTIVEIO, ENQUEUE, or QUEUEDIO, an additional operand is used to identify the specific device type and number or enqueue type, as shown in the following examples:

DISPLAY PGN(2) RIF(AIO(VOLUME(VSRESA)>5%)) THISWEEK


DISPLAY STC(IMSCNTL) RIF(QIO(ANY >10%)) INTERVAL YDAY


DISPLAY TSO(*) RIF(ENQ(ANY >1S)) INTERVAL TODAY

displays all intervals in which any TSO user session waited for an enqueue more than 1 second. For a complete list of the available I/O and enqueue operands, as well as the list of which operands accept the NO prefix, please see the description of the ACTIVEIO, ENQUEUE, or QUEUEDIO keywords.



Using REPORTIF for Resource Exception Filtering

keyword Defines the resource exception filter. Valid resource exception filters can be found by consulting the Data Dictionary appendix to this manual. In general, you can select using any data value appearing on the resource display panel, except for data values that are selected with other keywords, such as start date, start time, system ID, and so on.

pnnq Sets the quantity at which the exception is reached. Note that this expression must be enclosed by parentheses (as shown in the format statement) or preceded by a blank space.

p The comparator to be used. For resource exception filtering, you can use both character and sign comparators. Valid character comparators are shown below.

GT GE EQ NE LE LTValid sign comparators are shown below.

GT >

GE >= => !< <! ^< <^

EQ = ==

NE != =! <> >< ^= =^

LE < =< !> >! ^> >^

LT <

The following rules apply to comparators.n One or more blank spaces are required to separate a character

comparator from the keyword and value in the expression. Sign comparators do not require blank spaces to separate them from the keyword and value.

n For two-character sign comparators, order is insignificant. (For example, >= is equivalent to =>.)

n Two NOT symbols are supported (^ and !), as well as a special NOT EQUAL symbol ( <> ). In addition, a NOT symbol may be specified with a GREATER THAN or LESS THAN symbol ( !< or ^< ).

n For both character and sign comparators, parentheses are optional. If used, however, the parentheses must be balanced.

nn For resource exception filtering, the matching value or the value at which the exception is reached. This value may be numeric, character, or hexadecimal, and when the value is a character string, masking may be used. Special considerations apply in each case:

n Numeric values



When using numeric values, it is important to be aware that the value in the record is generally of greater precision than the value displayed on the screen. For example, suppose that the value of the field % Dev Busy (Percent Device Busy) on the RDAS report is displayed as 7.2, but the internally stored value is the floating point number 7.2432.... You decide to use the % Dev Busy field to create a RIF filter, using the expression RIF (DPCTBUSY>7.2). (The term DPCTBUSY is the Data Dictionary element name for the indicated field.) Although the displayed value seems to be excluded by the RIF filter, the record will be selected, because the internal value meets the RIF condition.

n Character StringsCharacter strings may be specified in their entirety for exact matches, or may use masks for pattern matching.

An asterisk in the middle of a pattern fixes the length of the matching string, except if there is an asterisk at the end of the pattern.

Examples

OMON* Matches any character string beginning with OMON.

OMON*A Matches any 6-character string beginning with OMON and ending with A.

n Hex Strings

Hex strings are used for device numbers, and can be treated as hex numbers or character strings. They are evaluated numerically if a greater-than or less-than comparator is used, and are treated as character strings if an equal-to or not-equal comparator is specified.

To keep the distinction between hex numbers and character strings, masking of hex strings is allowed only with the EQ and NE. If an asterisk is included in the value of any other comparator, it is flagged as invalid.

q The units for the exception value. For resource exception filtering, units are optional; if no unit is specified, the value is assumed to be in the unit shown on the display panel and documented in the manual. If a unit is specified, it must be compatible with the units of the data element that is selected. For example, if you select the Data Dictionary element PCTCPTCB, you can specify the value as n% or n, with no difference in interpreted meaning.

For time and storage units, you can specify a compatible unit other than that on the display panel, and it will be converted to the correct unit for the test. For example, if the value specified is ordinarily shown in milliseconds, and you specify 1S, the value is automatically scaled to milliseconds for comparison with the value in the record.

Valid time units are:

us microseconds

ms milliseconds

s seconds



Examples: Resource Exception Filtering

For example,

DIS RCPU RIF(PCTCPTCB > 30)

displays all RCPU records in which the %TCB exceeds 30%.

DIS RDAS RIF(VOLSER EQ OMON*)

displays all devices with volsers beginning with OMON.

DIS RDAS RIF(DCUBUSY GE 1S)

displays all devices with a DCUBUSY greater than or equal to 1000. The DCUBUSY value is collected and stored in milliseconds; the value specified was automatically converted from seconds to milliseconds for the comparison.

DIS RDAS RIF(DEVADD >= 0000, DEVADD <= 000F)

treats the value as a hex number, and only those devices between 000 and 00F are included on the RDAS display.

The following command produces the same effect:

DIS RDAS RIF(DEVADD = 00*)

In this case, however, the device address is treated as a character string.

Resource Exception Filtering: Tabular vs. Panel-Oriented Displays

There are two types of EPILOG resource displays: tabular displays and panel-oriented displays. Tabular displays contain columns of data, and the same information is repeated for a list of entries on the panel. The RDAS display is an example of a tabular display.

The RIF test is applied differently to tabular displays and panel-oriented displays.

n For tabular displays, each line of the display is subjected to the RIF test. If the keyword value from the line fails the test, it is omitted from the display. If it passes, it is included. If all panels are suppressed, the EB620 message is issued.

n For panel-oriented displays, if the keyword values from the panel fail the RIF test, the entire panel is suppressed. (This is a standard way to handle RIF processing.) If all panels are suppressed, the EB620 message is issued.

For example, if you enter

DIS RDAS YDAY STIME(9) ETIME(0915) RIF(DPCTBUSY > 30%)

m minutes

h hours

d days

Valid space units are:

b bytes

Kb kilobytes



only devices that were more than 30% busy appear in the output display. If all lines of an RDAS display fail the test, the entire panel is suppressed.

The following is a list of resource displays that have the RIF test applied to the entire display panel.

n RINF

n RPAG

n RSWA

If the RIF test fails, the panel is entirely suppressed.

The following is a list of resource displays that have the RIF test applied to each line of the display.

n RCCH

n RCHN

n RDAS

n RDOM

n RPDS

n RPGN

n RSDS

n RSRM

n RSWR

n RVLF

If the RIF test fails, only the lines that failed the test are suppressed.

There are two resource keywords that do not fall neatly into the category of a tabular or panel-oriented display: RCPU and RLCU. This is because these panels contain both tabular and panel-level data. See the RCPU and RLCU entries for a discussion of RIF processing with these keywords.

Potential Ambiguity with SET

Most exception keywords are unique to a given resource type, but a few, such as VOLSER, DEVADD, and others appear in more than one resource panel. This introduces an ambiguity with the SET command. For example, consider the following command:

SET RIF(VOLSER EQ OMON*)

VOLSER is a valid field on three different resource types: RDAS, RPDS, and RSDS. In cases such as this, the exception filter will act on all resource types for which it is defined.

The Differences between REPORTIF and SELECTIF

Although REPORTIF and SELECTIF both provide exception filtering, they are not interchangeable. These are the differences between them:

n If you want resource exception filtering, you must use REPORTIF. SELECTIF is not compatible with resource keywords.



n If you want workload exception filtering with summary wait categories, you must use REPORTIF. SELECTIF is only available with RESPONSE, ELAPSED, and detail wait reason codes.

n Where you have a choice between REPORTIF and SELECTIF (that is, for workload exception filtering with RESPONSE, ELAPSED, or any of the detail wait reason codes) and are combining data across intervals, you may get different results depending upon whether you have used REPORTIF or SELECTIF. This is because SELECTIF applies its selection filter to single records, and REPORTIF applies its selection filters to combined (averaged or totalled) records.


REPTCLAS or RPCType: EPILOG Keyword

Description: Selects Workload Manager report class task degradation data by task name. The operand for this keyword is 1–8 characters long; it also accepts a wildcard (*) character. This keyword is only valid when the system is running in WLM goal mode. For example,

DISPLAY RPC(TSOREPT) LASTWEEK

obtains report class degradation data for report class TSOREPT last week.

The REPTCLAS keyword is not compatible with the ACCOUNT or CLASS keywords.


When exporting data to SAS, this keyword writes the following elements to the SAS report:

Execution state by report class (SAS dataset RCLDETL): CFRAMES, CLASTYP, CPUSU, DEVADD, EDATE, EDATTIME, EFRAMES, ENQNAME, ETIME, EXTDTIME, IORATE, IOSU, MSOSU, NAME, NUMICMB, NUMTRX, PRODIDX, RCTTIM, RESPUNIT, SDATE, SDATTIME, STIME, SMFID, TRXACT, TRXELAP, TRXEXEC, TRXESP, TRXSYST, VOLSER, WAITNAME, WAITPCT, WAITTIME, WRKNGSET


Related Information: Keyword of: EXTRACT, INQUIRE, DISPLAY, and OBTAIN


RESType: EPILOG Command

Description: See RESOURCE.




RESOURCE or RESType: EPILOG Command

Description: Displays the resource panels associated with the most severe wait reason on the currently displayed degradation screen.

RES [AMATRIX(cccc)] [resource keyword]

These resource panels can be selected in three ways:

1. If you enter the RESOURCE command without an operand, it uses the DEFAULT A-matrix to determine which resources to display.

2. If you enter the name of another A-matrix with the command, it uses that A-matrix to determine the resource panels.

3. If you enter one or more resource keywords (such as RPGN or RCHN), the specified resource panels are displayed.For example, suppose that you have navigated to a detail workload display, such as the one that follows.

FIGURE 1. SINGLE Interval DETAIL Display

In such a case, entering RESOURCE while the display is on the screen is equivalent to using the R navigational command to select resource panels for the Private Page-In Wait wait reason.

RESOURCE has an advantage over R in that you can supply an AMATRIX keyword to override the current default automatic analysis matrix, or specify a resource panel directly:

RESOURCE AMATRIX(A-matrix-ID)

or

RESOURCE RDAS

RESOURCE has the disadvantage that you cannot specify which bottleneck you want to analyze; it always provides resource data for the wait reason with the highest percentage. Of course, you can always use the DISPLAY command to choose exactly which resource panels you want to look at.

+=============================================================================+| Performance Group = 2 Symbolic Name = TSO || From 11:15 To 11:30 On 09/06/99 Elap = 15:00 M SYSA |+-----------------------------------------------------------------------------+|Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0||Using CPU 0.23 S 4.7|-> . . . . . . . . . .|RPrivate Page-In Wait 1.75 S 35.1|--------------> . . . . . . .||Swap Page-In Wait 0.38 S 7.7|--->. . . . . . . . . .|| ||Average Trans Time 4.98 S 865 MVS Transactions Ended ||Productivity Index 10% |+=============================================================================+



If you do not enter a keyword with RESOURCE, the resource panels defined in the current default matrix for the most severe wait reason are displayed.


RESPType: EPILOG Keyword

Description: See RESPONSE.


RESPONSE or RESPType: EPILOG Operand

Description: Selects performance group records by response time. This keyword cannot be entered with a percentage operand on the DISPLAY command; it requires a specific time, such as 2S, 30M, or 1H. It can, however, be used with a percentage operand on COMPARE, in which case both the profile record and the workload record are used to make the selection. For example,

DISPLAY PGN(2) RIF(RESP(>2S)) LASTWEEK

DAYOFWK(WEDNESDAY)

displays only those intervals on Wednesday of last week in which the response time of performance group 2 was greater than 2 seconds. (Presumably, performance group 2 defines a group of online TSO users.)

In contrast to the previous example,

COMPARE PGN(2) PNAME(SHIFT1) RIF(RESP(>25%)) LWK

DAY(WED)

displays only those comparisons in which the response time of the workload is 25% greater than that of the profile.

RESPONSE is a valid exception filter for REPORTIF or SELECTIF.

Related Information: Operand of: REPORTIF and SELECTIF

RIFType: EPILOG Keyword

Description: See REPORTIF.




RINFType: EPILOG Keyword

Description: Generates information about the status of your general system resources. One record is generated for each interval. When OMEGAMON II for MVS is running under MVS/SP™ 5.1 and above, this keyword displays the Workload Manager (WLM) mode (compatibility or goal). If MVS is running in goal mode, the RINF display shows the service policy and the service definition in effect.

Following is a sample panel of MVS in compatibility mode.

Following is a sample panel of MVS in goal mode.

When Exporting Data

When exporting data, RINF writes the following data elements: SYSLEVEL, CPUMODEL, CPUSERL, MODE, IPS, ICS, OPT, RMF, PARTNAME, PARTNUM, NUMPHYS, PARTWGT, PCTCMPLX, PCTMGPLX, INFFLAG, EDATE, EDATTIME, ETIME, EXTDTIME, NUMICMB, SDATE, SDATTIME, STIME, SMFID, WLMMODE, SERVDEF, SERVPOL



Other Resource Keywords: RALL, RCCH, RCHN, RCPU, RDAS, RDOM, RLCU, RPAG, RPDS, RPGN, RSCL, RSDS, RSRM, RSWA, RSWR, RVLF

RLCUType: EPILOG Keyword

Description: Generates information about I/O queueing.

+------------------GENERAL SYSTEM INFORMATION-------------------------------+|FROM: 08:14 TO 08:29 ON 02/22/93 ELAP = 14:58 M SYSA |+---------------------------------------------------------------------------+| MVS SP5.1.0 MODEL=9021 SERIAL=013237 MODE= PARTITIONED || IPS= AA ICS=AA OPT=AA RMF 5.x.x || PARTITION NAME=MVSA PARTITION NUM=1 PHYSICAL PROCESSORS=3 || PROCESSOR WEIGHT=500 PROCESSOR COMPLEX UTILIZATION=267.3 || CPU CAPPING=NO TOTAL LPAR MANAGEMENT OVERHEAD=9.8 || WLM MODE = COMPATIBILITY |+---------------------------------------------------------------------------+

+------------------GENERAL SYSTEM INFORMATION-------------------------------+|FROM: 08:29 TO 08:44 ON 02/22/93 ELAP = 15:00 M SYSA |+---------------------------------------------------------------------------+| MVS SP5.1.0 MODEL=9021 SERIAL=013237 MODE= PARTITIONED || OPT=AA RMF 5.x.x || PARTITION NAME=MVSA PARTITION NUM=1 PHYSICAL PROCESSORS=3 || PROCESSOR WEIGHT=500 PROCESSOR COMPLEX UTILIZATION=236.3 || CPU CAPPING=NO TOTAL LPAR MANAGEMENT OVERHEAD=10.2 || WLM MODE = GOAL SERVICE POLICY = PRIMSHFT || SERVICE DEFINITION = PLRXDRFN |+---------------------------------------------------------------------------+



When Using RLCU with REPORTIF

RLCU panels contain both tabular and panel-level data. A sample RLCU panel follows.

There are two lists in this panel: a list of I/O processors at the top and a list of LCUs at the bottom.

You can specify the I/Os/sec and the Avg # I/O Q from the top, thereby selecting the panel if any of the I/O processors satisfies the condition.

However, suppose that you have specified one REPORTIF condition for the top part of the panel, and another for a field on the bottom part. If the REPORTIF condition pertaining to the upper part of the display panel is met, the panel is displayed, even if no lines meet the criteria. If the top part of the panel fails a REPORTIF test, the entire panel is suppressed.

When Exporting Data

When exporting data, RLCU writes the following data elements: IOPROCID, LCUIOSEC, IOPIOSEC, LCUIOQLN, IOPIOQLN, DLCUID, IOPTLDEF, CPPCTBSY, IODEFSEC, DPCTBSY, CUPCTBSY, CUDEFSEC, CUID, CHPID, LCUTYPE, CHPINSEC, LCUCPST, EDATE, EDATTIME, ETIME, EXTDTIME, LCUERROR, MACHFLAG, NUMICMB, OSLEVEL, SDATE, SDATTIME, STIME, SMFID



Other Resource Keywords: RALL, RCCH, RCHN, RCPU, RDAS, RDOM, RINF, RPAG, RPDS, RPGN, RSCL, RSDS, RSRM, RSWA, RSWR, RVLF

+===================== Logical Control Unit Activity =========================+| From: 9:00 to 9:15 on 03/06/99 Elap =15:00 M SYSA |+-----------------------------------------------------------------------------+| I/O I/Os Avg # || Processor /sec I/O Q || --------- ------ ----- || 00 199.80 .08 || 01 194.84 .05 || || I/Os % All CHPID || /sec Avg # Ch Path % CU Ints || LCU Deferred I/O Q Busy Busy CU CHPID /sec Comment || --- -------- ----- ------- ---- ---- ----- ------ ------------------- || 00C .000 .00 .00 .00 0011 01 .31 || .00 02 .31 || .00 0071 07 .32 || .00 08 .30 || 00F .000 .00 .00 .28 0031 03 1.19 || .60 04 1.28 || .35 0091 09 1.26 || .28 0A 1.19 |+=============================================================================+



RMATType: EPILOG Reporter Command

Description: See REPLACEM.


RNGType: EPILOG Keyword

Description: See RANGE.


RPAGType: EPILOG Keyword

Description: Generates information about paging and storage resource activity. Since one record is generated for each storage area, each interval generates 12 records. If you want to select a specific storage area, use the OBTAIN command with one of the following:

n REPORTIF (STORNAME (=cccbbbbbbbb)), where ccc is the storage name whose character string must be 12 characters long, padded with blanks on the right.

n REPORTIF (STORNAME (=ccc*)), where ccc is the storage name, and is padded with * (wild card) on the right.

When Exporting Data

When exporting data, RPAG writes the following data elements: STORNAME, VIRT, REAL, FIXED, NONFIXED, PAGEIN, PAGEOUT, PAGES, SWAPIN, SWAPOUT, SWAPS, ESINST, ESONLINE, ESFRREAL, ESTOAUX, ESMIN, ESMAX, ESAVG, EDATE, EDATTIME, ETIME, EXTDTIME, MACHFLAG, NUMICMB, SDATE, SDATTIME, STIME, SMFID



Other Resource Keywords: RALL, RCCH, RCHN, RCPU, RDAS, RDOM, RINF, RLCU, RPDS, RPGN, RSCL, RSDS, RSRM, RSWA, RSWR, RVLF

RPDSType: EPILOG Keyword

Description: Generates information about page dataset resource activity. One record is generated for each page dataset on your system.

When Exporting Data

When exporting data, RPDS writes the following data elements: SPCTYPE, DEVADD, VOLSER, DEVTYPE, PCTFULL, PCTINUSE, IOPERSEC, PAGPERIO, TRNSTIME, PDSFLAG, EDATE, EDATTIME, ETIME, EXTDTIME, NUMICMB, SDATE, SDATTIME, STIME, SMFID





Other Resource Keywords: RALL, RCCH, RCHN, RCPU, RDAS, RDOM, RINF, RLCU, RPAG, RPGN, RSCL, RSDS, RSRM, RSWA, RSWR, RVLF

RPGNType: EPILOG Keyword

Description: Generates information about performance group resource activity. One record is generated for each performance group on your system. If a performance group is defined with multiple periods in the IPS, then a separate record is generated for each performance period.

When Exporting Data

When exporting data, RPGN writes the following data elements: PERF, PERIOD, SUPERSEC, ACTRESP, AVGCTRX, SWAPERTX, PCTRES, AVGWKST, AVGTRXIN, TOTSTGK, SRBPCT, TCBPCT, PIOPRSEC, REPTCNTL, PGNFLAG, EDATE, EDATTIME, ETIME, EXTDTIME, NUMICMB, SDATE, SDATTIME, STIME, SMFID



Other Resource Keywords: RALL, RCCH, RCHN, RCPU, RDAS, RDOM, RINF, RLCU, RPAG, RPDS, RSCL, RSDS, RSRM, RSWA, RSWR, RVLF

RSCLType: EPILOG Keyword

Description: Generates information about all the service and report classes with activity, organized by workload. One record is generated for each service and report class. RSCL does not accept operands.

When Exporting Data

When exporting data, RSCL writes the following data elements: POLNAME, POLDESC, POLACTDT, POLACTTM, DEFNAME, DEFDESC, DEFINSDT, DEFINSTM, DEFUSER, CPUCOEFF, IOCOEFF, MSOCOEFF, POLSWTCH, SRBCOEFF, CLASNAME, CLASDESC, WRKLNAME, WRKLDESC, RESGNAME, RESGDESC, RESGMIN, RESGMAX, RSPBKT01, RSPBKT02, RSPBKT03, RSPBKT04, RSPBKT05, RSPBKT06, RSPBKT07, RSPBKT08, RSPBKT09, RSPBKT10, RSPBKT11, RSPBKT12, RSPBKT13, RSPBKT14, PERIODCT, CLASSTYP, PERIODNM, RESPUNIT, GOALTYPE, GOALCHNG, GOALVALU, GOALPVAL, GOALDUR, GOALIMP, AVGRESP, TRANRATE, TRANRUNT, CPUSUS, VELOCITY, RSPBKA01, RSPBKA02, RSPBKA03, RSPBKA04, RSPBKA05, RSPBKA06, RSPBKA07, RSPBKA08, RSPBKA09, RSPBKA10, RSPBKA11, RSPBKA12, RSPBKA13, RSPBKA14, PRCNTTXN, PRCNTRSP, PERFINDX, NUMTRANS, AVGSTOR, CPUADJF, CPUPCT, IOCRATE





Other Resource Keywords: RALL, RCCH, RCHN, RCPU, RDAS, RDOM, RINF, RLCU, RPAG, RPDS, RPGN, RSDS, RSRM, RSWA, RSWR, RVLF

RSDSType: EPILOG Keyword

Descripton: Generates information about swap dataset resource activity. One record is generated for each swap dataset on your system.

When Exporting Data

When exporting data, RSDS writes the following data elements: DEVADD, VOLSER, DEVTYPE, PCTFULL, PCTINUSE, IOPERSEC, TRNSTIME, SDSFLAG, EDATE, EDATTIME, ETIME, EXTDTIME, NUMICMB, SDATE, SDATTIME, SMFID, STIME



Other Resource Keywords: RALL, RCCH, RCHN, RCPU, RDAS, RDOM, RINF, RLCU, RPAG, RPDS, RPGN, RSCL, RSRM, RSWA, RSWR, RVLF

RSRMType: EPILOG Keyword

Description: Generates information about SRM MPL adjustment values. One record is generated for each value of SRMVALS in the interval.

When Exporting Data

When exporting data, RSRM writes the following data elements: SRMVALS, SRCPU, SRUIC, SRASMQ, SRPAGFLT, SRDMDPAG, SRPAGDLY, SRFIXB16, SRFIXTOT, ESMIGRAT, EDATE, EDATTIME, ETIME, EXTDTIME, MACHFLAG, NUMICMB, SDATE, SDATTIME, STIME, SMFID



Other Resource Keywords: RALL, RCCH, RCHN, RCPU, RDAS, RDOM, RINF, RLCU, RPAG, RPDS, RPGN, RSCL, RSDS, RSWA, RSWR, RVLF

RSWAType: EPILOG Keyword

Description: Generates information about swapping activity. One record is generated for each interval.

When Exporting Data

When exporting data, RSWA writes the following data elements: PSWPRSEC, LTPPRSEC, PGPRSWPO, PGPRSWPI, DSWPPHSC, TSWPSEC, LSWPRSEC, ESDSWPSC,



ESTSWPSC, ESASWPSC, DSXAFLAG, EDATE, EDATTIME, ETIME, EXTDTIME, MACHFLAG, NUMICMB, SDATE, SDATTIME, STIME, SMFID



Other Resource Keywords: RALL, RCCH, RCHN, RCPU, RDAS, RDOM, RINF, RLCU, RPAG, RPDS, RPGN, RSCL, RSDS, RSRM, RSWR, RVLF

RSWRType: EPILOG Keyword

Description: Generates information about swap reasons.

When Exporting Data

When exporting data, RSWR writes the following data elements: SWPCATG, PSWPRSEC, DSWPPHSC, TSWPSEC, LSWPRSEC, ESDSWPSC, ESTSWPSC, ESASWPSC, EDATE, EDATTIME, ETIME, EXTDTIME, MACHFLAG, NUMICMB, SDATE, SDATTIME, STIME, SMFID



Other Resource Keywords: RALL, RCCH, RCHN, RCPU, RDAS, RDOM, RINF, RLCU, RPAG, RPDS, RPGN, RSCL, RSDS, RSRM, RSWA, RVLF

RVLFType: EPILOG Keyword

Description: Generates information about VLF class activity. One record is generated for each interval.

When Exporting Data

When exporting data, RVLF writes the following data elements: VLFCLASS, VLFVSUSD, VLFMXSTG, VLFLRGST, VLFADDS, VLFDELES, VLFTRIMS, VLFRATE, VLFHITS, VLFFULL



Other Resource Keywords: RALL, RCCH, RCHN, RCPU, RDAS, RDOM, RINF, RLCU, RPAG, RPDS, RPGN, RSCL, RSDS, RSRM, RSWA, RSWR

S Commands and Keywords 185

S Commands and Keywords


S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187SCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187SDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187SELECTIF or SIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187SERVCLAS or SCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190SETP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191SHORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193SIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193SINGLE or SNG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194SNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194STARTDATE or SDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194STARTTIME or STIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196STARTTSK or STC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197STC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198STEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198STIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199SUM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199SUMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199SUMDEF or SUMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200SUMMARY or SUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201SUMW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202SUMWAIT or SUMW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202SYM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204SYMBOLIC or SYM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

17


SYSID or SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205SYSTEM or SYS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208




SType: EPILOG Navigational Command

Description: Navigates you from the Combined display to the Single display.

Related Information: Other Fast Path Navigation Commands: D, J, P, R, V, W, and X

SCLType: EPILOG Keyword

Description: See SERVCLAS.


SDATEType: EPILOG Keyword

Description: See STARTDATE.


SELECTIF or SIFType: EPILOG Keyword

Description: Used to specify workload exception filters.

SELECTIF (keyword1(pnnq),keyword2(pnnq) ...)

SELECTIF will select an individual record from an EDS if it meets the selection criteria. As indicated in this format statement, SELECTIF supports multiple expressions within the parentheses. These expressions are separated by any of the standard EPILOG delimiters (commas, blanks, and so on), and are logically ANDed together during processing. Multiple SIF expressions on a command are also allowed, and are logically ANDed as well.

keyword Defines the workload exception filter. Valid workload exception filters can be:

n Elapsed time (ELAPSED or ELAP) for batch jobs, started tasks, or TSO user sessions.

n Response time (RESPONSE or RESP) for performance groups.n Detail wait reason codes, as defined in the description of the EXWAIT

keyword.



Using RESPONSE and ELAPSED

The RESPONSE (RESP) and ELAPSED (ELAP) keywords allow you to select performance group records by response time, and other workloads (batch jobs, started tasks, and TSO sessions) by elapsed time. These keywords cannot be entered with a percentage operand; they require a specific time, such as 2S, 30M, or 1H.

Examples

To display all intervals today where performance group 2 first-period response time was greater than 1 second, enter:

DISPLAY PGN(2) PGP(1) TODAY SIF(RESPONSE(>1S))

To display all those intervals where response time was greater than .5 seconds and private page-in waits made up greater than 30% of the average transaction wait time, enter:

DISPLAY PGN(2) PGP(1) TODAY SIF(RESP(>.5S) PAG(>30%))

To display degradation data for all jobs run last week with elapsed time greater than 30 minutes, enter:

DISPLAY JOB(*) LASTWEEK SIF(ELAP(>30M))

To display degradation data for all runs of the ARUPDATE job last month in which the elapsed time was greater than 30 minutes, enter:

DISPLAY JOB(ARUPDATE) LASTMONTH SIF(ELAP(>30M))

To display degradation data for all TSO sessions yesterday which were longer than 1 hour, enter:

DISPLAY TSO(*) YESTERDAY SIF(ELAP(>1H))

To display degradation data for all started tasks beginning with CICS™ in which CPU waits accounted for more than 5% of the total degradation, enter:

DISPLAY STC(CICS*) YESTERDAY SIF(CPW(>5))

pnnq Sets the quantity at which the exception is reached. Note that this expression must be enclosed by parentheses (as shown) or preceded by a blank space.

p The comparator to be used. Valid comparators for workload exception filtering are:

> for greater than

< for less than.

nn The value at which the exception is reached, expressed as a decimal number (25, .5, 37.5), for workload exception filtering.

q The units for the exception value. Valid units for workload exception filtering are:

% percent. This is the default.

S seconds

M minutes

H hours



To display only those intervals on Wednesday of last week in which the response time of performance group 2 (presumably, a group of online TSO users) was greater than 2 seconds, enter:

DISPLAY PGN(2) SIF(RESP(>2S)) LASTWEEK

DAYOFWK(WEDNESDAY)

Using the No Prefix on Detail Wait Reason Codes

If you want to display all periods for which no waits of a certain type are recorded, add the prefix NO to the detail wait reason code. For example,

NOSWI

eliminates degradation caused by Waiting to be swapped in from the display. (SWI is the short name for the detail wait reason code SWAPIN.) The new argument NOSWI is the equivalent of

SWI(<1%)

because EPILOG rounds a wait percentage of less than 1 to 0. NO is not valid when used with the ELAPSED, RESPONSE, and CPUTIL keywords.

I/O and Enqueue Exceptions

When the detail wait reason code is ACTIVEIO, ENQUEUE, or QUEUEDIO, an additional operand is used to identify the specific device type and address or enqueue type, as shown in the following examples:

DISPLAY PGN(2) SIF(AIO(VOLUME(VSRESA)>5%)) THISWEEK


DISPLAY STC(IMSCNTL) SIF(QIO(ANY >10%)) INTERVAL YDAY


DISPLAY TSO(*) SIF(ENQ(ANY >1S)) INTERVAL TODAY

displays all intervals in which any TSO user session waited for an enqueue more than 1 second. For a complete list of the available I/O and enqueue operands, as well as the list of which operands accept the NO prefix, please see the description of the ACTIVEIO, ENQUEUE, or QUEUEDIO keywords.

Related Infomation: Keyword of: DISPLAY, EXTRACT, OBTAIN, PROFILE, and SET

SERVCLAS or SCLType: EPILOG Keyword

Description: Selects Workload Manager service class task degradation data by task name. The operand for this keyword is 1&ndash.8 characters long; it also accepts a wildcard (*) character.

This keyword is only valid when the system is running in WLM goal mode. The SERVCLAS keyword is not compatible with the ACCOUNT or CLASS keywords. For example,



DISPLAY SCL(TSOSERV) LASTWEEK

obtains service class degradation data for service class TSOSERV last week.



Execution state by service class (SAS dataset SCLDETL): CFRAMES, CLASTYP, CPUSUS DEVADD EDATE, EDATTIME, EFRAMES, ETIME, ENQNAME, EXTDTIME GOALDUR, GOALIMP, GOALPVAL, GOALRTU, GOALTYPE, GOALVALU, IORATE, IOSU, MSOSU, NAME, NUMTRX, NUMICMB, PERIOD, PRODIDX, RCTTIM, RESPUNIT, SDATE, SDATTIME, STIME, SMFID, TOTVEL, TRXACT, TRXELAP, TRXRESP, TRXEXEC, VELOCITY, VOLSER, WAITNAME, WAITPCT, WAITTIME, WRKNGSET


Related Information: Keyword of: EXTRACT, INQUIRE, DISPLAY, and OBTAIN


SETType: EPILOG Reporter Command

Description: Establishes default settings for subsequent DISPLAY or OBTAIN commands.

SET [time period] -

[display and reporting options] -

[CLEAR] -

[REPORTIF|SELECTIF(filter1,filter2,...)]

When using the DISPLAY or OBTAIN command, you will often find that you are entering the same set of options (such as start/end date and time) over and over. To reduce the amount of typing required, the SET command allows you to establish defaults for certain keywords. For example, if you intended to issue a series of commands targeted at yesterday from 9:00 AM to 5:00 PM, you might want to issue the following SET command first:

SET YESTERDAY STIME(9) ETIME(17)

From now on, anytime you issue a command, EPILOG will assume you have also entered the clause YESTERDAY STIME(9) ETIME(17). If you enter another time or date frame with a given command, the specified keywords override the default settings for that command.

The current default settings can be viewed at any time by entering the SET command without any keywords. Adding the keyword CLEAR clears all default settings (as if the reporter session had been stopped and another session started.)

To Set Defaults for DISPLAY

When SET is used to set defaults for DISPLAY, the keywords that can be SET fall into three categories:

n date and time keywords; for a list of these keywords, see Date and Time Keywords in “Command Groupings” on page 19.

n the REPORTIF or SELECTIF filtering keywords; and



n the following display and batch reporting options keywords: AMATRIX, AUTOMATIC, LIMIT, LOGOFF, LOGON, NOPRODIDX, PLOTMIN, PRDXDEF, PRODIDX, SHORT, SUMDEF, SUMWAIT, SYSID, TITLE, TITLE2, TITLE3, TWAITOFF, and TWAITON.

The following keywords cannot be used with SET: AVERAGE, COMBINE, DETAIL, XPG, STEP, SUMMARY, TOTAL, workload identifiers (PGN, JOB, and so on), and resource keywords (RCPU, RINF, and so on).

Note: When multiple SET commands are issued with certain keywords, such as SYSID or TITLE, the operands are appended. For example, if you enter

SET SYSID (SYSA)

SET SYSID (SYSB)

the result is:

SET SYSID (SYSA, SYSB)

To Set Defaults for OBTAIN

When SET is used to set defaults for OBTAIN, the list of available keywords expands to include APPEND, ELEMENTS, FORMAT, OUTFILE, and REPLACE. All of the keywords that are valid with SET as a preliminary for DISPLAY are valid with SET as a preliminary for OBTAIN. As usual, the following keywords cannot be used with SET: AVERAGE, COMBINE, DETAIL, XPG, STEP, SUMMARY, TOTAL, workload identifiers (PGN, JOB, and so on), and resource keywords (RCPU, RINF, and so on).

Related Information: Command of: See Date and Time Keywords in “Command Groupings” on page 19. Also: AMATRIX, APPEND, AUTOMATIC, CLEAR, ELEMENTS, FORMAT, LIMIT, LOGOFF, LOGON, NOPRODIDX, OUTFILE, PLOTMIN, PRDXDEF, PRODIDX, REPLACE, REPORTIF, SELECTIF, SHORT, SUMDEF, SUMWAIT, SYSID, TITLE, TITLE2, TITLE3, TWAITOFF, and TWAITON.


SETPType: EPILOG Reporter Command

Description: Establishes a default workload, time period, and/or SYSID value for subsequent COMPARE commands. The COMPARE (or COMPEXT) command then uses this value to select the profile from the profile datastore (PRDS). These defaults remain in effect until changed by a subsequent SETP command or cancelled by SETP CLEAR.

SETP workload -

time period -

SYSID(cccc,...) -

CLEAR



Notes:

n SETP is required when the profile you want for the comparison has a workload name, time period, or SYSID different from the most current profile for PROFNAME on the COMPARE command.

n Until cancelled by SETP CLEAR, values established by SETP commands are combined to create a cumulative default value. However, when you specify a workload value of any type with a SETP command, it replaces any workload previously established. Similarly, a time period value specified on a SETP command replaces a duplicate type established by a previous SETP command.

For example, PGN(2) STIME(0900) ETIME(1700) established with one SETP command would be combined with SDATE(6/1) EDATE(6/30) established with another. However, PGN(12) established with a subsequent SETP command would replace the previously set workload default value PGN(2). Similarly, STIME(1200) established with a subsequent SETP command would replace the previously set time period default value STIME(0900).

For example:

SETP SDATE(04/01/99) EDATE(04/30/99)

specifies the time period for the profile to be used in the comparison. As a result, the profile must include degradation data from April 1st to April 30th inclusive, or for any time period between those dates.

Using SETP with COMPARE

The following example shows how SETP and COMPARE interact to select a profile.

SETP JOB(DEV0) -

LASTMONTH

COMPARE JOB(DEV12) -

workload Identifies the batch job or performance group that should be used in selecting the profile for a comparison. Use any of the workload keywords, listed under Workload Keywords in “Command Groupings” on page 19, except STEP and INTERVAL. You may not specify multiple workloads.

time period Specifies the date and/or time interval of the profile to be used in the comparison. This date does not refer to the date on which you created the profile, but rather to the time period covered by the profile. Use any of the date/time keywords as listed under Date and Time Keywords in “Command Groupings” on page 19.

SYSID(cccc,...) Specifies the SMF System ID that should be used to select the profile(s) for a comparison. You may specify multiple SYSIDs, for example (SYSA,SYSB), to select a profile for each SMF ID.

CLEAR This keyword cancels previously established SETP defaults.



PNAME(DEVBATCH) -

TODAY -

RIF(ELAPSED(>10%))

The SETP command specifies the workload and time period for the profile to be used in the comparison. As a result, the COMPARE command generates a report comparing the historical datastore records for DEV12 jobs run today and that have elapsed times which exceed the profile’s by 10%. The basis of comparison is the most current profile with the name DEVBATCH that was created for DEV0 jobs run last month.

The following example shows how the various selection criteria specified on SETP and COMPARE are used.

SETP SYSID(SYSA,SYSB) -

LASTMONTH

COMPARE JOB(DEV0) -

PNAME(DEVBATCH) -

TODAY -

RIF(ELAPSED(>10%))

The SYSIDs (SYSA and SYSB) and the time period (LASTMONTH) specified on the SETP command are the defaults that the COMPARE command uses to mselect the profiles for the comparison. The selection criteria specified in the COMPARE command (TODAY and RIF) are applied to the workload.

As a result, this COMPARE command generates a report comparing the historical datastore records for DEV0 jobs run today, with elapsed times that exceed the profile’s by 10%, against the most current profiles for either SYSA or SYSB with the name DEVBATCH that were created for DEV0 jobs run during the previous month.


SHORTType: EPILOG Keyword

Description: Indicates that the report title block should be in a condensed format.

Related Information: Keyword of: DISPLAY, EXTRACT, INQUIRE, OBTAIN, SET, and SETP


SIFType: EPILOG Keyword

Description: See SELECTIF.




SINGLE or SNGType: EPILOG Keyword

Description: Allows you to display performance group and resource data for individual RMF intervals. (This is the default.) The SINGLE and COMBINE keywords are mutually exclusive. See COMBINE.


SNGType: EPILOG Keyword

Description: See SINGLE.


STARTDATE or SDATEType: EPILOG Keyword

Description: Specifies the start date of the display. If no STARTDATE is specified, data is displayed from the first record in the database. Dates can be entered in either of two formats:

n Julian

n Gregorian


For example,

DISPLAY... SDATE(99011) STIME(0900) -

EDATE(99018) ETIME(1700) RANGE

displays data from 9:00 AM on January 11, 1999 until 5:00 PM on January 18, 1999.

Using Relative Dates and Times

You can specify relative dates and times by including a plus sign (+) or a minus sign (-) before the expression to be evaluated. For example, to enter a start date thirty days prior to the current date, enter:

STARTDATE(-30)


mmddyy

mm/dd/yy (assume the current year)

mm/dd (assume the current month and year)



Each unit within a time or date expression can be independently assigned a relative value. For example:

STARTDATE(-1/+1)

specifies a start date one month prior to tomorrow. (The -1 in the month position means subtract 1 from the current month; the +1 in the day position means add one to the current day.)

If no sign is entered before a unit, it is assumed to be absolute rather than relative. For example:

STARTDATE(-1/15)

specifies a start date of the 15th day of the previous month.

If a relative value in one unit causes a change in another unit, that change “wraps around” and increments (or decrements) the second unit accordingly. For example, if you entered this start date on March 15:

STARTDATE(-1/-15)

the resulting start date would be January 31. The month is evaluated first and decremented to February. The date is evaluated next and comes out to zero. Since zero is below the range of valid dates (1 - 31), the month is decremented again (to January), and the date is set at the last day in January. If you had entered:

STARTDATE(-1/-16)

the resulting start date would be January 30. This wrap-around feature only takes place between units entered in the same keyword; an excessively high (or low) value in STARTTIME will not increment (or decrement) any values in the STARTDATE keyword, nor vice versa.

Guidelines for Using Relative Dates and Times

n Relative date values are evaluated in the following order: year, month, day. Relative time values are evaluated in hour, minute, second order.

n A value is considered absolute if it is not preceded by a plus or minus sign.

n A +0 or -0 entry defaults to the current value (current day, current hour, and so on). If you enter a 0 that is not preceded by a plus or minus sign, it is interpreted as an absolute value.

n Values entered must be valid for the unit they represent. The valid values are:

Years 1 - 99

Months 1 - 12

Days 1 - 31

Hours 0 - 23

Minutes 0 - 59

Seconds 0 - 59



n Values entered in the same keyword will “wrap around” if they are found to be outside allowed boundaries. The wrap-around feature does not apply to values entered in different keywords.



STARTTIME or STIMEType: EPILOG Keyword

Description: Specifies the start time of the display. If no STARTTIME is specified, data is displayed from the first record on the specified STARTDATE. (If no STARTDATE is specified, data is displayed from the first record in the database.) Times must be entered in 24-hour format (that is, 1300 instead of 1:00 PM), and can be abbreviated as follows:

For example,

DISPLAY... SDATE(99011) STIME(0900) -

EDATE(99018) ETIME(1700) RANGE

displays data from 9:00 AM on January 11, 1999 until 5:00 PM on January 18, 1999.

Using Relative Dates and Times

You can specify relative dates and times by including a plus sign (+) or a minus sign (-) before the expression to be evaluated. An entry of +0 or -0 defaults to the current value. For example:

STARTTIME(+0:+15)

specifies a start time of fifteen minutes after the current hour. If the sign is omitted before the zero, it is interpreted as an absolute value. For example:

STARTTIME(-1:00)

specifies a start time of one hour (on the hour) before the current hour. If this command were entered at 10:45 AM, the start time would be 9:00 AM.

h One-digit hour without a leading zero

hh Two-digit hour

hmm or h:mm Hours and minutes without a leading zero

hhmm or hh:mm Hours and minutes

hhmmss or hh:mm:ss Hours, minutes, and seconds



Guidelines for Using Relative Dates and Times

n Relative date values are evaluated in the following order: year, month, day. Relative time values are evaluated in hour, minute, second order.

n A value is considered absolute if it is not preceded by a plus or minus sign.

n A +0 or -0 entry defaults to the current value (current day, current hour, and so on). If you enter a 0 that is not preceded by a plus or minus sign, it is interpreted as an absolute value.

n Values entered must be valid for the unit they represent. The valid values are:

n Values entered in the same keyword will “wrap around” if they are found to be outside allowed boundaries. The wrap-around feature does not apply to values entered in different keywords.



STARTTSK or STCType: EPILOG Keyword

Description: Selects started task degradation data by task name. The task name can be further qualified by JES number.

The operand for this keyword is 1-8 characters long; it also accepts a wildcard (*) character. The STARTTSK keyword is not compatible with the ACCOUNT or CLASS keywords. For example,

DISPLAY STC(IMSCNTL) LASTWEEK

displays degradation data for started task IMSCNTL last week. A separate display panel is generated for each time the task was started and stopped. If the task consists of multiple steps, all steps are combined into a single display panel.

The following example shows how to qualify the task name using the JES started task number.

DISPLAY STC(IMSCNTL(S3156)) STEP

Years 1 - 99

Months 1 - 12

Days 1 - 31

Hours 0 - 23

Minutes 0 - 59

Seconds 0 - 59



This command displays degradation data for the run of started task IMSCNTL with JES number 3156. Notice that the JES number follows the task name and is prefixed with an S.


When exporting data to SAS, this keyword writes the following elements to the respective SAS report:






STCType: EPILOG Keyword

Description: See STARTTSK.


STEPType: EPILOG Keyword

Description: Specifies that the data should be displayed for individual steps rather than for the complete job or task. (That is, a separate display panel is generated for each job or task step that meets the criteria.) The STEP keyword may not be used for combined displays or for workload profile displays; that is, with COMBINE or PNAME. For example,

DISPLAY TSO(USER01) YDAY STIME(13) ETIME(14) STEP



produces the following batch job step level display.



STIMEType: EPILOG Keyword

Description: See STARTTIME.


STOPType: EPILOG Reporter Command

Description: See END.


SUMType: EPILOG Keyword

Description: See SUMMARY.

Relateted Information: None

SUMDType: EPILOG Keyword

Description: See SUMDEF.


+=============================================================================+ | Job = USER01 JES Number = 3273 Program = IMASPZAP | | Job Class = F Acct No = Operations | | Step = S14X Procstep = ZAPSTEP Step Number = 2 | | From 13:54 To 13:54 On 08/01/99 Elap = 25.73 S SYSA | +-----------------------------------------------------------------------------+ |Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0| |Using CPU 0.54 S 2.1|. . . . . . . . . . .| |Waiting For CPU 12.61 S 49.0|------------=======>. . . . . .| |Disk SYSA24 322 Act 7.56 S 29.4|----------->. . . . . . . .| |Waiting For MVS Lock 2.52 S 9.8|--->. . . . . . . . . .| |ECB Wait 2.52 S 9.8|--->. . . . . . . . . .| |Job Step Elapsed Time 25.73 S | |Productivity Index 30% | +=============================================================================+



SUMDEF or SUMDType: EPILOG Keyword

Description: Specifies a summary wait definition member of rhilev.midlev.RKANPAR. (The summary wait definitions are used to group detail wait reasons into summary wait categories, and the member is invoked when the SUMWAIT keyword is used or a summary wait category is used with REPORTIF.) By default, SUMWAIT displays use the KEPDEFS member of rhilev.midlev.RKANPAR; the SUMDEF keyword allows you to specify another member.

For example, if you copied KEPDEFS to a member called MYSUMS in rhilev.midlev.RKANPAR, and then modified the summary wait definitions in it with an external editor, you would invoke it during a &r. session by issuing the following command:

SET SUMDEF(MYSUMS)

The definitions in MYSUMS would then be used any time the SUMWAIT keyword was used.

To reset the definitions back to the defaults, simply enter:

SET SUMDEF(KEPDEFS)

The operand for SUMDEF is 1–7 characters long.

Note that you must use an external editor (such as ISPF EDIT or TSO EDIT) to copy and modify the KEPDEFS member. When you do so, please observe the following guidelines:

n Each definition associates a detail wait reason code with a summary wait reason. Valid detail wait reason codes appear in “Command Groupings” on page 19 as Wait Reason Codes, Detail.

n Both the detail wait reason code and the summary wait category must be enclosed in single quotes. (The equal sign between them is optional.)

n Each summary wait category consists of a long and short definition. The long definition is used on workload degradation displays, and can be up to 20 characters in length. The short form is recognized by the REPORTIF exception keyword and used to construct the XPG display, and is 4 characters long. (If you do not define a short form for a summary wait category, then the first 4 characters of the wait reason name are used to construct the short form.) We recommend that you define short forms for each summary wait category to avoid confusion.

n You must be careful in naming the summary wait category so that the short form (whether explicitly specified or derived from the first four characters of the full name) does not match any of the detail wait reason codes. If a short form matches a detail wait reason code, this creates an ambiguity for the command parser when the term is used with the REPORTIF keyword.

The only exception to this occurs when only one detail wait reason code is defined for a summary wait category. This is the case with the CPUTIL summary wait category, which consists only of the Waiting for CPU (CPU) detail wait reason.

You invoke the new definitions with the SET command. For example, if you copied KEPDEFS to a member called MYSUMS in rhilev.midlev.RKANPAR, and then modified the summary wait definitions in it, you would invoke it during a reporter session by issuing the following command:



SET SUMDEF(MYSUMS)

The definitions in MYSUMS would then be used anytime the SUMWAIT keyword was used.

To reset the definitions back to the defaults, simply enter:

SET SUMDEF(KEPDEFS)



SUMMARY or SUMType: EPILOG Keyword

Description: Displays only the most important wait reason for each interval, job, or step. The following display is an example of a summary display for performance group 2, showing the most important wait reason for each interval:

Only the most important wait reason for each interval (Swap Page-In for the first interval) is shown in the summary display.

Notice that the arrows in the summary display consist of asterisks and hyphens. The total length of the line represents the average transaction time for that interval. The segment of the line depicted with asterisks indicates the average time spent on that wait reason for the interval.

For example, consider the interval from 3:00 to 3:15. The total length of the arrow in the summary display is 0.37 seconds, the average transaction time for that interval. The segment of the line represented with asterisks is 0.11 seconds, meaning that transactions spent an average of 0.11 seconds waiting for swap page-ins during that interval.

The rules for summary job and step level displays are summarized as follows.

n If you specify a JOBNAME, the summary display shows the main wait reason for each run of the specified job. If you add the STEP keyword, it shows the main wait reason for each step of each run of the job.

+=============================================================================+ | Performance Group = 2 Symbolic Name = DEV TSO | | From 03:00 To 04:41 On 08/07/99 | +-----------------------------------------------------------------------------+ |DATE__START_END___MAIN_REASON(*)_TIME(-)|0S____0.2____0.4____0.6____0.8_____1| |08/07 03:00 03:15 Swap Page-In 0.37 S|****--------> . . . .| | 03:15 03:30 Using CPU 0.20 S|***--->. . . . .| | 03:30 03:45 Wait For Lock 0.18 S|**---> . . . . .| | 03:45 04:00 Term Out Wait 0.31 S|****------> . . . .| | 04:00 04:15 Detected Wait 0.53 S|***--------------> . . .| | 04:15 04:30 ECB Wait 0.31 S|***-------> . . . .| | 04:30 04:41 ECB Wait 1.23 S|************---------------------->+| |---------------------------------------- | |Average For This Workload Display 0.45 S | |Productivity Index 20% | +=============================================================================+



n If you do not specify JOBNAME and use the ACCOUNT, PROGRAM, or CLASS keyword, the summary display shows the main wait reason for each job step that meets the selection criteria established by the other keywords in the command.

Related Information: Keyword of: COMPARE, COMPEXT, DISPLAY, EXTRACT, INQUIRE, OBTAIN, and SET


SUMWType: EPILOG Keyword

Description: See SUMWAIT.


SUMWAIT or SUMWType: EPILOG Keyword

Description: Summarizes the display by grouping similar wait reasons together into summary wait categories. This keyword considerably simplifies the display, and allows you to focus in quickly on the main sources of the problem without having to read through a large number of wait reasons. For example,

DISPLAY JOB(APL17PTF) YESTERDAY SUMWAIT

produces the following degradation display with summary wait categories:

The productivity index shown on the SUMWAIT display is based upon detailed wait reasons, not summary categories. (This is because summary categories are groups of detailed wait reasons, and each category is potentially a mixture of productive, unproductive, and idle execution states.)

The grouping of detailed wait reasons into summary categories is controlled by a list of summary wait definitions in a member of the rhilev.midlev.RKANPAR partitioned dataset. For

+-----------------------------------------------------------------------------+ | Job = APL17PTF JES Number = 2990 Job Steps = 1 / 1 | | Job Class = A Account Number = DCSP07 Input Queue = 14.36 S | | From 11:36 To 11:38 On 07/01/99 Elap = 2:11 M SYSA | +-----------------------------------------------------------------------------+ |Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0| |CPU Used 5.11 S 3.9|-> . . . . . . . . . .| |CPU Wait 1:01 M 47.2|------------======> . . . . . .| |I/O 12.80 S 17.3|------> . . . . . . . . .| |Page + Swap 13.77 S 10.5|----> . . . . . . . . .| |SRM Delay(MPL) 13.77 S 10.5|----> . . . . . . . . .| |Misc Event 13.64 S 10.3|----> . . . . . . . . .| |Job Elapsed Time 2:11 M | |Productivity Index 21% | +-----------------------------------------------------------------------------+



further information about this dataset, see the OMEGAMON II for MVS Configuration and Customization Guide. The default summary wait categories are listed at the end of this entry.

When you invoke the reporter, the default member (named KEPDEFS) is used to provide summary category definitions. You can override these definitions by creating a member in rhilev.midlev.RKANPAR with your own summary wait definitions, and then invoking it with the SET command using the SUMDEF keyword. For more information, see SUMDEF.

Default Summary Wait Categories

CPU USED Using CPU

CPU WAIT Waiting for CPU

ENQUEUE Waiting for an enqueue

HSM Waiting for a dataset backup

Waiting for a C/I locate

Waiting for a dataset deletion

Waiting for an HLIST user command

Waiting for a dataset migration

Waiting for a control dataset record

Waiting for a dataset recall

Waiting for backup dataset recovery

I/O Active on an I/O device

Waiting for a logical channel

Queued on an I/O device

Waiting for a reserved I/O device

JES Waiting for a job cancellation

Waiting for a job deletion

Waiting for a queued job status request

Waiting for a job requeue request

Waiting for a queued SYSOUT request

MISC EVENT ECB waits with STIMER TASK or REAL pending

Voluntary waits

Waiting to acquire an MVS lock

SRM delay to meet the response time objective

Waiting for a mass storage volume to be staged

Waiting for a STIMER to end

OPER ACT Waiting for a disk mount operation

Waiting for a tape mount operation

Swapped with WTOR pending





SYMType: EPILOG Keyword

Description: See SYMBOLIC.


SYMBOLIC or SYMType: EPILOG Keyword

Description: Selects degradation data for a performance group by user-defined symbolic name. The operand for this keyword is 1-8 characters long; it also accepts a wildcard (*) character. If you assigned symbolic names to performance groups during collector startup, you can use the SYMBOLIC (or SYM) keyword to refer to groups by their symbolic names now. Symbolic performance group names are assigned during customization. For a detailed explanation, see the OMEGAMON II for MVS Configuration and Customization Guide. In the following example, the user has previously assigned the symbolic names PRODTSO and REGBATCH to two different performance groups.

PAGE + SWAP Waiting for a PLPA or common page-in

Waiting for a private page-in

Waiting to be swapped in

SRM DELAY(MPL) Waiting for SRM to allow a swap

SWAP Auxiliary storage shortage swaps

Detected wait swaps

Enqueue exchange swaps

Exchange swaps

User-requested long wait swaps

Real storage shortage swaps

Requested swaps

Terminal output wait swaps

Transition swaps

Unilateral swaps

Out Too Long swaps

Central Storage swaps

System Paging swaps

APPC Wait swaps

TERM IN Waiting for terminal input



DISPLAY SYMBOLIC(PRODTSO)

DISPLAY SYM(REGBATCH)

The SYMBOLIC keyword is not compatible with the PGPERIOD keyword.









SYSType: EPILOG Keyword

Description: See SYSID.


SYSType: EPILOG Keyword

Desciption: See SYSTEM.


SYSID or SYSType: EPILOG Keyword

Description: Combines data from selected systems by SMF ID into as little as one display panel per interval. The SYSID keyword allows you to control the way that multiple-system



data is displayed. If your active datastore list defines multiple datasets for multiple systems, and you issue a DISPLAY command, one panel is generated for each system per recording interval. You can use the SYSID keyword to limit the number of systems that will be included in the displays, thereby reducing the number of panels by interval.

The operand for this keyword is at least one 1-to 4- character SMF system ID. MERGE is an optional additional operand. For example,

SYSID(SYSA,SYSB)

produces one panel per interval for systems A and B, while excluding data from other systems.

To merge data from different systems into one RDAS display per interval, use the MERGE operand. For example,

SYSID(MERGE,SYSA,SYSB)

produces one DASD device activity display per interval for systems A and B.

In a multi-system configuration, performance problems can result from contention across multiple systems for shared-DASD devices. To help you detect the cross-system impact of shared-DASD usage, EPILOG allows you to combine DASD activity information from multiple datastores into a single shared-DASD display.

The MERGE keyword allows you to merge DASD historical data into a single display panel showing shared-DASD activity across multiple systems. This feature is available when you use the DISPLAY command with the RDAS keyword.

If you issue the DISPLAY RDAS command, the SYSID keyword allows the following syntax:

The MERGE operand can be placed anywhere among a number of SYSIDs and will apply to all the SYSIDs enclosed in the same pair of parentheses.

For example:

DISPLAY RDAS STIME(10) ETIME(1015) SYSID(MERGE) YDAY

SYSID (MERGE)

Show one RDAS panel per reporting interval, with one detail line for each system being monitored.

SYSID (MERGE SYSA SYSB SYSC)

Combine systems A, B, and C into one display panel; exclude the other systems.

SYSID ((MERGE, SYSA, SYSB), (SYSC, SYSD, MERGE) SYSE)

Generate three RDAS panels; one combines SYSA and SYSB; the second combines SYSC and SYSD; and the third shows SYSE.



merges SYSA and SYSF records together in this RDAS display in a multi-system environment.

The MERGE keyword has merged data from two systems into one panel per interval. This display panel shows that volumes CHKPT1, COM001, and COM002 are shared between the two systems.

The MERGE function does not merge across different MVS environments equally.

If you attempt to merge across MVS/XA and MVS/ESA™ environments, the merge is performed, but there is a change in the RDAS screen. The column header for the last column in the RDAS display, which is Open Dsns for MVS/XA systems and Avg Allocs for MVS/ESA systems, is changed to Open Allcs, indicating a merge between the two kinds of information. The detail lines in the RDAS display show either open dataset names or average allocations in this column, depending on the type of environment.

There is a potential problem when data from two systems with unequal collection intervals is displayed together. In multi-system reporting, the sampling intervals used to collect the data (usually RMF-based) must be the same for both systems. When an interval cannot be merged, the following message is displayed in the panel header, and the interval search proceeds to completion:

This display is incomplete because of incompatible RMF intervals

You can overcome the interval time tolerance limit by using the COMBINE keyword. For example, if you add the keyword COMBINE(1H) to the MERGE command, all intervals with a starting time within the one hour reporting interval will be merged.

For more information about shared-DASD contention, see JDAS and PDAS.

Related Information: Keyword of: COMPARE, COMPEXT, DISPLAY, EXTRACT, INQUIRE, OBTAIN, PROFILE, SET, and SETP


+========================== DASD Device Activity =============================+| From: 10:00 to 10:15 on 10/18/99 Elap = 14:59 M || Sysid: SYSA SYSF || Merge of 2 Intervals |+-----------------------------------------------------------------------------+|Volume SMF Dev I/O -------- Time in Milliseconds -------- % Dev Avg||Serial id # LCU Rate Total = IOSQ+Pend+Conn+Disc CUB DB Util Allcs||------ ---- --- --- ---- ----- ---- ---- ---- ---- ---- ---- ----- -----||CHKPT1 SYSA 150 00C 1.2 43 0 22 7 14 21.9 17.7 1.0|| SYSF 150 00A 1.0 29 0 10 6 13 9.9 17.4 1.0||COM001 SYSA D89 055 6.5 10 1 2 5 2 .2 1.1 5.0 339.5|| SYSF D89 056 3.2 10 1 2 4 3 .1 1.3 2.6 267.1||COM002 SYSA D8A 055 1.3 17 1 2 6 8 .2 1.7 2.7 483.1|| SYSF D8A 056 .6 15 0 3 6 6 .4 2.0 2.0 238.1|+=============================================================================+



SYSTEM or SYSType: EPILOG Keyword

Description: Used to display workload degradation across the entire system.

DISPLAY SYSTEM YDAY STIME(9) ETIME(17)

This command results in a set of panels for the reporting period. One of the resulting display panels might look like this systemwide degradation display:

The SYSTEM display shows you a general picture of transactions running under MVS. The degradation figures and percentages are derived by dividing total counts by the average number of address spaces running during the interval. For example, the Using CPU figure of 1.4% means that the average or typical MVS transaction spent 1.4% of its time using CPU. Notice the notation in the display header indicating that systemwide degradation is being displayed.

SYSTEM is not compatible with any of the other workload keywords.






+=============================================================================+| System Wide || From 14:00 To 14:15 On 07/31/99 Elap = 14:51 M SYSA |+-----------------------------------------------------------------------------+|Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0||Using CPU 0.04 S 1.4|. . . . . . . . . . .||ECB Wait (W/ STIMER) 1.37 S 46.1|------------======> . . . . . .||ECB Wait 0.55 S 18.5|------->. . . . . . . . .||STIMER Wait 0.27 S 8.9|--->. . . . . . . . . .||Detected Wait 0.19 S 6.3|--> . . . . . . . . . .||Waiting For CPU 0.17 S 5.6|--> . . . . . . . . . .||Average Trans Time 2.98 S 2699 MVS Transactions Ended ||Productivity Index 14% |+=============================================================================+

T Commands and Keywords 211

T Commands and Keywords


Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212THISMONTH or TMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212THISWEEK or TWK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212THISYEAR or TYR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212TITLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213TITLE2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213TITLE3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214TMN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214TODAY or TDAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214TOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214TOTAL or TOT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215TSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215TSOUSER or TSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215TWAITOF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216TWAITOFF or TWAITOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216TWAITON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216TWK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217TYR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

18




TDAYType: EPILOG Keyword

Description: See TODAY.


TESTType: EPILOG Keyword

Description: Instructs WPF not to write the profile it has generated to the Profile datastore. You can thus create and display profiles while testing for the most appropriate OUTLIER value without wasting datastore space.

We recommend that you specify the PLOT keyword, or leave it as the default, when using TEST so that you can see the different ranges of outliers generated by your test profile.


THISMONTH or TMNType: EPILOG Keyword

Description: Displays data from the first day of the current month to the most recent record in the database.



THISWEEK or TWKType: EPILOG Keyword

Description: Displays data from the first day of the current week to the most recent record in the database.

Note: The first day of the week is a Monday.



THISYEAR or TYRType: EPILOG Keyword



Description: Displays data from the first day of the current year to the most recent record in the database. THISYEAR covers a long time period and therefore may take a long time to process when used with the DISPLAY command.



TITLEType: EPILOG Keyword

Description: Used interchangeably with TITLE2 and TITLE3 to produce one line of a possibly multi-line report title. The first of these title keywords specified on the command gives the first line of the report title, and so on. For example,



produces the following page separator three times on the dataset identified by the RKM2OUTR DD statement.

The operand for this keyword is 1–72 characters long.

Related Information: Keyword of: COMPARE, COMPEXT, DISPLAY, EXTRACT, INQUIRE, OBTAIN, PAGESEP, SET, and SETP


TITLE2Type: EPILOG Keyword




Description: Used interchangeably with TITLE1 and TITLE3 to produce one line of a possibly multi-line report title. The first of these title keywords specified on the command gives the first line of the report title, and so on. The operand for this keyword is 1&ndash.72 characters long.

Related Information: Keyword of: COMPARE, COMPEXT, DISPLAY, EXTRACT, INQUIRE, OBTAIN, PAGESEP, SET, AND SETP


TITLE3Type: EPILOG Keyword

Description: Used interchangeably with TITLE1 and TITLE2 to produce one line of a possibly multi-line report title. The first of these title keywords specified on the command gives the first line of the report title, and so on. The operand for this keyword is 1–72 characters long.

Related Information: Keyword of: COMPARE, COMPEXT, DISPLAY, EXTRACT, INQUIRE, OBTAIN, PAGESEP, SET, AND SETP


TMNType: EPILOG Keyword

Description: See THISMONTH.


TODAY or TDAYType: EPILOG Keyword

Description: Displays data from the beginning of the current day to the most recent record in the database.



TOTType: EPILOG Keyword

Description: See TOTAL.




TOTAL or TOTType: EPILOG Keyword

Description: Displays total performance group figures, and combines the data over the time period specified in the command. There are no operands. By default, performance group data is displayed as average figures for each interval. The TOTAL display shows you the total wait time of all transactions for each wait reason, summed over the specified time period. For example,

DISPLAY PGN(2) YESTERDAY TOTAL

results in the following display:



TSOType: EPILOG Keyword

Description: See TSOUSER.


TSOUSER or TSOType: EPILOG Keyword

Description: Selects TSO session degradation data by TSO user ID. The TSO user ID can be further qualified by JES number to specify a particular session. The operand for this keyword is 1–8 characters long; it also accepts a wildcard (*) character. TSOUSER is not compatible with CLASS. For example,

DISPLAY TSO(USER01(T4806)) INTERVAL

displays degradation data for the TSO user session of USER01 with JES number 4806. Notice that the JES number follows the TSO user ID and is prefixed with a T. The INTERVAL keyword specifies that a separate display panel is generated for each interval.


+=============================================================================+ | Performance Group = 2 Symbolic Name = DEV TSO | | From 00:16 TO 24:00 ON 08/29/99 SYSA | | Total Of 94 Intervals | +-----------------------------------------------------------------------------+ |Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0| |Using CPU 1:26 H 4.6|-> . . . . . . . . . .| |Long Wait 13:34 H 43.4|------------=====> . . . . . .| |Waiting For CPU 3:49 H 12.2|----> . . . . . . . . .| |Total Trans Time 31:17 H 80948 MVS Transactions Ended | |Productivity Index 7% | +=============================================================================+







Related Information: Keyword of: COMPARE, COMPEXT, DISPLAY, EXTRACT, INQUIRE, OBTAIN, PROFILE, and SETP.


TWAITOFType: EPILOG Keyword

Description: See TWAITOFF.


TWAITOFF or TWAITOFType: EPILOG Keyword

Description: Excludes swaps due to terminal input waits in the degradation display for performance groups. This is the default, since these waits are not generally considered to be related to system degradation. See also TWAITON.



TWAITONType: EPILOG Keyword

Description: Includes swaps due to terminal input waits in the degradation display for performance groups. When the system is waiting for a TSO user to enter data on the terminal, the user is not actually within an MVS transaction&semi. such a user is generally shown by degradation analysis to be swapped out for a terminal input wait. Because users in this state are not within a transaction, this does not represent degradation and is not ordinarily reported as such.



However, if you add the TWAITON keyword to a DISPLAY request, you can display these states. The resulting display looks like this:

Instead of response time, the display now shows response plus think time.

By including the TWAITON keyword in a DISPLAY command, you display terminal input waits for that command only. Alternatively, you can set a TWAITON default for all successive DISPLAY commands by using the SET keyword.

Once you have set the default to TWAITON using SET, the TWAITOFF keyword on DISPLAY allows you to suppress the display of terminal input waits for a given display and still leave the default set to TWAITON.



TWKType: EPILOG Keyword

Description: See THISWEEK.


TYRType: EPILOG Keyword

Description: See THISYEAR.


+=============================================================================+ | Performance Group = 2 Symbolic Name = DEV TSO | | From 21:30 To 21:45 On 06/02/99 Elap = 14:57 M SYSA | +-----------------------------------------------------------------------------+ |Wait_Reason_____________Time_____%_|0___1___2___3___4___5___6___7___8___9___0| |Using CPU 0.06 S .9|. . . . . . . . . . .| |Terminal Input Wait 5.79 S 72.3|------------============>>>>> . . .| |Trans And Think Time 7.10 S 142 MVS Transactions Ended | |Productivity Index 22% | +=============================================================================+

U-W Commands and Keywords 219

U-W Commands and Keywords


Commands and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220WORKLOAD or WKL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

19




USEType: EPILOG Keyword

Description: Defines a list of datastores that supersede the active datastore list. The use operand is similar to the ADD operand, except that the ADD operand adds datatstores to the active datastore list, while the USE operand supersedes the active datastore list with a new list of one or more datastores.


VType: EPILOG Navigational Command

Description: Navigates you from the DASD Resource (overall on a single system) to the DASD Resource (single device across multiple systems) display in a multi-system configuration.

Related Information: Other Fast Path Navigation Commands: D, J, P, R, S, T, W, and X

WType: EPILOG Navigational Command

Description: Navigates you from the Summary Wait display to the Detailed Wait display.

Related Information: Other Fast Path Navigation Commands: D, J, P, R, S, T, V, and X

WORKLOAD or WKLType: EPILOG Keyword

Description: Selects Workload Manager workload task degradation data by task name. The operand for this keyword is 1–8 characters long; it also accepts a wildcard (*) character.

This keyword is only valid when the system is running in WLM goal mode. The SERVCLAS keyword is not compatible with the ACCOUNT or CLASS keywords. For example,

DISPLAY SCL(TSOSERV) LASTWEEK

obtains service class degradation data for service class TSOSERV last week.



Execution state by service class (SAS dataset SCLDETL): CFRAMES, CLASTYP, CPUSU, DEVADD, EDATE, EDATTIME, EFRAMES, ETIME, ENQNAME, EXTDTIME, GOALDUR, GOALIMP, GOALPVAL, GOALRTU, GOALTYPE, GOALVALU, IORATE, IOSU, MSOSU, NAME, NUMTRX, NUMICMB, PERIOD, PRODIDX, RCTTIM, SDATE, SDATTIME, STIME, SMFID, TOTVEL, TRXACT, TRXELAP, TRXRESP, TRXEXEC, VELOCITY, VOLSER, WAITNAME, WAITPCT, WAITTIME, WRKNGSET

U-W Commands and Keywords 221



Related Information: Keyword of: DISPLAY. See Workload Keywords in “Command Groupings” on page 19.

X-Z Commands and Keywords 223

X-Z Commands and Keywords


X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224XPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224YDAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226YESTERDAY or YDAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

20




XType: EPILOG Navigational Command

Description: Navigates you from the Degradation display to the XPG display.

Related Information: Other Fast Path Navigation Commands: D, J, P, R, S, T, V, and W

XPGType: EPILOG Keyword

Description: Displays the distribution of various execution states across performance groups. The cross-performance group display is available for single intervals only. There are no operands.

XPG is not compatible with COMBINE, SUMMARY, and DETAIL. For example,

DISPLAY XPG YDAY STIME(11) ETIME(17)

might result in this cross-performance group degradation display:

The format of the display is different from other performance group degradation displays. Across the top, the display shows the 14 top execution states, ranked by the number of times an address space was found in that state. The abbreviations for each execution state (except for I/O and enqueues) are summarized in Wait Reason Codes, Detail in “Command Groupings” on page 19. Active I/O on a device is represented by just the device number (for example, 736). Queued and DASD RESERVE execution states are shown by prefixing the device number with a Q or an R (for example, Q736 or R736). Enqueue execution states are indicated by abbreviations for the enqueue major names, which are described in the entry for the ENQUEUE keyword.

On the left side, the display lists performance groups active during the interval in ascending performance group number order. (If a symbolic name has been defined for a performance group, the symbolic name is displayed. In this example, SYSTEM is the symbolic name for performance group 0, REGBATCH for performance group 1, and TSO for performance group 2.)

Each column shows a systemwide view of a given execution state, broken down by performance group. For example, column 1 always shows a breakdown of the execution

+=============================================================================+| Period: 11:45 to 12:00 on 08/23/99 Elap = 15:00 M A083 |+-----------------------------------------------------------------------------+|XPG CPU DET CPW TIN LON 140 736 A9A EXC QA9A 157 Q4A3 Q736 4A3 ||*SYSTEM* 1.4 43.4 5.0 2.0 ||REGBATCH 65.5 4.7 44.6 100. 6.2 13.6 100. 0.9 100. 99.5 100. 70. 100.||TSO 26.3 51.9 6.3 100. .2 99.1 .5 ||PERF5 3.9 33.3 86.2 20. ||PERF9 2.9 10.8 91.6 .2 10. |+=============================================================================+

X-Z Commands and Keywords 225


state CPU Utilization. In the previous figure, this column shows that when EPILOG found the CPU being utilized, 65.5% of the time it was being used by the REGBATCH performance group, 26.3% of the time it was being used by the TSO performance group, and so on. Each column adds to 100%, except perhaps for rounding errors.

This format gives you insight into inter-performance group contention, that is, how the activity of one performance group affects another performance group. To get a feel for this, let’s look at the two columns that describe activity on device 736. The column labeled 736 shows active I/Os to that device, and the column labeled Q736 shows queued I/O. You can see that when EPILOG for IMS found the device active, 86.2% of the time it was being used by performance group 5. When the device was found waiting, 70% of the time it was REGBATCH that was waiting. At this point, you might want to look at a degradation display for REGBATCH. If waiting for device 736 was a major degradation factor for REGBATCH, you could conclude that performance group 5 was causing a good deal of that.

Your installation’s performance group definitions will influence the way this information is interpreted. For the purpose of the example, let’s say that performance group 5 consists of CICS users, and REGBATCH consists of overnight batch jobs that were submitted that day. This changes the interpretation radically. In this case, we will see performance group 5 as the preferred group, and will view any contention from REGBATCH as undesirable. In the Q736 column, you can see that when EPILOG for IMS found I/O queued for device 736, 20% of the time it was performance group 5, and that when the device was found active, 13.6% of the time it was being used by REGBATCH. If queued I/O to device 736 was a significant source of degradation to performance group 5, you can see that the REGBATCH performance group is causing some of that. Most of the activity on device 736, however, is being done by performance group 5 itself, which means that address spaces within performance group 5 are competing for that device. This is a good example of self-contention within a performance group.

By adding the SUMWAIT keyword to the command, you can display summary wait categories instead of detail wait reasons. A typical XPG display with SUMWAIT follows.



This display presents a more simplified picture of cross-performance group degradation.



YDAYType: EPILOG Keyword

Description: See YESTERDAY.


YESTERDAY or YDAYType: EPILOG Keyword

Description: Displays data from the beginning of the previous day to the last record of the previous day.



+-----------------------------------------------------------------------------+ | From: 15:26 To 15:30 On 07/07/99 Elap = 3:59 M SYSA | +-----------------------------------------------------------------------------+ |XPG MISC I/O SWAP OPER CPU PAGE SRM | |*SYSTEM* 2.5 29.3 91.4 19.8 | |REGBATCH 3.5 30.9 97.6 42.2 27.9 | |DEV TSO .0 2.4 2.2 | |STC TASK 22.6 14.5 2.6 | |IMS CNTL 3.8 | |VTAM 3.7 14.1 | |JES2 3.1 7.7 | |PERF15 15.1 .3 | |PERF16 7.1 .3 27.0 | |PERF17 .5 10.2 .6 17.0 12.8 72.1 | |AUX A.S. 15.3 | |Q BATCH 1.0 | |PERF26 3.2 32.3 | |CICS TST 10.5 7.3 14.2 | |PERF28 3.8 | |PERF30 3.7 .3 | +-----------------------------------------------------------------------------+

Data Dictionary 227

Data Dictionary

This appendix describes the data elements which can be exported from the historical datastores. It is intended to be used as a reference when you write programs that use data generated by the OBTAIN command or the SAS interface, as explained in the OMEGAMON II for MVS User’s Guide.

Interpreting the Information ProvidedThe data elements are listed in alphabetical order. Information about data elements with both a long name and a short name (VOLS and VOLSER, for example) appears under the long name, VOLSER in our example. The entry for VOLS reads, “See VOLSER”. Please note that the short names listed here are the only recognized short names.

For each data element, the Data Dictionary provides a table entry, with several columns of data:

Data Element The name of a field in the historical datastore that can be accessed by an exporting command. The following OBTAIN example mentions three data elements: IPS, ICS and RMF:

OBT RINF STIME(9) ETIME(11) SDATE(8/2) EDATE(8/2)- ELEMENTS(IPS,ICS,RMF)

All three data elements can be found in the Data Dictionary.

Description A brief description of this data element along with any hardware or software requirements that apply. If the data element is drawn from a resource table (for example, RPGN) and it appears on the EPILOG resource display, we also provide its field name on that display.

Tables The tables that include this data element. Resource tables are identified by the resource keyword which generates them: RCCH, RCHN, RCPU, and so on. Workload degradation tables (BTCHDETL, PGNDETL, STCDETL, TSODETL) are generated by the workload keywords: ACCOUNT, CLASS, JOBNAME, and so on.

Commands The EPILOG commands that can be used to generate the data element. Note that EXTRACT and COMPEXT commands indicate the SAS interface.

Data Type The data type and length of the data element. The different formats (INT, COL, PC and SAS) may support different data types for a given data element.

The following symbols are used in the Data Type columns:

A

Interpreting the Information Provided


Symbol Definition

C Character (all formats)

D Floating point number (INT format)

F Floating point number (SAS format)

H Hexadecimal (in EBCDIC for COL and PC formats)

I Numeric signed integer (INT format)

N General numeric format. Can be integer or decimal. If positive, will be unsigned; if negative, will be signed. (COL and PC formats)

P Packed decimal (INT format)

T Time in hundredths of a second (for INT format)

U Unsigned binary integer (INT format)

X Hexadecimal (INT format)

Filtering Keywords

The exception threshold filters that can be used with this data element. RIF is the short form of the REPORTIF keyword.

Data D

ictionary229


Table 1. Data Dictionary

Data Element Description Tables Valid Values Commans

Data Type and Length Filter Key-

wordsSASOBTAIN

INT COL,PC

ACCTCDE Account code for batch jobs and TSO users. The source of the data is the accounting field on the job card or the LOGON procedure. This data element will only be valid for batch jobs and TSO session workloads if you have chosen to collect it in your installation’s collection filter process.

For COMPEXT data, this field refers to the batch job, started task, or TSO user session in the workload, not the profile.

BTCHDETL, BTCHCOMP, STCDETL, STCCOMP, TSODETL, TSOCOMP

User-defined OBTAIN, EXTRACT

C, 12 C, 12 C, 12 None

ACPU See SRCPU.ACRT See ACTRESP.ACTRESP

orACRT

Actual response time for a transaction (in milliseconds). See also the data element RESP.EPILOG field name: Avg Resp

RSCL Positive real number

OBTAIN,DISPLAY

F, 4 I, 4 N, 11 RIF

AGOT See AVGUGOUT.ANSP See AVGNSWAP.ARDY See AVGURDY.ARSP See AVGRESP.ASMQ See SRASMQ.ASRC See ASRPTCLS.ASRPTCLS

orASRC

The report class that the address space is classified into by the workload classification rules.

BTCHDETL,STCDETL,TSODETL

Valid service class name

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 None

ASSC See ASSRVCLS.ASSF See ASSRVFLG.ASSRVCLS

orASSC

The service class that the address space is classified into by the workload classification rules.

BTCHDETL, STCDETL, TSODETL

Valid service class name

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 None



wordsSASOBTAIN

INT COL,PC

ASSRVFLGor

ASSF

Indicates whether the address space is a server.

BTCHDETL, STCCOMP, TSODETL,

0 =non-server, 1=server

OBTAIN, EXTRACT

C, 1 C, 1 C, 1 None

AUIC See SRUIC.AUIN See AVGUIN.AUOT See AVGUOUT.AVGCTRX

orAVTX

Average concurrent transactions. The average number of concurrent transactions in the performance group for the intervalEPILOG field name: Avg Trx

RPGN Positive real number

OBTAIN,EXTRACT

F, 4 I, 4 N, 11 RIF

AVGNSWAPor

ANSP

Average non-swappable users. The average number of non-swappable users who were concurrently active during the interval.EPILOG field name: Avg NSwap

RDOM Positive integers

OBTAIN,EXTRACT

F, 4 I, 4 N, 10 RIF

AVGRESP or

ARSP

Average response time for a transaction (in milliseconds). See also the data element RESP.EPILOG field name: Avg Resp

RPGN Positive real numbers

OBTAIN, ____ I, 4 N, 11 RIF

AVGSTOR Average storage use(bytes) per second RSCL Valid unsigned numbers

OBTAIN,EXTRACT,DISPLAY

F, 4 U, 4 N, 11 RIF

AVGTRXINor

TXIN

Average transaction in. The average number of concurrent transactions in storage from the performance group.EPILOG field name: Avg In


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

AVGUGOUTor

AGOT

Average users going out. The average number of address spaces in the domain that were marked for swap-out during the interval.EPILOG field name: Going Out

RDOM Positive real numbers

OBTAIN,EXTRACT

F, 4 I, 4 N, 11 RIF

Data D

ictionary231




wordsSASOBTAIN

INT COL,PC

AVGUINor

AUIN

Average users in. The average number of swappable users from the domain that were in-storage during the interval.EPILOG field name: Users In


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

AVGUOUTor

AUOT

Average users out. The average number of users in the domain that were swapped-out during the interval.EPILOG field name: Users Out


OBTAIN,EXTRACT

F, 4 I, 4 N, 11 RIF

AVGURDYor

ARDY

Average users ready. The average number of users in the domain that were ready to use the CPU.EPILOG field name: Avg U Ready

RDOM Positive real number

OBTAIN,EXTRACT

F, 4 I, 4 N, 11 RIF

AVGWKSTor

WKST

Average working set. The average working set size for an address space in the performance group (in bytes).EPILOG field name: Avg WKST

RPGN Positive integers

OBTAIN,EXTRACT

F, 4 I, 4 N, 10 RIF

AVTX See AVGCTRX.BATAVGAS

orBAVG

Batch average address spaces. The average number of concurrent batch address spaces running during the interval.

RCPU Positive real number

OBTAIN,EXTRACT

F, 4 I, 4 N, 11 RIF

BATMINASor

BMIN

Batch maximum address spaces. The highest number of concurrent batch address spaces running during the interval.EPILOG field name: Batch Max

RCPU Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

BATMINASor

BMIN

Batch minimum address spaces. The lowest number of concurrent batch address spaces running during the interval.EPILOG field name: Batch Min


OBTAIN,EXTRACT

F, 4 I, 4 N, 10 RIF

BAVG See BATAVGAS.BMAX See BATMAXAS.



wordsSASOBTAIN

INT COL, PC

BMIN See BATMINAS.BPCI See BPSSCCH1.BPC2 See BPSSCCH2.BPSSCCH1

orBPC1

The bypass cache percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3880 first storage director or the 3990/2105 subsystem.EPILOG field name: Bypass Cache %

RCCH Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

BPSSCCH2or

BPC2

The bypass cache percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3880 second storage director.EPILOG field name: Bypass Cache %


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

BUSY See CPCTBUSY.CACHSTT1

orCST1

The caching status of the 3990/2105 or the 3880 first storage director.EPILOG field name: Cache State

RCCH On 3880 displays: “activbb” or “Inactbb,” on 3990/2105 displays: “PenAcbb,” “PenDabb,” “TimeObb,” “activ*bb,” “inact*bb,” “PenAc*bb,” “PenDa*bb,” or “TimeO*bb”

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 RIF

CACHSTT2or

CST2

The caching status of the 3880 second storage director.EPILOG field name: Cache State

RCCH “activbb,” “inactivbb,” or“inact*bb“

OBTAIN,EXTRACT

C, 8 C, 8 C, 8 RIF

Data D

ictionary233




wordsSASOBTAIN

INT COL, PC

CAT See SWPCATG.CBSY See CPPCTBSY.CCFF See CPUCOEFF.CCHDASDN

orTCDN

The normal track transfers from cache to DASD for a cache device, expressed in tenths of a tract per second. This statistic comes from the 3990/2105 subsystem.


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

CFRAMESor

CFRM

The number of central storage frames occupied by an address space.

SCLDETH, RCLDETL, WKLDETL

Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

CHNTYPEor

CTYP

Channel type, including byte multiplexor, block multiplexor, ESCON&TM. channel, ESCON converter, ESCON director, and ESCON channel-to-channel adapter.EPILOG field name: Typ

RCHN Valid channel types are:

BYTBLKES-CHNES-CNVES-DIRES-CTC

OBTAIN,EXTRACT

C,8 C,6 C,6 RIF

CHPIDor

CPID

Channel path ID.EPILOG field name: CHPID or CHN

RCHN,RLCU

Twohexadecimaldigits

OBTAIN,EXTRACT

C, 2 C, 2 C, 2 RIF

CHPINSECor

CINS

The rate at which I/O requests for devices attached to this control unit are completed by this channel path.EPILOG field name: CHPID Ints per secEnvironment: XA, ESA (3090™ only)

RLCU Positiveintegers

OBTAIN,EXTRACT

F, 4 I, 4 N, 11 RIF

CIDX See CONTIDX.CINS See CHPINSEC.CIOPRSEC

orCIOS

Average number of channel I/O per second RCHN Valid signed number

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF



wordsSASOBTAIN

INT COL, PC

CLASDESC or

CLSD

The service class description. RSCL Valid service class description

OBTAIN, EXTRACT

C, 32 C, 32 C, 32 RIF

CLASNAME or

CLSN

The service class name. RSCL Valid service class name

OBTAIN, EXTRACT,DISPLAY

C, 8 C, 8 C, 8 RIF

CLASSTYP or

CLTY

The class type: service class or report class. RSCL, SCLDETL, RCLDETL

S = service class or R = report class

OBTAIN, EXTRACT

C, 1 C, 1 C, 1 RIF

CLSD See CLASDESC.CLSN See CLASNAME.CLTY See CLASSTYP.CMOD See CNTRLMOD.CNTRLMOD

orCMOD

The controller model.EPILOG field name: CU Type

RCCH 3880-13, 3880-23, 3990-3, 3990-6 or 2105

OBTAIN, EXTRACT

C, 7 C, 7 C, 7 RIF

CONNTIMEor

CTIM

Connect time. The average number of milliseconds the device is connected to the channel path for search and data transfer.EPILOG field name: Conn

RDAS Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

CONTIDXor

CIDX

Contention index. The contention index of a domain is used to select which domain will have its target MPL adjusted when the SRM determines the system’s MPL must be changed. The contention index indicates how busy the system looks to the domain as a whole. Its method of calculation is determined by the installation’s IPS.EPILOG field name: Contn Index


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

Data D

ictionary235




wordsSASOBTAIN

INT COL, PC

CPBUSUSEor

CBUS

Channel bUS Utilization in tenths of a percent

RCHN Positive real numbers between 0.0% and 100.0%

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

CPCRRATEor

CCRD

Channel Complex Read Rate in lenths of a megabyte per second

RCHN Valid signed numbers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

CPCTBUSYor

BUSY

Channel percent busy. The percentage of the interval that the channel was busy.EPILOG field name: % Busy

RCHN Positive real numbers between 0.0% and 100.0%

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

CPCWRATEor

CCWR

Channel Complex Write Rate in tenths of a megabyte per second


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

CPLRRATEor

CLRD

Channel LPAR Read Rate in tenths of a megabyte per second


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

CPLTBUSYor

CPLU

Percent of channel utilization by the LPAR RCHN Valid signed numbers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

CPLWRATEor

CLWR

Channel LPAR Write Rate in tenths of a megabyte per second


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

CPID See CHPID.CPM See CPUMODEL.CPPCTBSYorCBSY

The percentage of the time that all channel paths for this LCU were busy at the same time.EPILOG field name.: % All Ch Path Busy

RLCU Positive real numbers between 0.0% and 100.0%

OBTAIN, EXTRACT

F, 4 F, 4 F, 4 RIF

CPS See CPUSERL.CPUADJF CPU speed adjustment factor RSCL Valid

unassigned numbers

OBTAIN,EXTRACT,DISPLAY

F, 4 U, 4 N, 11 RIF

Data Element Description TablesValid

Values Commans


wordsSASOBTAIN

INT COL, PC

CPUCOEFFor

CCFF

The CPU Coefficient*10,000. RSCL Valid unsigned numbers

OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

CPUFLAG Indicates any change to the status of the CPU configuration that may have affected RCPU values during the interval. The CPU flags are represented as one decimal value. The decimal value is equivalent to a 32 bit unsigned binary field. Each bit represents a status change. Bit 0 represents the most significant bit.

RCPU OBTAIN, EXTRACT

F, 4 X, 4 H, 8 None

Bit Description0 - 7 Unused.8 The number of physical processors

assigned for use by logical partitioning changed during the combined reporting interval.

9 The number of logical processors assigned to thislogical partition changed during the combined reporting interval.

10 The wait state assist status of the logical partition changed during the combined reporting interval.

11 The combined record includes interval records with different logical partition names or numbers.

12 The LPAR Management data indicator.13 -14 Unused.

Data D

ictionary237


Data Element Description TablesValid

Values Commans


wordsSASOBTAIN

INT COL, PC

(Continued)=====>CPUFLAG

Bit Description15

16

Indicates the availablity of LPAR management data during the user-requested combined reporting interval.The number of CPUs in the configuration changed during the combined reporting interval.

17 Reserved.18 The record contains queuing I/O

information (XA and ESA only).19 Some combined interval records

lack queuing information.20 SRB service definition coefficient

changed during combined interval.21 Indicates that the system was

running as a logical partition.22 Logical partitioning information is

missing.23 Mode change to or from logical

partitioning24 CPU speed factor is missing from the

record. The CPU speed factor is used to calculate the SRB, TCB, and MVS percent utilization figure. If it is missing, EPILOG derives a CPU speed factor from the current processor configuration and uses it in calculating the percent utilization figures.


Data Type and LengthFilter Key-

wordsSASOBTAIN

INT COL, PC

(Continued)=====>CPUFLAG

CPUID CPU identifier. It identifies a specific CPU in the processor complex.EPILOG field name: CPUn


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 None

CPUMODELor

CPM

The CPU model type, for example, 3081K.EPILOG field name: Model

RINF Valid CPU model numbers

OBTAIN, EXTRACT

C, 6 C, 6 C, 6 RIF

CPUPCT Percent of CPU consumed during the interval RSCL Positive real numbers

OBTAIN,EXTRACT

I, 4 N, 11 RIF

CPUSERLor

CPS

CPU serial. The CPU serial number is a unique number assigned by the manufacturer for this specific processor.EPILOG field name: Serial

RINF Positive integers. In a logical partitioning environment, the second position from the left holds a hexadecimal digit (0-F).

OBTAIN, EXTRACT

C, 6 C, 6 C, 6 RIF

CPUSUSor

CPSU

The CPU service units per second. RSCL, RCLDETL, SCLDETL

Valid unsigned number


F, 4 U, 4 N, 11 RIF

CPUTRXTM Total CPU time for the job, task, session, or step (in CPU seconds).

BTCHDETL, STCDETL, TSODETL

Positive integers

OBTAIN, EXTRACT

F, 4 D, 4 N, 10 None

Bit Description25 The number of CPUs in the

configuration changed during the combined reporting interval.

26 Reserve27 An error was encountered in

calculating the MVS overhead.

28 Indicates dedicated processors in the logical partition.

Data D

ictionary239




wordsSASOBTAIN

INT COL, PC

CSRVTIMEor

SERV

Average channel service time RCHN Valid signed numbers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

CST1 See CACHSTT1.CST2 See CACHSTT2.CTIM See CONNTIME.CTYP See CHNTYPE.CUBY See DCUBSY.CUDEFSEC

or

UDEF

The percent of I/O requests deferred for that control unit.

EPILOG field name: % CU Busy

Environment: XA, ESA (3090 only)

RLCU Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

CUID Identifies a control unit in the LCU.

EPILOG field name: CU


OBTAIN, EXTRACT

C, 4 C, 4 C, 4 RIF

CUM See CURMPL.CUPCTBSY

or

UBSY

The percentage of I/O requests to the LCU deferred due to a CONTROL UNIT BUSY condition.

EPILOG field Name: CU Busy

Environment: Non-3090


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

CURMPL

or

CUM

Current multiprogramming level. The actual multiprogramming level assigned to the domain for the interval.

EPILOG field name: Cur MPL


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

DACT See POLACTDT.DASDCCHN

or

TDCN

The normal track transfers from DASD to cache for a cache device, expressed in tenths of a track per second. This statistic comes from the 3990/2105 subsystem.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF



wordsSAS

OBTAIN

INT COL, PC

DASDCCHS

or

TDCS

The sequential track transfers from DASD to cache for a cache device, expressed in tenths of a track per second. This statistic comes from the 3990/2105 subsystem.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

DASDFWST or

DFWS

DASD Fast Write status. (3990/2105 only) RCCH “activbb”, “inactbb”, “PenAcbb”, “PenDabb, “activ*bb”, inact*bb”, “PenAc*bb”, “PenDa*”,or “n/a”

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 RIF

DBSY See DPBBUSY or DPCTBSY.DCUBSY

or CUBY

Average delay for an I/O request caused by the control unit busy condition (in milliseconds).EPILOG field name: CUBEnvironment: XA, ESA (3090 only)


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

DDEVBSY or

DVBY

Average delay for an I/O request caused by the device busy condition (in milliseconds).EPILOG field name: DBEnvironment: XA, ESA (3090 only)


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

DDEVPAVS Maximum number of Parallel Access Volumes configured for the DASD volume.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

DDEVPAVF A flag indicating whether the Number of Parallel Access Volumes changed during the reported interval

RDAS BlankYN

OBTAIN, EXTRACT

C, 1 C, 1 C, 1 RIF

DEFDESC or

DEFD

The service definition description. RSCL Valid service definition description

OBTAIN, EXTRACT

C, 32 C, 32 C, 32 RIF

DEFINSDT or

DINS

The date definition installed. RSCL Positive integers

OBTAIN, EXTRACT

C, 8 P, 4 N, 8 RIF

Data D

ictionary241



Data Type and Length

Filter Key-

wordsSAS

OBTAIN

INTCOL, PC

DEFINSTMor

TINS

The time that the definition was installed. RSCL Positive integers

OBTAIN, EXTRACT

C, 8 T, 4 C, 8 RIF

DEFNAME or

DEFN

The service definition name. RSCL Valid service definition name

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 RIF

DEFUSER or

DEFU

The definition installer userid. RSCL Valid jobname

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 RIF

DESW See ESDSWPSC.DEVA See DEVADD.DEVADD

orDEVA

Device number. The channel, control unit, and unit numbers used to identify the device number.For COMPEXT data, a blank address for ACTIVEIO, QUEUEDIO, and RESRVEIO signifies that the observation is a composite of all the extracted data for the wait reason and is not device specific.EPILOG field name: Dev # or Dev Adr

RCCH, RDAS,RPDS, RSDS, PGNDETL, PGNCOMP, BTCHDETL, BTCHCOMP, STCDETL, STCCOMP, TSODETL, TSOCOMP, RCLDETL, SCLDETL

Unsigned hexadecimal digit, 0000 to FFFF

OBTAIN, EXTRACT

C, 4 C, 4 (for

workload

tables),C, 3 (forre-

source tables)

C, 4 (for

workload

tables),C, 3

(for resource tables)

RIF (resources)

None (workloads)

DEVTYPE or

DTYP

The device model type, such as 3380.EPILOG field name: Dev TypeEnvironment: XA, ESA (3090 only)

RPDS, RSDS Valid device types

OBTAIN, EXTRACT

C, 4 C, 4 C, 4 RIF

DFWBYPSSor

DFWR

The DASD fast write bypass percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3990/2105 subsystem.EPILOG field name: DFW Bypass %


OBTAIN, EXTRACT

F, 4 I, 4 N,11 RIF



wordsSASOBTAIN

INT COL, PC

DFWR See DFWBYPSS.DFWS See DASDFWST.DINS See DEFINSDT.DIOP See DIOPRSEC.DIOPRSEC

or DIOP

Device I/Os per second. The average number of I/Os per second issued to the device.EPILOG field name: I/O Rate

RDAS Positive real numbers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

DISCTIMEor

DTIM

Disconnect time (in milliseconds). For XA channels only. This represents the time the device is busy but not transferring data. This time is composed of such items as SEEK and SET SECTOR.EPILOG field name: Disc


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

DLCU See DLCUID.DLCUID

or DLCU (in RDAS)RLCU (in RLCU)

Logical control unit ID.EPILOG field name: LCUEnvironment: XA and above.

RDAS, RLCU

Positive integers

OBTAIN, EXTRACT

C, 3 C, 3 C, 3 RIF

DMN See DOMNUM.DOMNUM

or DMN

The domain identification number.EPILOG field name: Dmn


OBTAIN, EXTRACT

F, 4 U, 1 N, 3 RIF

DPBBUSY or

DBSY

Average delay time to an I/O request due to a busy ESCON director port.Environment: ESA (3090 and ES9000 only)


OBTAIN, EXTRACT

F,4 I,4 N,11 RIF

Data D

ictionary243




wordsSASOBTAIN

INT COL, PC

DPCTBSYor

DBSY

The percentage of I/O requests to the LCU deferred due to a DEVICE BUSY condition.EPILOG field name: Dev BusyEnvironment: Non-3090

RLCU Positive percentage, 0.0% to 100.0%

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

DPCTBUSY or

PBSY

Device percent busy. The percentage of the interval time that the device was busy.EPILOG field name: % Dev Busy

RDAS Positive percentage, 0.0% to 100.0%

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

DPGR See SRDMDPAG.DPRODIDX Delta productivity index. Difference in

productivity index between the workload and the profile. See also the data element PRODIDX.

PGNCOMP, BTCHCOMP, STCCOMP, TSOCOMP

0 - 100 COMPEXT F, 4 ____ ____ None

DSWP See DSWPPHSC.DSWPPHSC

or DSWP

Number of swaps per second from central storage to auxiliary storage that were not marked as logically swapped before the physical swap was performed.EPILOG field name: Direct

RSWA, RSWR

Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

DSXAFLAG Architecture flag. This flag indicates, for the RDAS dataset, that unique XA and ESA data elements apply.

RCHN, RCPU, RDAS, RSWA

“XAb” OBTAIN, EXTRACT

C, 3 C, 3 C, 3 RIF

DTIM See DISCTIME.DTRXELAP Delta average elapsed time (in seconds).

The difference in average elapsed times between the workload and the profile.

BTCHCOMP, STCCOMP, TSOCOMP

Positive or negative real numbers

EXTRACT F, 4 ____ ____ None

DTRXRESP Delta average transaction response time (in seconds). The difference in average transaction response time between the workload and the profile.

PGNCOMP Positive or negative real numbers

COMPEXT F, 4 ____ ____ None

DTYP See DEVTYPE.DVBY See DDEVBSY.



wordsSASOBTAIN

INT COL, PC

DWAITTME Delta average transaction time for this wait reason (in seconds). For performance group data, this data element contains the difference in average transaction time spent on this wait reason between the workload and the profile. For batch job, started task, and TSO session data, it contains the difference in average elapsed time spent on this wait reason between the workload and the profile.


Positive or negative real numbers


EDATE End date. The date value for the end of the interval that covers this OBTAIN record. This data element contains a time value. If multiple RMF-based intervals are being combined into larger intervals, this figure reflects the end date of the larger combined interval.

All (except RVLF, PGNCOMP, BTCHCOMP, STCCOMP, and TSOCOMP)

Positive integers

OBTAIN ____ P, 4 N, 8 None

EDATTIME End date time. The date and time value for the end of the interval that covers this SAS observation. For COMPEXT data, this field applies to the workload, not the profile. This data element contains a standard SAS date/time value. If multiple RMF-based intervals are being combined into larger intervals, this figure reflects the end date time of the larger combined interval.

All SAS tables

Positive integers


EFRAMES or

EFRM

Number of expanded storage frames occupied by an address space.

SCLDETL, RCLDETL, WKLDETL

Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

EMIG See ESMIGRAT.

Data D

ictionary245




wordsSASOBTAIN

INT COL, PC

ENQNAME Enqueue name. The major name component of an enqueue request.

PGNDETL, PGNCOMP, BTCHDETL, BTCHCOMP, STCDETL, STCCOMP, TSODETL, TSOCOMP RCLDETL, SCLDETL

Enqueue major names are defined during product installation and described in the entry for the ENQUEUE keyword.

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 None

ESASWPSCor

ESMG

Number of swaps per second that were first swapped from central storage to expanded storage, and then migrated from expanded storage to auxiliary storage.EPILOG field name: Migrated

RSWA, RSWR

Positive integers

OBTAIN, EXTRACT

F, 4 I,4 N, 11 RIF

ESAV See ESAVG.ESAVG

or ESAV

Average number of expanded storage frames available during the interval.EPILOG field name: Avg

RPAG Positive real numbers

OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

ESAX See ESTOAUX.ESDSWPSC

or DESW

Number of swaps per second from central storage to expanded storage that were not marked as logical swaps before the physical swap was performed.EPILOG field name: Direct

RSWA, RSWR

Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

ESFRREAL or

ESRL

Average number of pages per second sent to expanded storage from central storage for paging and swapping requests.EPILOG field name: Pages to ES per SecEnvironment: XA, ESA (expanded storage only)


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

ESIN See ESINST.



wordsSASOBTAIN

INT COL, PC

ESINST or

ESIN

The total amount of expanded storage installed (in frames).EPILOG field name: Installed FramesEnvironment: XA, ESA (expanded storage only)


OBTAIN, EXTRACT

F, 4 I, 4 , N,10 RIF

ESMAX or

ESMX

Maximum number of expanded storage frames available during the interval.EPILOG field name: MaxEnvironment: XA, ESA (expanded storage only)


OBTAIN, EXTRACT

F, 4 I, 4 , N,10 RIF

ESMG See ESASWPSC.ESMIGRAT

or EMIG

Expanded storage migration age; that is, the average length of time that a page remains unreferenced in expanded storage before it is migrated to auxiliary storage.Environment: XA, ESA (3090 only)

RSRM Positive integers

OBTAIN ____ I, 4 I, 10 None

ESMINor

ESMN

Minimum number of expanded storage frames available during the interval.EPILOG field name: MinEnvironment.: XA, ESA (expanded storgae only)


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

ESMN See ESMIN.ESMX See ESMAX.ESON See ESONLINE.ESONLINE

or ESON

The amount of expanded storage online during the interval (in frames).EPILOG field name: Online FramesEnvironment: XA, ESA (expanded storage only)


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

ESRL See ESFRREAL.

Data D

ictionary247




wordsSASOBTAIN

INT COL, PC

ESTOAUXor

ESAX

Average number of pages per second sent to auxiliary storage from expanded storage during the interval.EPILOG field name: Pages Migrated per SecEnvironment: XA, ESA (expanded storage only)


OBTAIN, EXTRACT

F,4 I,4 N,11 RIF

ESTSWPSC or

TESW

Number of swaps per second from central storage to expanded storage that were marked as logical swaps before the physical swap was performed.EPILOG field name: Trans

RSWA, RSWR

Positive integers

OBTAIN, EXTRACT

F,4 I,4 N,11 RIF

ETIME End time. The time value for the end of the interval that covers this OBTAIN record. This data element contains a time value. If multiple RMF-based intervals are being combined into larger intervals, this figure reflects the end time of the larger combined interval.

All (except PGNCOMP, BTCHCOMP, STCCOMP, and TSOCOMP)

Positive integers

OBTAIN ____ T, 4 C, 8 None

EXTDTIME Extract date time. The date and time the EXTRACT command which produced this observation was executed. This field is common to all observations in a dataset which were produced by a particular EXTRACT command and to the title observation in the title dataset which defines the parameters of the extract. This data element contains a standard SAS date/time value.

All SAS datasets

Positive integers


FIXED Average fixed frame counts (in 4K frames).EPILOG field name: Fixed


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 None

FXB See SRFIXB16.FXT See SRFIXTOT.



wordsSASOBTAIN

INT COL, PC

GOALCHNG or GLCH

Service class goal change indicator. RSCL 0 = No goal change1 = Goal changed

OBTAIN, EXTRACT

C, 1 C, 1 C, 1 RIF

GOALDUR or

GDUR

The period duration. RSCL, SCLDETL

Valid unsigned numbers


F, 4 U, 4 N, 11 RIF

GOALIMP or

GIMP

The goal importance. RSCL, SCLDETL

0 - 5 OBTAIN, EXTRACT,DISPLAY

C, 1 C, 1 C, 1 RIF

GOALPVAL or

GPVL

The goal percentage of transactions to complete within the response time set by goal value.

RSCL, SCLDETL


F,4 U,4 N,11 RIF

GOALRTUor

GRTU

Goal response time units. SCLDETL Positive integers

OBTAIN, EXTRACT

C, 1 C, 1 C, 1 RIF

GOALTYPE or

GTYP

The goal type. RSCL, SCLDETL


C, 1 C, 1 C, 1 RIF

GOALVALUor

GVAL

The response time goal value expressed in milliseconds.

RSCL, SCLDETL

Valid unsigned number


F, 4 U, 4 N, 11 RIF

HIGHSTEP Highest step number of the job or started task.

BTCHDETL, STCDETL

Positive integers

OBTAIN, EXTRACT

F, 4 U, 2 N, 5 None

ICFF See IOCOEFF.ICS The current ICS suffix.

EPILOG field name: ICSRINF Valid ICS

suffixesOBTAIN, EXTRACT

C, 2 C, 2 C, 2 RIF

IDEF See IOPTLDEF.IDFS See IODEFSEC.IHC1 See INHBCCH1.

Data D

ictionary249




wordsSASOBTAIN

INT COL, PC

IHC2 See INHBCCH2.INFFLAG Bits 8-15 indicate changes made during a

combined interval (not used unless the interval is combined.) The flags are represented as one decimal value. The decimal value is equivalent to a 32 bit unsigned binary field. Each bit represents a flag. Bit 0 represents the most significant bit.

RINF 1 or 0 in each of the bits

OBTAIN, EXTRACT

F, 4 I, 4 C, 10 None

Bit Description

0 - 7 Unused.

8 The partition number changed.

9 The partition name changed.

10 The number of physical processors changed.

11 The relative share changed.

12 The global time slice changed.

13 The CPU capping changed.

14 - 15 Unused.

16 VM is running in native mode.

17 Logically partitioned.

18 Dedicated processors.

19 Wait completion = yes.

20 CPU capping is in effect for the partition in which EPILOG is running.

21 Logical partitioning management data is present.



wordsSASOBTAIN

INT COL, PC

=====>INFFLAG

INHBCCH1 or

IHC1

The inhibit cache percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3880 first storage director or the 3990/2105 subsystem.EPILOG field name: Inhibit Cache %


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

INHBCCH2or

IHC2

The inhibit cache percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3880 second storage director.EPILOG field name: Inhibit Cache %


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

INTVLSRV or

SRVU

Average number of SRM service units used by all members of the domain during the interval.EPILOG field name: Intvl Srvce


OBTAIN, EXTRACT

F, 4 I,4 N, 10 RIF

Bit Description

22 - 23 Unused.

24 MVS level.

25 IPS.

27 OPT.

28 CPU model.

29 Serial.

30 Mode.

31 RMF version.

Data D

ictionary251




wordsSASOBTAIN

INT COL, PC

IOCOEFF or

ICFF

The I/O Coefficient*10,000. RSCL Valid unsigned number

OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

IOCRATE I/O activity rate in bytes per second RSCL Valid unsigned numbers


F, 4 U, 4 N, 11 RIF

IODEFSECorIDFS

Total percent of I/O requests on the LCU that were deferred.EPILOG field name: TotalEnvironment: XA, ESA (non-3090 only)

RLCU Positive real numbers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

IOINTRPT or

IONT

Average number of I/O interrupts per second handled by the processor during the interval.EPILOG field name: Interrupt Rate

RCPU Positive real numbers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

IONT See IOINTRPT.IOPERSEC

orIOSC

Average number of I/O requests for the dataset per second.EPILOG field name: I/Os per sec or IO per second

RPDS, RSDS Positive real numbers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

IOPIOQLNor

IOQL

The average number of I/O requests queued for this I/O processor.EPILOG field name: Avg # I/O QEnvironment: XA, ESA (3090 only)


OBTAIN, EXTRACT

F, 4 I, 4 N,11 RIF

IOPIOSECor

IOPS

The rate per second at which I/O requests are placed on the IOP initiation queue.EPILOG field name: I/Os per secEnvironment: XA, ESA (3090 only)


OBTAIN, EXTRACT

F, 4 I, 4 N,11 RIF

IOPROCID I/O processor ID.EPILOG field name: I/O ProcessorEnvironment: XA, ESA (3090 only)


OBTAIN, EXTRACT

C, 2 C, 2 C, 2 None



wordsSASOBTAIN

INT COL, PC

IOPS See IOPIOSEC.IOPTLDEF

orIDEF

The rate at which the IOP placed delayed I/O requests on the control unit header queue during the interval.EPILOG field name: I/Os per sec DeferredEnvironment: XA, ESA (3090 only)


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

IOQL See IOPIOQLN.IORATE

orIORT

The I/O rate in tenths of an I/O per second for an address space.


Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

IOSC See IOPERSEC.IOSQTIME

orQTIM

The average time (in milliseconds) that an I/O spent on the IOS queue for the device.EPILOG field name: IOSQ


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

IOSU or

ISU

I/O service units. RCLDETL, SCLDETL

Valid I/O service unit

OBTAIN, EXTRACT

C, 24 C, 24 C, 24 RIF

IPS The current IPS suffix.EPILOG field name: IPS

RINF Valid IPS suffixes

OBTAIN, EXTRACT

C, 2 C, 2 C, 2 RIF

ISU See IOSU.

ITDM See ITRGMPL.ITRGMPL

orITDM

Average In-Target MPL over the interval, as calculated by SRM.Environment: ESA SP 4.2 and above


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

JESCLASS Batch job execution class. For COMPEXT data, this field refers to the batch job in the workload, not the profile.

BTCHDETL, BTCHCOMP

Valid execution classes

OBTAIN, EXTRACT

C, 3 C, 3 C, 3 None

Data D

ictionary253




wordsSASOBTAIN

INT COL, PC

JESNUM JES job number for the batch job, started task, or TSO user session. For COMPEXT data, this field refers to the batch job, started task, or TSO session in the workload, not the profile.

BTCHDETL, BTCHCOMP, STCDETL, STCCOMP, TSODETL, TSOCOMP

Positive integers

OBTAIN, EXTRACT

C, 4 C, 4 C, 4 None

JOBNAME Batch job name. For COMPEXT data, this field refers to the batch job in the workload, not the profile.

BTCHDETL, BTCHCOMP


C, 8 C, 8 C, 8 None

LCUCPST Indicates the status of the channel path during the reporting interval. The status flags are represented as one decimal value. The decimal value is equivalent to a 32-bit unsigned binary field. Each bit represents a status flag. Bit 0 represents the most significant bit.

EPILOG field name: Comment

RLCU As described OBTAIN, EXTRACT

F, 4 X, 1 H, 2 None

LCUERROR If this data element contains a value other than hexadecimal zero (“0”), this indicates that the collector encountered an error while collecting this data, and that the data in this observation may not be reliable.

RLCU Hexadecimal numbers

OBTAIN, EXTRACT

C, 1 X, 1 H,2 None

LCUIOQLN or

LOQL

The average number of I/O requests queued for this LCU.EPILOG field name: Avg # I/O Q


OBTAIN, EXTRACT

F, 4 I, 4 N,11 RIF

0 = Channel path installed

1 = Channel path online

2 = Channel path varied

3 = Channel path offline to all devices

4 = Channel path to all devicesaltered

5 = Path data invalid



wordsSASOBTAIN

INT COL, PC

LCUIOSECor

LIOS

The rate per second at which I/O requests were successfully selected for initiation by the associated LCU.EPILOG field name: I/Os per secEnvironment: Non-3090


OBTAIN, EXTRACT

F, 4 I, 4 N,11 RIF

LCUTYPE or

LTYP

LCU record subtype. RLCU OBTAIN, EXTRACT

C, 1 U, 1 N, 3 None

LIOS See LCUIOSEC.LOQL See LCUIOQLN.LSPS See LTPPRSEC.LSW See LSWPRSEC.LSWPRSEC

or LSW

Logical swap rate (in pages per second). This rate consists of the total number of address spaces that were marked as logically swapped during the interval, divided by the number of seconds in the interval. (Some of these address spaces may have been subsequently transitioned to auxiliary or expanded storage during the interval.)EPILOG field name: Logical Swaps/Sec

RSWA, RSWR

Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

LSW See LSWPRSEC.LTPPRSEC

or LSPS

Percent of logical swaps that became physical swaps.EPILOG field name: Percent logical that became PhysicalEnvironment: XA, ESA (Non-3090)

RSWA 0 - 100 OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

LTYP See LCUTYPE.

Data D

ictionary255




wordsSASOBTAIN

INT COL, PC

MACHFLAG Machine flag. 3090 processors differ from other processors with respect to I/O activity and expanded storage. Because of this, there are several data elements unique to 3090 processors. This flag indicates that unique 3090 data elements apply.Environment: XA, ESA (3090 only)

RDAS, RLCU, RPAG, RSRM, RSWA, RSWR

Valid values are:“309X” for 3090 records or SAS observations,“bbbb” for non-3090 records or SAS observations.For the RPAG table, the valid values are:“EXT” for expanded storage systems,“bbb” for non-expanded storage systems.

OBTAIN, EXTRACT

C, 4 C, 4 C, 4 None

MAXMPL or

MXM

Maximum MPL specified for the domain in the IPS.EPILOG field name: Max MPL


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

MCFF See MSOCOEFF.MINMPL

or MNM

Minimum MPL specified for the domain in the IPS.EPILOG field name: Min MPL


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

MNM See MINMPL.



wordsSASOBTAIN

INT COL, PC

MODE Processor mode during the time period.EPILOG field name: Mode

RINF NATIVE = Native MVSVM = MVS under VMVM/PMA = MVS under VM/PMAPARTI- TIONED = MVS in LPAR mode

OBTAIN, EXTRACT

C, 20 C, 20 C, 20 RIF

MSOCOEFF or

MCFF

The MSO Coefficient*10,000. RSCL Valid unsigned number

OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

MSOSU or

MSU

MSO service units. RCLDETL, SCLDETL

Valid MSO service units

OBTAIN, EXTRACT

C, 24 C, 24 C, 24 RIF

MXM See MAXMPL.NAME Service class name, Report Class name, or

Workload name.EPILOG field name: Service Class, Report Class, or Workload

SCLDETL, RCLDETL

Valid name OBTAIN, EXTRACT

C,8 C,8 C,8 RIF

NMTR See NUMTRANS.NONFIXED Average non-fixed frame counts (in 4K

frames).EPILOG field name: Non-Fix


OBTAIN, EXTRACT

F, 4 I,4 N, 10 None

NPRO See NUMPHYS.NTRX See NUMTRX.

Data D

ictionary257




wordsSASOBTAIN

INT COL, PC

NUMICMB Number of EDS records extracted for the record (or SAS observation). This value is of interest in situations where data has been combined in some fashion.

All Positive integers

OBTAIN, EXTRACT

F, 4 I,4 N, 10 None

NUMPHYSS or

NPRO

The number of physical processors available to the logically partitioned processor complex.EPILOG field name: Physical ProcessorsEnvironment: Logically partitioned machine

RINF Positive real numbers

OBTAIN, EXTRACT

C, 1 C, 1 C, 1 RIF

NUMTRXor

NTRX

Number of transactions in the record.EPILOG field name:. Number of Transactions

PGNDETL, RCLDETL, SCLDETL

Positive integers

OBTAIN, EXTRACT

F, 4 D, 4 N, 10 None

NUMTRANS or

NMTR

The transaction count. RSCL Valid unsigned number


F, 4 U, 4 N,11 None

ODSN See OPENDSN.OPENDSN

or ODSN

Average number of DCBs and ACBs concurrently open on a volume. On MVS/ESA systems, this field contains the average number of allocations against a device.EPILOG field name: Open Dsns or Avg Allcs


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

OPT The current OPT suffix.EPILOG field name: OPT

RINF Valid OPT suffixes

OBTAIN, EXTRACT

C, 2 C, 2 C, 2 RIF



wordsSASOBTAIN

INT COL, PC

OSLEVEL or

OSLV

The level of MVS/ESA under which you are running.

RCPU, RCHN, RDAS, RDOM, RLCU

1 = ESA 3.1.02 = ESA 3.1.33 = SP 4.1.04 = SP 4.2.05 = SP 4.2.36 = SP 4.3.07 = SP 5.1.013 = SP 5.2.0

OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

OSLV . See OSLEVELOTDM See OTRGMPL.OTRGMPL

or OTDM

Average Out Target MPL over the interval, as calculated by SRM.Environment: ESA SP 4.2 and above


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PACCTCDE Account code for the profile. (For details, see data element ACCTCDE.)


User-defined COMPEXT C, 12 ____ ____ None

PAGEIN Average page-ins per second.EPILOG field name: Page/Sec In


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 None

PAGEOUT Average page-outs per second.EPILOG field name: Page/Sec Out


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 None

PAGES or

PGS

Average number of page operations per second (page-ins plus page-outs).


OBTAIN ____ I, 4 N, 11 None

PAGPERIO or

PGIO

Average number of pages per I/O request.EPILOG field name: Pages per IO

RPDS Positive real numbers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

Data D

ictionary259




wordsSASOBTAIN

INT COL, PC

PARTNAME or

PTN

Partition name. The name assigned to the partition in which EPILOG is running.EPILOG field name: Partition NameEnvironment: Logically partitioned machine


OBTAIN, EXTRACT

C, 8 C, 8 C, 8 RIF

PARTNUM or

PNUM

The partition number in which EPILOG is running.EPILOG field name: Partition NumberEnvironment: Logically partitioned machine


OBTAIN, EXTRACT

C, 1 C, 1 C, 1 RIF

PAVGELAP The average elapsed time for the profile (in seconds).


Positive real numbers

COMPEXT F, 4 I, 4 C, 10 RIF, SIF

PARTWGTor

PWT

Processor weight. Relative importance of the logical partition with respect to the other partitions that share the same CPU.EPILOG field name: Processor WeightEnvironment: Logically partitioned machine

RINF 0 - 1000.MIX indicates a logical partition with both shared and dedicated processors.

OBTAIN, EXTRACT

C, 3 C, 3 C, 3 RIF

PAVGTRX The average transaction response time for the profile (in seconds).

PGNCOMP Positive real numbers


PBSY See DPCTBUSY.PCMX See PCTMGPLX.PCPU See PCTCPU.PCRT See PRCNTRSP.PCTCMPLX

or PCTX

Processor complex CPU utilization. Percentage of total CPU cycles used by all the partitions in the processor complex.EPILOG field name: Processor Complex CPU UtilizationEnvironment: Logically partitioned machine


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF



wordsSASOBTAIN

INT COL, PC

PCTCPMVSor

PMVS

Percent CPU used by MVS for all processors during the interval. If RMF-based intervals were combined into larger intervals, this figure represents the percent CPU used over the larger combined interval. In processors that support logical partitioning, this value represents utilization for the partition under which EPILOG is running.EPILOG field name: CPU Utilization MVS


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PCTCPSRB or

PSRB

Percent CPU used by SRBs for all processors during the interval. If RMF-based intervals were combined into larger intervals, this figure represents the percent CPU used over the larger combined interval. In processors that support logical partitioning, this value represents utilization for the partition under which EPILOG is running.EPILOG field name: CPU Utilization SRB


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PCTCPSRB or

PSRB

Percent CPU used by SRBs for all processors during the interval. If RMF-based intervals were combined into larger intervals, this figure represents the percent CPU used over the larger combined interval. In processors that support logical partitioning, this value represents utilization for the partition under which EPILOG is running.EPILOG field name: CPU Utilization SRB


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PCTCPTCB or

PTCB

Percent CPU used by TCBs for all processors during the interval. If RMF-based intervals were combined into larger intervals, this figure represents the percent CPU used over the larger combined interval. In processors that support logical partitioning, this value represents utilization for the partition under which EPILOG is running.EPILOG field name: CPU Utilization TCB


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PCTCPU or

PCPU

Average percent of total CPU capacity used over the interval. If RMF-based intervals were combined into larger intervals, this figure represents the percent CPU used over the larger combined interval.EPILOG field name: nn %


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

Data D

ictionary261




wordsSASOBTAIN

INT COL, PC

PCTFULLor

PFUL

Average percent of slots used on the dataset.EPILOG field name: % Full

RPDS, RSDS 1-100 OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PCTG See PRCNTTXN.PCTINUSE

or PUSE

Percent of the time that the dataset was considered busy by ASM.EPILOG field name: % In Use

RPDS, RSDS 1-100 OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PCTPARTA or

PRTA

Average logical processor utilization. Average percent of total CPU cycles assigned to this partition that was used.EPILOG field name: Average Logical Processor UtilizationEnvironment: Logically partitioned machine


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PCTPARTA or

PRTA

Average logical processor utilization. Average percent of total CPU cycles assigned to this partition that was used.EPILOG field name: Average Logical Processor UtilizationEnvironment: Logically partitioned machine


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PCTPRMCPor

PRMC

The average percent of time that a physical processor in this partition was performing logical partitioning management functions.EPILOG field name: LPAR ManagementEnvironment: Partitioned, RMF 4.2.1 and above

RCPU 1-100 OBTAIN, EXTRACT

F, 4 I, 4 N,10 RIF

PCTMGPLX or

PCMX

The percent of time that logical partitioning management functions were being performed for the processor complex.EPILOG field name: Total LPAR Management OverheadEnvironment: Partitioned, RMF 4.2.1 and above

RINF 1-100 OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF



wordsSASOBTAIN

INT COL, PC

PCTPRTCP or

PRTC

Physical CPU utilization. Average percent of time that a physical processor in this partition was busy.EPILOG field name: Physical CPU UtilizationEnvironment: Logically partitioned machine


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PCTRESor

PRES

Percent of the time that at least one transaction was in storage.EPILOG field name: % Res

RPGN 0 - 100 OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PCTRSVDL or

PRSV

Percent of the time during the interval that a shared device was reserved by another processor or a control unit was busy with another path.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PCTTPI or

PTPI

Percent of the total I/O interrupts handled with the TPI instruction during the interval.EPILOG field name: %TPI


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PCTX See PCTCMPLX.PDATTIME The date and time of the COMPEXT

command.PGNCOMP, BTCHCOMP, STCCOMP, TSOCOMP



PDSFLAG If the page dataset is found to be unusable, bit 0 of this field is set to 1.

RPDS 0 or 1 in bit 0 OBTAIN, EXTRACT

F, 4 X, 4 H, 8 RIF

PEDATTIM The date and time of the interval end for the profile.




PENDTIMEor

PTIM

The average time (in milliseconds) that an I/O spent in the pending condition.EPILOG field name: Pend


OBTAIN, EXTRACT

F,4 I,4 N,10 RIF

Data D

ictionary263




wordsSASOBTAIN

INT COL, PC

PERF Performance group number. See also the data element PGN.EPILOG field name: PGN

RPGN Positive integers

OBTAIN ____ I, 2 N, 10 RIF (for resources)None (for workloads)

PERFINDX or

PIDX

The performance index. RSCL 0.000-4294967.295

OBTAIN, EXTRACT’DISPLAY

F, 4 U, 4 N, 11 RIF

PERIODor

PRD

Performance group period. See also the data element PGP. For data collected in WLM goal mode, this field refers to the performance period of the service class.EPILOG field name: PGP or Period (if in WLM goal mode)

RPGN, SCLDETL

Positive numbers

OBTAIN ____ I, 4 N, 10 RIF (for resources)None (for workloads)

PERIODCT or

PRCT

The number of service class periods. RSCL 0-8 OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

PERIODNM or

PDNM

The period number. RSCL 0-8 OBTAIN, EXTRACT

C, 1 C, 1 C, 1 RIF

PFLT See SRPAGFLT.PFUL See PCTFULL.PGDL See SRPAGDLY.PGIO See PAGPERIO.PGMNAME Batch job or started task program name. For

COMPEXT data, this field refers to the batch job or started task in the workload, not the profile. A value of N/A is displayed if the program name was not available at the time that the job was being monitored. This normally occurs for jobs in allocation wait prior to execution.

BTCHDETL, BTCHCOMP, STCDETL, STCCOMP


C, 8 C, 8 C, 8 None



wordsSASOBTAIN

INT COL, PC

PGN Performance group number. For COMPEXT data, this field refers to the performance group in the workload, not the profile. See also the data element PERF.

PGNDETL, PGNCOMP, RPGN

Positive integers


PGNFLAG Indicates whether the CPU speed was recorded for the interval (0 = recorded, 64 = not recorded). Since OBTAIN values are formatted as hexadecimal, the “not recorded” indicator will appear as 40, the hexadecimal equivalent of 64.

RPGN Bit string OBTAIN, EXTRACT

F, 4 X, 4 H, 8 None

PGNTYPE Performance group type. For COMPEXT data, this field refers to the performance group in the workload, not the profile.

PGNDETL, PGNCOMP

For OBTAIN, the values are:C = ControlR = ReportFor EXTRACT and COMPEXT, the values are:CONTROL PGN, or REPORT PGN

OBTAIN, EXTRACT

C, 11 C, 1 C, 1 None

PGP Performance group period. For profile/workload comparisons, this refers to the performance period of the workload, not the profile. See also the data element PERIOD.

PGNDETL, PGNCOMP, RPGN

Positive numbers


PGPRSWPIor

PPSI

Average number of pages per address space swap-in.EPILOG field name: InEnvironment: XA, ESA (non-expanded storage only)

RSWA Positive real numbers

OBTAIN, EXTRACT

F, 4 I, 4 N,11 RIF

Data D

ictionary265




wordsSASOBTAIN

INT COL, PC

PGPRSWPO or

PPSO

Average number of pages per address space swap-out.EPILOG field name: OutEnvironment: XA, ESA (non-expanded storage only)

RSWA Positive real numbers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PGS See PAGES.PIDX See PERFINDX.PIOPRSEC

or PIOS

Average EXCPs per second for the performance group (as counted by SM F).EPILOG field name: EXCPs/sec


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PIOS See PIOPRSEC.PJESCLAS Batch job execution class for the profile. BTCHCOMP Valid

execution classes

COMPEXT C, 4 ____ ____ None

PJOBNAME Batch job name for the profile. BTCHCOMP User-defined COMPEXT C, 7 ____ ____ NonePMVS See PCTCPMVS.PDNM See PARTNUM.PNUM See PERIODNM.POLACTDT

or DACT

The date that the service policy was activated.

RSCL Positive integers

OBTAIN, EXTRACT

C, 8 P, 4 N, 8 None

POLACTTM or

TACT

The time that the service policy was activated.

RSCL Positive integers

OBTAIN, EXTRACT

C, 8 T,4 C, 8 None

POLDESC or

POLD

The service policy description. RSCL Valid service policy description

OBTAIN, EXTRACT

C, 32 C, 32 C, 32 RIF

POLNAME or

POLN

The service policy name. RSCL Valid service policy description

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 RIF



wordsSASOBTAIN

INT COL, PC

POLSWTCH or

PLSW

Service policy switch indicator. RSCL 0 = No switch1 = Switch occurred

OBTAIN, EXTRACT

C, 1 C, 1 C, 1 RIF

PPGMNAME Batch job or started task program name for the profile.

BTCHCOMP, STCCOMP

User-defined COMPEXT C, 8 ____ ____ None

PPGN Performance group number for the profile. PGNCOMP Positive real numbers


PPGNTYPE Performance group type for the profile. PGNCOMP CONTROL PGN or REPORT PGN


PPGP Performance group period for the profile. PGNCOMP Positive real numbers


PPRODIDX Productivity index of the profile. For an explanation of the productivity index, see the description of the PRODIDX data element.

PGNCOMP, BTCHCOMP, STCCOMP, and TSOCOMP

1 - 100 COMPEXT F, 4 ____ ____ None

PPSI See PGPRSWPI.PPSO See PGPRSWPO.PRCNTRSP

or PCRT

The response time percentile completed in one tenths of a millisecond.

RSCL 0.0-429496729.5

OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

PRCNTTXNor

PCTG

The percentage of transactions within a goal. RSCL 0.0-100.0 OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

PRCT See PERIODCT.PRD See PERIOD.PRES See PCTRES.PRMC See PCTPRMCP.

Data D

ictionary267




wordsSASOBTAIN

INT COL, PC

PROCNAME Batch job or started task procedure name. BTCHDETL, STCDETL


C, 8 C, 8 C, 8 None

PRODIDX Productivity index. This is a general indicator of how severely the workload is being degraded. It is derived by dividing the amount of time spent doing productive work (such as active I/O or using CPU) by the total amount of time spent in productive and unproductive activities. Idle time (such as STIMER waits) is disregarded in the calculation, since it is not relevant to performance degradation.For COMPEXT data, this data element contains the productivity index of the workload, not the profile.

PGNDETL, BTCHDETL, STCDETL, TSODETL, PGNCOMP, BTCHCOMP, STCCOMP, TSOCOMP, RCLDETL, SCLDETL

1 - 100 OBTAIN, EXTRACT

F, 4 F, 4 F, 4 None

PROFNAME Profile name. PGNCOMP, BTCHCOMP, STCCOMP, TSOCOMP

User-supplied COMPEXT C, 16 ____ ____ None

PRTA See PCTPARTA.PRTC See PCTPRTCP.PRSV See PCTRSVDL.PSDATTIM Date and time of interval start for the profile. PGNCOMP,




PSMFID SMF ID for the profile. Up to five IDs may be included.


Valid SMD IDs


PSRB See PCTCPSRB.PSTCNAME Started task name for the profile. STCCOMP User-defined COMPEXT C,8 ____ ____ NonePSW See PSWPRSEC.



wordsSASOBTAIN

INT COL, PC

PSWPRSECor

PSW

Physical swap rate (in pages per second).EPILOG field name: Physical or Phys Swaps per sec:

RSWA, RSWR

Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

PSYMBNAM Symbolic name of the performance group, if one was defined during installation, for the profile.

PGNCOMP 8-character descriptive name


PTCB See PCTCPTCB.PTIM See PENDTIME.PTN See PARTNAME.PTPI See PCTTPI.PTSOUSER TSO user ID in the profile record. TSOCOMP User-defined COMPEXT C, 7 ____ ____ NonePUSE See PCTINUSE.PWAITPCT For performance group data, this data

element contains the percent of average transaction response time spent on this wait reason for the profile. For batch jobs, started tasks, and TSO sessions, it contains the percent of average elapsed time spent on this wait reason for the profile.




PTIM See PENDTIME.PWAITTME For performance groups, this data element

contains the average transaction response time spent on this wait reason for the profile (in seconds). For batch jobs, started tasks, and TSO sessions, it contains the average elapsed time spent on this wait reason for the profile (in seconds).




PWT See PARTWGT.

Data D

ictionary269




wordsSASOBTAIN

INT COL, PC

PWKLNAME Workload name for the profile. PGNCOMP, BTCHCOMP, STCCOMP, TSOCOMP

For performance groups, valid workload names are:ALL SYSTEM, PERIOD, SYMBOLIC PGN, or PGNFor batch jobs, started tasks, and TSO sessions, valid workload names are:ACCOUNT NUM, PROGRAM NAME, BATCH CLASS, BATCH JOB/ STARTED TASK/TSO USER ID

COMPEXT C, 12 ____ ____ RIF, SIF

QTIM See IOSQTIME.RA01 See RSPBKA01.RA02 See RSPBKA02.RA03 See RSPBKA03.RA04 See RSPBKA04.RA05 See RSPBKA05.RA05 See RSPBKA05.



wordsSASOBTAIN

INT COL, PC

RA06 See RSPBKA06.RA07 See RSPBKA07.RA08 See RSPBKA08.RA09 See RSPBKA09.RA10 See RSPBKA10.RA11 See RSPBKA11.RA12 See RSPBKA12.RA13 See RSPBKA13.RA14 See RSPBKA14.RCTTIM

or RTIM

RCT time in microseconds. RCLDETL, SCLDETL

Positive integers

OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RDHITCFW or

RHCF

The total cache fast write read hit percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3990/2105 subsystem.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

RDHITNM1or

RHN1

The normal read hit percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3880 first storage director or the 3990/2105 subsystem.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

RDHITNM2or

RHN2

The normal read hit percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3880 second storage director.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

RDHITSQ1 or

RHS1

The sequential read hit percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3880 first storage director or the 3990/2105 subsystem.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

Data D

ictionary271




wordsSASOBTAIN

INT COL, PC

RDHITSQ2 or

RHS2

The sequential read hit percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3880 second storage director.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

RDHITTOTor

RHTT

The total read hit percentage for a cache device, expressed in tenths of a percent.EPILOG field name: Read Hit %


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

RDRTIME Time (in seconds) that the job waited on the input queue either for the job to start, or, if the EXTRACT was done at the step level, for the step to start.

BTCHDETL Positive integers

OBTAIN, EXTRACT

F, 4 D, 4 N, 10 None

RDWR See RDWRTRT.RDWRTRT

or RDWR

The percentage of total read and write operations that involve read processing.EPILOG field name: R/W %

RCCH Positive integers or the negative integer -2147483648

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

READYIN or

RIN

Average number of ready users that were observed as “swapped-in” during the interval. If RMF-based intervals were combined into larger intervals, this figure reflects the larger combined interval.EPILOG field name: Ready Users In


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

READYOUTor

ROUT

Average number of ready users that were observed as “swapped-out” during the interval. If RMF-based intervals were combined into larger intervals, this figure reflects the larger combined interval.EPILOG field name: Ready Users Out


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

REAL Average real frame counts (in 4K frames).EPILOG field name: Real


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 None



wordsSASOBTAIN

INT COL, PC

REPTCNTL Performance group type flag.EPILOG field name: None

RPGN R = report performance group,C = control performance group

OBTAIN, EXTRACT

C, 1 C, 1 C, 1 RIF

RESGDESC or

RSGD

The resource group description. RSCL Valid resource group description

OBTAIN, EXTRACT

C, 32 C, 32 C, 32 RIF

RESGMAXor

RGMX

The resource group maximum capacity. RSCL Valid unsigned number

OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RESGMIN or

RGMN

The resource group minimum capacity. RSCL Valid unsigned number

OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RESGNAME or

RSGN

The resource group name. RSCL Valid resource group name

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 RIF

RESP Average response time for a transaction (in milliseconds). See also the data element AVG RESP.


EXTRACT F, 4 ____ ____ RIF

RESPUNIT or

RUNT

The response time goal units. RSCL, SCLDETL

0 - 4 OBTAIN, EXTRACT

C, 1 C, 1 C, 1 RIF

RGMN See RESGMIN.RGMX See RESGMAX.RHCF See RDHITCFW.RHN1 See RDHITNM1.RHN2 See RDHITNM2.RHS1 See RDHITSQ1.

Data D

ictionary273




wordsSASOBTAIN

INT COL, PC

RHS2 See RDHITSQ2.RHTT See RDHITTOT.RIN See READYIN.RLCU See DLCUID.RM01 See RSPBKT01.RM02 See RSPBKT02.RM03 See RSPBKT03.RM04 See RSPBKT04.RM05 See RSPBKT05.RM06 See RSPBKT06.RM07 See RSPBKT07.RM08 See RSPBKT08.RM09 See RSPBKT09.RM10 See RSPBKT10.RM11 See RSPBKT11.RM12 See RSPBKT12.RM13 See RSPBKT13.RM14 See RSPBKT14.RMF RMF version number.

EPILOG field name: RMFRINF Valid RMF

version numbers

OBTAIN, EXTRACT

C, 20 C, 20 C, 20 RIF

ROUT See READYOUT.RSGD See RESGDESC.RSGN See RESGNAME.RSPBKA01

or RA01

Response time bucket 01 transactions. RSCL Valid unsigned number

OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF



wordsSASOBTAIN

INT COL, PC

RSPBKA02 or

RA02


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKA03 or

RA03


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKA04 or

RA04


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKA05 or

RA05


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKA06or

RA06


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKA07 or

RA07


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKA08 or

RA08


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKA09 or

RA09


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKA10 or

RA10


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKA11 or

RA11


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

Data D

ictionary275




wordsSASOBTAIN

INT COL, PC

RSPBKA12or

RA12


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKA13 or

RA13


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKA14 or

RA14


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKT01 or

RM01

Response time map bucket 01. RSCL Valid unsigned number

OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKT02 or

RM02


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKT03or

RM03


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKT04or

RM04


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKT05 or

RM05


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKT06 or

RM06


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKT07 or

RM07


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF



wordsSASOBTAIN

INT COL, PC

RSPBKT08orRM08


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKT09 or

RM09


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKT10 or

RM10


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKT11 or

RM11


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKT12 or

RM12


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKT13 or

RM13


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RSPBKT14 or

RM14


OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

RTIM See RCTTIM.SAVG See STCAVGAS.SCFF See SRBCOEFF.SCRG See SCRSGNAM.SCRSGNAM

or SCRG

Name of resource group that service class is associated with through workload classification.

SCLDETL Valid resource group name

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 None

Data D

ictionary277




wordsSASOBTAIN

INT COL, PC

SCWKLNAMorSCWL

Name of workload that service class is associated with through workload classification.

SCLDETL Valid workload name

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 None

SCWL See SCWKLNAM.SDATE Start date. The date value for the start of the

interval that covers this OBTAIN record. This data element contains a time value. If multiple RMF-based intervals are being combined into larger intervals, this figure reflects the start date of the larger combined interval.


Positive integers

OBTAIN ____ P, 4 N, 8 None

SDATTIME Date and time of interval start (for SAS data only). For COMPEXT data, this field applies to the workload, not the profile. If multiple RMF-based intervals are being combined into larger intervals, this figure reflects the start date and time of the larger combined interval. This data element contains a standard SAS date/time value.

All SAS datasets

Positive integers

EXTRACT F,8 ____ ____ None

SDSFLAG Indicates the swap dataset condition. If the X’80’ bit is on, ASM has found the swap dataset to be unusable.

RSDS Bit indicator OBTAIN, EXTRACT

F, 4 X, 4 H, 8 RIF

SERVDEF or

DEF

Service Definition in effect.EPILOG field name: Service Definition

RINF User-defined OBTAIN, EXTRACT

C, 8 C, 8 C, 8 RIF

SERVPOL or

POL

Service Policy in effect.EPILOG field name: Service Policy

RINF User-defined OBTAIN, EXTRACT

C, 8 C, 8 C, 8 RIF

SMAX See STCMAXAS.SMFID The SMF ID of the system on which the data

was collected. For COMPEXT data, this field applies to the workload, not the profile.

All Valid SMF IDs OBTAIN, EXTRACT

C, 4 C, 4 C, 4 None



wordsSASOBTAIN

INT COL, PC

SMIN See STCMINAS.SPCTYPE

or STYP

Page space type.EPILOG field name: Space Type

RPDS Valid space types are: PLPA, COMMON, DUPLEX, LOCAL, or SWAP

OBTAIN, EXTRACT

C, 6 C, 6 C, 6 RIF

SPS See SWAPS.SRASMQ

or ASMQ

Average ASM queue length, as calculated by SRM.EPILOG field name: ASMQ


OBTAIN, EXTRACT

F, 4 I, 4 I, 10 RIF

SRBCOEFFor

SCFF

The SRB Coefficient*10,000. RSCL Valid unsigned number

OBTAIN, EXTRACT

F, 4 U, 4 N, 11 RIF

SRBP See SRBPCT.SRBPCT

or SRBP

Percent of CPU used by SRBs in the performance group.EPILOG field name: SRB%


F, 4 U, 4 N, 11 RIF

SRCPUor

ACPU

Average percent CPU utilization, as calculated by SRM.EPILOG field name: CPU


OBTAIN, EXTRACT

F, 4 I, 4 I, 10 RIF

SRDMDPAGor

DPGR

Demand paging rate (non-swap, non-VIO page-ins plus reclaims) in pages per second.EPILOG field name: Dmand Pging

RSRM Positive real numbers

OBTAIN, EXTRACT

F, 4 I, 4 I, 10 RIF

SRFIXB16or

FXB

Percent of the first 16M of real storage that was fixed (that is, non-pageable).EPILOG field name: % of Frames Fixed Below 16M

RSRM 0 - 100 OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

Data D

ictionary279




wordsSASOBTAIN

INT COL, PC

SRFIXTOT or

FXT

Percent of total real storage that was fixed (that is, non-pageable).EPILOG field name: % of Frames Fixed Total

RSRM 0 - 100 OBTAIN, EXTRACT

F, 4 I, 4 N, 10 None

SRMVALS or

SRVS

SRM MPL adjustment values and observed values.EPILOG field name: SRM parameters and observed values

RSRM The five allowed values are: HIGH THRESHOLD, LOW THRESHOLD, OBSERVED MAX, OBSERVED MIN, and OBSERVED AVG

OBTAIN, EXTRACT

C, 16 C, 14 C, 14 RIF

SRPAGDLYor

PGDL

Page delay time (excluding swap paging) in milliseconds, as calculated by SRM.EPILOG field name: Page Delay


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

SRPAGFLT or

PFLT

Page fault rate (non-swap, non-VIO page-ins plus page-outs) in pages per second.EPILOG field name: Page Fault


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

SRUIC or

AUIC

Average unreferenced interval count, as calculated by SRM.EPILOG field name: UIC

RSRM Positive real numbers

OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

SRVS See SRMVALS.SRVU See INTVLSRV.SSYS See SUBSYSID.



wordsSASOBTAIN

INT COL, PC

STCAVGAS or

SAVG

The average number of started tasks running concurrently during the interval. If multiple RMF-based intervals were combined into larger intervals, this figure reflects the number of started tasks running during the larger combined interval.EPILOG field name: STG Avg


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

STCMAXAS or

SMAX

The maximum number of started tasks running concurrently during the interval. If multiple RMF-based intervals were combined into larger intervals, this figure reflects the number of started tasks running during the larger combined interval. STCMAXAS data elementEPILOG field name: STC Max


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

STCMINAS or

SMIN

The minimum number of started tasks running concurrently during the interval. If multiple RMF-based intervals were combined into larger intervals, this figure reflects the number of started tasks running during the larger combined interval.EPILOG field name: STC Min


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

STCNAME The name of the started task. For COMPEXT data, this refers to the started task name in the workload, not the profile.

STCDETL, STCCOMP

Positive integers

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 None

STD1 See STGDIR1.STD2 See STGDIR2.STEPNAME Batch job or started task step name. BTCHDETL,

STCDETLUser-defined OBTAIN,

EXTRACTC, 8 C, 8 C, 8 None

STGDIR1or

STD1

The first storage director. (3880 only)EPILOG field name: Stg Dir

RCCH Hexadecimal digit, 00 to FF

OBTAIN, EXTRACT

C, 2 C, 2 C, 2 RIF

Data D

ictionary281




wordsSASOBTAIN

INT COL, PC

STGDIR2or

STD2

The second storage director. (3880 only)EPILOG field name: Stg Dir

RCCH Hexadecimal digit, 00 to FF

OBTAIN, EXTRACT

C, 2 C, 2 C, 2 RIF

STIME Start time. The time value for the start of the interval that covers this OBTAIN record. This data element contains a time value. If multiple RMF-based intervals are being combined into larger intervals, this figure reflects the start time of the larger combined interval.


Positive integers

OBTAIN ____ T, 4 C,8 None

STORNAME Name of storage area that is mapped.EPILOG field name: storage areas

RPAG One of the following areas of storage:SQA, CSA, LPA, LSQA,PVT, FREE, NUC,TOTAL,EPVT, ECSA, ELPA, ESQA, orEXP. STOR.

OBTAIN, EXTRACT

C, 6 C, 12 C, 12 None

STYP See SPCTYPE.SUBSYSID

orSSYS

The cache device subsystem id. (3990/2105 only)EPILOG field name: SSID

RCCH Hexadecimal digit, 0000 to FFFF

OBTAIN, EXTRACT

C, 4 C, 4 C, 4 RIF

SUPERSEC or

SUPS

Average SRM service units used per second.EPILOG field name: SUs/Sec


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF



wordsSASOBTAIN

INT COL, PC

SUPS See SUPERSEC.SWAPERTX

or SWTX

Average number of swaps per transaction.EPILOG field name: Swaps/Trx


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

SWAPIN Average number of pages swapped in per second.EPILOG field name: Swap paging/sec InEnvironment: XA, ESA (non-expanded storage)


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 None

SWAPOUT Average number of pages swapped out per second.EPILOG field name: Swap paging/sec OutEnvironment: XA, ESA (non-expanded storage)


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 None

SWAPS or

SPS

Average number of pages swapped per second (swap-ins plus swap-outs).


OBTAIN ____ I, 4 N, 11 None

Data D

ictionary283




wordsSASOBTAIN

INT COL, PC

SWPCATG or

CAT

Swap category.EPILOG field name: Swap Category

RSWR These are the swap categories:

TERMINALWAIT,DETECTEDLONGTHINK,LONG WAIT,DETECTEDWAIT,EXCHANGE,UNI- LATERAL,REQUEST,ENQ EXCHANGE,AUX STORAGE SHORTAGE,REAL STORAGE SHORTAGE,

=====>

OBTAIN, EXTRACT

C, 21 C, 21 C, 21 RIF



wordsSASOBTAIN

INT COL, PC

=====>SWPCATG

TRAN- SITION TO NONSWAPCENTRAL STORAGE (MVS/SP 4.2 and above),SYSTEM PAGING (MVS/SP 4.2 and above),OUT TOO LONG (MVS/SP 4.2 and above),APPC WAIT (MVS/SP 4.2 and above),TOTAL PHY SWAPS / SEC., OM1,and OM2 (MVS/SP 5.1 and above)

SWTX See SWAPERTX.SYMBNAME Symbolic name of the performance group, if

one was defined during installation. For COMPEXT data, this field refers to the performance group in the workload, not the profile.

PGNDETL, PGNCOMP

8-character descriptive name

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 None

SYS See SYSLEVEL.SYSLEVEL

or SYS

Operating system level, for example, MVS SP3.1.0.EPILOG field name: Operating System and Level

RINF Valid operating system levels

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 RIF

Data D

ictionary285




wordsSASOBTAIN

INT COL, PC

TACT See POLACTTM.TARGMPL

or TDM

Target MPL specified for the domain in the IPS.EPILOG field name: Tar MPL


OBTAIN, EXTRACT

F, 4 I,4 N,11 RIF

TAVG See TSOAVGAS.TCBP See TCBPCT.TCBPCT

orTCBP

Percent of CPU used by TCBs in the performance group.EPILOG field name: TCB%


F, 4 I,4 N,11 RIF

TCDN See CCHDASDN.TDCN See DASDCCHN.TDCS See DASDCCHS.TDM See TARGMPL.TESW See ESTSWPSC.TINS See DEFINSTM.TMAX See TSOMAXAS.TMIN See TSOMINAS.TOTCPUTM Total CPU time used by all transactions in the

interval (in seconds) . If multiple RMF-based intervals are being combined into larger intervals, this figure reflects the number of transactions in the larger combined interval.

PGNDETL Positive integers

OBTAIN, EXTRACT

F, 4 D, 4 N, 10 None

TOTIOTME or

TTME

The average end-to-end service time per I/O to the device (in milliseconds).EPILOG field name: Total

RDAS Positive real integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

TOTSTGK or

TSTG

Average amount of working set storage used by the performance group (in bytes).EPILOG field name: Total Stg


OBTAIN, EXTRACT

F,4 I,4 N,10 RIF



wordsSASOBTAIN

INT COL, PC

TOTVEL or

TVEL

Total delays considered for velocity. SCLDETL Postive number

OBTAIN, EXTRACT

F,4 U,4 N,11 RIF

TRANRATEor

TRAT

The transaction time. See TRANRUNT, which expresses the time units of the transaction rate.

RSCL Valid unsigned numbers


F,4 U,4 N,11 RIF

TRANRUNT or

TRTU

The time units in which the transaction rate is expressed. The transaction rate is contained in the data element TRANRATE.

RSCL 1 = transactions per day 2 = transactions per hour 3 = transactions per minute 4 = transactions per second


C,1 C,1 C,1 RIF

TRNSTIME or

TRTM

Average time required to complete a page transfer (in milliseconds).EPILOG field name: Trnsfr Time or Avg Srv Time

RPDS, RSDS Positive real numbers

OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

TRTM See TRNSTIME.TRXACT

or TRXA

Transaction active time (1024 microseconds).

SCLDETL, RCLDETL

Positive integers

OBTAIN, EXTRACT

C, 24 C, 24 C, 24 RIF

Data D

ictionary287




wordsSASOBTAIN

INT COL, PC

TRXELAPor

TRXE

Total transaction time for performance group data, or total elapsed time for batch job, started task, or TSO ession data (in seconds). For COMPEXT data, this field refers to the batch job, started task, or TSO session elapsed time in the workload, not the profile.EPILOG field name: Elapsed

PGNDETL, BTCHDETL, STCDETL, TSODETL, BTCHCOMP, STCCOMP, TSOCOMP, SCLDETL, RCLDETL

Positive integers

OBTAIN, EXTRACT

F, 4 D, 8 N, 10 None

TRXEXEC or

TRXC

Transaction execution time (1024 microseconds).

SCLDETL, RCLDETL

Positive integers

OBTAIN, EXTRACT

C, 24 C, 24 C, 24 RIF

TRXRESP or

TRXR

Average transaction response time (in seconds). For COMPEXT data, this field refers to the performance group in the workload, not the profile.

PGNDETL, PGNCOMP, RCLDETL, SCLDETL

Positive integers

OBTAIN, EXTRACT

F, 4 D,4 N,10 None

TRXSYST or

TRXS

Transaction system time (1024 microseconds).

SCLDETL, RCLDETL

Positive integers

OBTAIN, EXTRACT

C, 24 C, 24 C, 24 RIF

TRXTHINK Average transaction think time (in seconds). PGNDETL Positive integers

OBTAIN, EXTRACT

F, 4 D, 4 N, 10 None

TSOAVGAS or TAVG

The average number of TSO users during the interval. If multiple RMF-based intervals are combined into larger intervals, this figure reflects the number of TSO users during the larger combined interval.EPILOG field name: TSO Avg


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

TSOMAXAS or

TMAX

The maximum number of TSO users during the interval. If multiple RMF-based intervals are combined into larger intervals, this figure reflects the number of TSO users during the larger combined interval.EPILOG field name: TSO Max


OBTAIN, EXTRACT

F, 4 D, 4 N, 10 RIF



wordsSASOBTAIN

INT COL, PC

TSOMINASor

TMIN

The minimum number of TSO users during the interval. If multiple RMF-based intervals are combined into larger intervals, this figure reflects the number of TSO users during the larger combined interval.EPILOG field name: TSO Min


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

TSOUSER The TSO user ID. For COMPEXT data, this refers to the TSO user ID in the workload, not the profile.

TSODETL, TSOCOMP

Positive integers

OBTAIN, EXTRACT

C, 7 C, 7 C, 7 None

TSTG See TOTSTGK.TSWP See TSWPSEC.TSWPSEC

or TSWP

Number of transition swaps per second. Transition swaps are swap-outs of address spaces that were already marked as logically swapped when the physical swap-out was made.EPILOG field name: Transition

RSWA, RSWR


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

TTME See TOTIOTME.TVEL See TOTVEL.TXIN See AVGTRXIN.UBSY See CUPCTBSY.UDEF See CUDEFSEC.VELOCITY

or VELO

The average velocity. RSCL, SCLDETL

0.0-100.0 OBTAIN, EXTRACT,DISPLAY

F, 4 U, 4 N, 11 RIF

VLFA See VLFADDS.VLFADDS or VLFA

The number of objects in this class that were added to virtual storage during the interval.EPILOG field name: AddEnvironment: ESA 3.1 and above

RVLF Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

VLFC See VLFCLASS.

Data D

ictionary289




wordsSASOBTAIN

INT COL, PC

VLFCLASS or

VLFC

The name of this class.EPILOG field name: VLF ClassEnvironment: ESA 3.1 and above

RVLF User-defined OBTAIN, EXTRACT

C, 8 C, 8 C, 8 RIF

VLFD See VLFDELES.VLFDELES

orVLFD

The number of objects in this class that were deleted from virtual storage during the interval.EPILOG field name: DeleteEnvironment: ESA 3.1 and above


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

VLFF See VLFFULL.VLFFULL

or VLFF

The storage used by objects in this class, divided by the maximum storage available for objects in this class, expressed as a percentage in tenths of a percent.Environment: ESA 3.1 and above

RVLF 1-100 OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

VLFH See VLFHITS.VLFHITS

or VLFH

The number of times an object in this class was found in cache, divided by the number of times cache was searched for objects in this class, expressed as a percentage in tenths of a percent.EPILOG field name: Hit %Environment: ESA 3.1 and above

RVLF 1-100 OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

VLFL See VLFLRGST.VLFLRGST

orVLFL

The size of the largest object which VLF attempted to load into virtual storage.EPILOG field name: ObjectEnvironment: ESA 3.1 and above


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

VLFM See VLFMXSTG.



wordsSASOBTAIN

INT COL, PC

VLFMXSTG or

VLFM

The maximum number of virtual storage pages that this class can use.EPILOG field name: MaximumEnvironment: ESA 3.1 and above


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

VLFR See VLFRATE.VLFRATE

orVLFR

The number times cache was searched for an object in this class during an interval, divided by the number of seconds in the interval.EPILOG field name: Reads/secEnvironment.: ESA 3.1 and above


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

VLFT See VLFTRIMS.VLFTRIMS

or VLFT

The number of objects in this class that were trimmed from virtual storage during the interval.EPILOG field name: TrimEnvironment: ESA 3.1 and above


OBTAIN, EXTRACT

F, 4 I,4 N, 10 RIF

VLFU See VLFVSUSD.VLFVSUSD

or VLFU

The number of pages of virtual storage used by this class.EPILOG field name: UsedEnvironment: ESA 3.1 and above


OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

VIRT Virtual storage (in kilobytes). Used in conjunction with STORNAME.EPILOG field name: Virtual Storage

RPAG Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 10 None

VOLS See VOLSER.

Data D

ictionary291




wordsSASOBTAIN

INT COL, PC

VOLSERorVOLS

Volume serial number.EPILOG field name: Volume Serial or VOLSER

RCCH, RDAS, RPDS, RSDS, PGNDETL, BTCHDETL, STCDETL, TSODETL, PGNCOMP, BTCHCOMP, STCCOMP, TSOCOMP, RCLDETL, SCLDETL

Valid volume serial numbers

OBTAIN, EXTRACT

C, 6 C, 6 C, 6 RIF (resource)None (workloads)

WAITNAME Detail wait reason. PGNDETL, BTCHDETL, STCDETL, TSODETL, PGNCOMP, BTCHCOMP, STCCOMP, TSOCOMP, RCLDETL, SCLDETL

Detail wait reason codes are defined in the entry for the EXWAIT keyword. For COMPEXT data, a blank DEVADD for ACTIVEIO, QUEUEDIO, or RESRVEIO signifies that the observation is a composite of all the extracted data for the wait reason and is not device specific.

OBTAIN, EXTRACT

C, 10 C, 20 C, 20 None

Data Element Description Tables Valid Values CommansData Type and Length Filter

Key-

wordsSAS

OBTAIN

INT COL, PC

WAITPCT Percent of the average transaction time spent on this wait reason. For COMPEXT data, this field applies to the workload, not the profile.


Positive integers

OBTAIN, EXTRACT

F, 4 D, 4 N, 10 None

WAITTIME Average transaction time spent on this wait reason (in seconds). For COMPEXT data, this field applies to the workload, not the profile.


Positive integers

OBTAIN, EXTRACT

F, 4 D, 4 N, 10 None

WHCF See WRHITCFW.WHDN See WRHITDFN.WHDS See WRHITDFS.WHDT See WRHITDFT.WHN1 See WRHITNM1.WHN2 See WRHITNM2.WHSQ See WRHITSEQ.WHTT See WRHITTOT.

Data D

ictionary293




wordsSASOBTAIN

INT COL, PC

WKLNAME Workload name. PGNDETL, BTCHDETL, STCDETL, TSODETL, PGNCOMP, BTCHCOMP, STCCOMP, TSOCOMP

For performance groups, valid workload names are:ALL SYSTEM,PERIOD,SYMBOLIC PGN, and PGN.For batch jobs, started tasks, and TSO sessions, valid workload names are:ACCOUNT NUM,PROGRAM NAME,BATCH CLASS, and BATCH JOB/ STARTED TASK/TSO USER ID.

OBTAIN, EXTRACT

C, 12 C, 12 C, 12 None

WLMMODE or

MODE

Workload Manager mode: compatibility (c) or goal (g)EPILOG field name: WLM Mode

RINF compatibility or goal

OBTAIN, EXTRACT

C, 1 C, 1 C, 1 RIF

WRHITCFW or

WHCF

The cache fast write write hit percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3990/2105 subsystem.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF



wordsSASOBTAIN

INT COL, PC

WRHITDFN or

WHDN

The DASD fast write normal write hit percentage for a cache device expressed in tenths of a percent. This tatistic comes from the 3990/2105 subsystem.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

WRHITDFS or

WHDS

The DASD fast write sequential write hit percentage for a cache device, expressed in tenths of a percent. This tatistic comes from the 3990/2105 subsystem.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

WRHITDFTor

WHDT

The total DASD fast write write hit percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3990/2105 subsystem.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

WRHITNM1 or

WHN1

The normal write hit percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3880 first storage director or the 3990/2105 subsystem.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

WRHITNM2 or

WHN2

The normal write hit percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3880 second storage director.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

WRHITSEQ or

WHSQ

The sequential write hit percentage for a cache device, expressed in tenths of a percent. This statistic comes from the 3990/2105 subsystem.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

WRHITTOT or

WHTT

The total write hit percentage for a cache device, expressed in tenths of a percent.EPILOG field name: Write Hit %


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

WRITENM1 or

WRN1

The normal write requests for a cache device, expressed in tenths of a write per second. This statistic comes from the 3880 first storage director.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

WRITENM2 or

WRN2

The normal write requests for a cache device, expressed in tenths of a write per second. This statistic comes from the 3880 second storage director.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

Data D

ictionary295




wordsSASOBTAIN

INT COL, PC

WRITESQ1 or

WRS1

The sequential write requests for a cache device, expressed in tenths of a write per second. This statistic comes from the 3880 first storage director.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

WRITESQ2or

WRS2

The sequential write requests for a cache device, expressed in tenths of a write per second. This statistic comes from the 3880 second storage director.


OBTAIN, EXTRACT

F, 4 I, 4 N, 11 RIF

WRKLDESC or

WKLD

The WLM workload description. RSCL Valid workload description

OBTAIN, EXTRACT

C, 32 C, 32 C, 32 RIF

WRKLNAMEor

WKLN

The WLM workload name. RSCL Valid workload name

OBTAIN, EXTRACT

C, 8 C, 8 C, 8 RIF

WRKNGSETor

WKGS

The number of working set frames occupied by an address space.


Positive integers

OBTAIN, EXTRACT

F, 4 I, 4 N, 10 RIF

WRN1 See WRITENM1.WRN2 See WRITENM2.WRS1 See WRITESQ1.WRS2 See WRITESQ2.

Guide to Candle Customer Support 297

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298– 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302– Assigned Support Center Representative (ASCR)

– Maintenance Assessment Services (MAS)

– Multi-Services Manager (MSM)

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

B

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 305

AA/S report class data element 229A/S server address space flag data element 230A/S service class data element 229ACCTCDE data element 229, 230, 231ACTRESP data element 229, 230Adobe portable document format 13AMATRIX 53A-matrix keywords 21analysis keywords, degradation 25analysis, automatic 21analysis, exception 28ASCR

assigned support center representative 302assigned support center representative

ASCR 302automatic analysis 21AVGCTRX data element 230AVGNSWAP data element 230AVGSTOR data element 230AVGTRXIN data element 230AVGUGOUT data element 230AVGUIN data element 231AVGUOUT data element 231AVGURDY data element 231AVGWKST data element 231

Bband|range keywords 23BATAVGAS data element 231batch data extract commands 21batch job degradation data keywords 21batch job degradation data, exporting 32batch utilities commands 22batch workload keywords 22BATMAXAS data element 231BATMINAS data element 231blinking displays 77BPSSCCH1 data element 232BPSSCCH2 data element 232buffer keywords for the REOPEN command 23

Ccache subsystem statisitics keyword 23CACHSTT1 data element 232CACHSTT2 data element 232

categories, summary wait 43categories, wait summary 44CCHDASDN data element 233CFRAMES data elemen 233channel resource keyword 23CHNTYPE data element 233CHPID data element 233CIOPRSEC data element 233CNTRLMOD data element 234codes, detail wait reason 25codes, wait reason 44codes, wait reasons

See wait reason codes, EPILOGcodes, wait reasons

See wait reason codes, EPILOGcollector commands 23, 25commadns, EPILOG

RMAT 180command groupings 19commands, EPILOG

CMAT 65CMX 65CNTL 65COM 66COMPAREor COM 68COMPEXT or CMX 72CONTROL COLOR or CNTL COLOR 76CONTROL MODE or CNTL MODE 78CONTROL RECALL or CNTL RECALL 79CONTROL TITLE or CNTL TITLE 79CREATEM or CMAT 80D 84DAT 84DATASTOR 84DELETEM or DMAT 87DIS 88DISPLAY or DIS 88DMAT 90END 93EXT 97EXTRACT or EXT 98HELP 110INQ 112INQUIRE or INQ 112J 116LISTM or LMAT 121LMAT 122

Index


OBT 130OBTAIN or OBT 130P 142PAGESEP or PSEP 142PFK 146PRODUCTS 153PROF 153PROFILE or PROF 153PSEP 158QUIT 160R 163REOPEN 166REPLACEM or RMAT 167RES 175RESOURCE or RES 176S 187SET 190SETP 191STOP 199V 220W 220X 224

COMPEXT command, performance group degradation data keywords 36

CONNTIME data element 234CONTIDX data element 234CPBUSUSE data element 235CPCRRATE data element 235CPCTBUSY data element 235CPCWRATE data element 235CPLRRATE data element 235CPLTBUSY data element 235CPLWRATE data element 235CPPCTBSY data element 235CPU utilization keyword 23CPUFLAG data element 236CPUID data element 238CPUMODEL data element 238CPUSERL data element 238CPUSUS data element 238CPUTRXTM data element 238CSRVTIME data element 239CUDEFSEC data element 239CUID data element 239CUPCTBSY data element 239CURMPL data element 239customer support

base maintenance plan 298contact information 303enhanced support services 302eSupport 299severity levels 299

telephone support 298

DDASD resource keyword 23DASD, shared 42DASDCCHN data element 239DASDCCHS data element 240DASDFWST data element 240data extract, batch 21datastore maintenance commands 23, 25date and time keywords 23date keywords 23day keywords 24DCUBSY data element 240DDEVBSY data element 240DDEVPAVF data element 240DDEVPAVS data element 240DEFDESC data element 240DEFINSDT data element 240DEFINSTM data element 241DEFNAME data element 241DEFUSER data element 241degradation analysis keywords 25degradation data keywords for OBTAIN and

EXTRACT commands 36degradation data keywords for the COMPEXT

command 36degradation data keywords, batch job 21degradation, started task 43detail wait reason codes 25, 44DEVADD data element 241DFWBYPSS data element 241DIOPRSEC data element 242DISCTIME data element 242display resource 42display shared-DASD degradation 42DLCUID data element 242DOMNUM data element 242DPBUSY data element 242DPCTBSY data element 243DPCTBUSY data element 243DPRODIDX data element 243DSWPPHSC data element 243DSXAFLAG data element 243DTRXELAP data element 243DTRXRESP data element 243DWAITTME data element 244

EEDATE data element 244EDATTIME data element 244EFRAMES data element 244

Index 307

ENQNAME data element 245EPILOG commands 25

See comands, EPILOGSee commands EPILOGSee commands, EPILOG

EPILOG commands See commands, EPILOGEPILOG keyowrds

See keywords, EPILOGEPILOG keywords

See Keywords, EPILOGSee keywords, EPILOG 64

EPILOG operandsSee operands, EPILOG

EPILOG wait reason codesSee wait reason codes, EPILOGSee wait reasons codes, EPILOG

EPILOG, wait reason codesSee wait reason codes, EPILOG

ESASWPSC data element 245ESAVG data element 245ESDSWPSC data element 245ESFRREAL data element 245ESINST data element 246ESMAX data element 246ESMIGRAT data element 246ESMIN data element 246ESONLINE data element 246ESTOAUX data element 247ESTSWPSC data element 247eSupport

customer support 299ETIME data element 247exception analysis keywords 28exception filter reporting keywords 32exception, workload sfilter keywords 46exceptions, resource 34exceptions, workload 34exporting batch job degradation data 32exporting EPILOG data keywords 32exporting performance group degradation data 32exporting started task degradation data 33exporting TSO user session degradation data 33EXTDTIME data element 247EXTRACT and OBTAIN commands, performance

group degradation data keywords 36extract commands, batch data 21

Ffast-path navigation commands 33, 35filter keywords, workload exception 46filter, exception 32filter, resource exception filter 42filtering keyword for resource exceptions 34

filtering keywords for workload exceptions 34FIXED data element 247format, reporting 39

GGOALCHNG data element 248GOALDUR data element 248GOALIMP data element 248GOALRTU data element 248GOALTYPE data element 248GOALVAL data element 248GOALVALU data element 248grouping of commands 19

HHIGHSTEP data element 248historical commands 34historical reporting 34HOLD mode 79

II/O queuing information 35ICS data element 248INFFLAG data element 249information keyword, page dataset 36information keyword, paging 36information keywords, SRM 42information keywords, swapping 43information, I/O queuing 35INHBCCH1 data element 250INHBCCH2 data element 250INTVLSRV data element 250IOCOEFF data element 251IOCRATE data element 251IODEFSEC data element 251IOINTRPT data element 251IOPERSEC data element 251IOPIOQLN data element 251IOPIOSEC data element 251IOPROCID data element 251IOPTLDEF data element 252IORATE data element 252IOSQTIME data element 252IOSU data element 252IPS data element 252ITRGMPL data element 252

JJ 116JESCLASS data element 252JESNUM data element 253


job degradation data keywords, batch 21JOBNAME data element 253

Kkeywords

A-matrix 21band|range 23batch workload 22buffer 23cache subsystem statisitics 23channel resource 23CPU utilization 23DASD resource 23date 23date and time 23day 24degradation analysis 25exception analysis 28filtering 34page dataset information 36paging information 36performance group 36performance group degradation data for OBTAIN

and EXTRACT commands 36performance group degradation data for the

COMPEXT command 36performance group resource 37plot scale 37reporting format 39resource display 42shared-DASD degradation display 42SRM information 42started task degradation 43swapping information 43time 25, 43TSO user session degradation data 44VLF class statistics 44workload display options 45workload exception filter 46workload exceptions, filtering 34

keywords, EPILOGACCOUNT or ACCT 50ACCT 51ADD 53AMAT 53AMATRIX or AMAT 53APPEND 54AUTO 54AUTOMATIC or AUTO 54AVERAGE or AVG 57AVG 58BACK 60

BAND 60BLOCK 60BUFND 61BUFNI 61CLASS 64CLEAR 65CLS 65CMB 65CMPL 65COMBINE or CMB 66COMPLETE or CMPL 75DAY 85DAYOFWK or DAY 85DET 87DETAIL or DET 87DROP 90DUP 90DUPLICATE or DUP 90EDATE 92ELEM 92ELEMENTS or ELEM 92ELT 93ENDDATE or EDATE 93ENDTIME or ETIME 94EPILOG keywords 183ETIME 96EXD 97EXDATE or EXD 97EXW 100EXWAIT or EXW 100FOLDOFF 106FOLDON 106FORMAT 106INT 113INTERVAL or INT 113IODEV 114IODEVICE or IODEV 114JDAS 116JOB 117JOBNAME or JOB 117LASTMONTH or LMN 120LASTWEEK or LWK 120LASTYEAR or LYR 120LCNT 120LIM 120LIMIT or LIM 121LINECNT or LCNT 121LMN 122LOGOFF 122LOGON 122LWK 123LYR 123

Index 309

MAX 126MAXSCALE or MAX 126NOOUTLIER 130NOPLOT 130NOPRDX 130NOPRODIDX or NOPRDX 130OUTFILE 138OUTL 138OUTLIER or OUTL 138PDAS 143PER 144PERFGROUP or PGN 144PGM 148PGN 148PGP 149PGPERIOD or PGP 149PLOT 150PLOTMIN or PMIN 150PMIN 151PNAME 151PRDD 151PRDX 151PRDXDEF or PRDD 151PRODIDX or PRDX 153PROFNAME or PNAME 156PROGRAM or PGM 157RALL 163RANGE or RNG 163RCCH 163RCHN 164RCPU 164RDAS 165RDOM 166REPLACE 167REPORTIF or RIF 168REPTCLAS or RPC 175RESP 177RIF 177RINF 178RLCU 178RNG 180RPAG 180RPC 164RPDS 180RPGN 181RSCL 181RSDS 182RSRM 182RSWA 182RSWR 183RVLF 183SCL 187

SDATE 187See keywords, EPILOG 183SELECTIF or SIF 187SERVCLAS or SCL 189SHORT 193SIF 193SINGLE or SNG 194SNG 194STARTDATE or SDATE 194STARTTIME or STIME 196STARTTSK or STC 197STC 198STEP 198STIME 199SUM 199SUMD 199SUMDEF or SUMD 200SUMMARY or SUM 201SUMW 202SUMWAIT or SUMW 202SYM 204SYMBOLIC or SYM 204SYS 205SYSID or SYS 205SYSTEM or SYS 208TDAY 212TEST 212THISMONTH or TMN 212THISWEEK or TWK 212THISYEAR or TYR 212TITLE 213TITLE2 213TITLE3 214TMN 214TODAY or TDAY 214TOT 214TOTAL or TOT 215TSO 215TSOUSER or TSO 215TWAITOF 216TWAITOFF or TWAITOF 216TWAITON 216TWK 217TYR 217WORKLOAD or WKL 220XPG 224YDAY 226YESTERDAY or YDAY 226

keywords, epilogUSE 220


LLCUCPST data element 253LCUERROR data element 253LCUIOQLN data element 253LCUIOSEC data element 254LCUTYPE data element 254logical grouping of commands 19logical partitioning 236, 249LSWPRSEC data element 254LTPPRSEC data element 254

MMACHFLAG data element 255maintenance assessment service

MAS 302maintenance, datastore 23, 25MAS

maintenance assessment service 302MINMPL data element 255MODE data element 256MSM

multi-services manager 302MSOCOEFF data element 256MSOSU data element 256multi-services manager

MSM 302

NNAME data element 256navigation commands, fast-path 33, 35NMTR data element 256NONFIXED data element 256NUMICMB data element 257NUMPHYS data element 257NUMTRANS data element 257NUMTRX data element 257

OOBTAIN and EXTRACT commands, performance

group degradation data keywords 36OPENDSN data element 257operands, EPILOG

ELAP 92ELAPSED or ELAP 92MERGE 127RESPONSE or RESP 177

OPT data element 257OSLEVEL data element 258OTRGMPL data element 258

PPACCTCDE data element 258page dataset information keyword 36PAGEIN data element 258PAGEOUT data element 258PAGES data element 258paging information keyword 36PAGPERIO data element 258PARTNAME data element 259PARTNUM data element 259PARTWGT data element 259PAVGELAP data element 259PAVGTRX data element 259PCTCMPLX data element 259PCTCPMVS data element 260PCTCPTCB data element 260PCTCPU data element 260PCTFULL data element 261PCTINUSE data element 261PCTMGPLX data element 261PCTPARTA data element 261PCTPRMCP data element 261PCTPRTCP data element 262PCTRES data element 262PCTRSVDL data element 262PCTTPI data element 262PDATTIME data element 262PDSFLAG data element 262PEDATTIM data element 262PENDTIME data element 262PERF data element 263performance group degradation data keywords for

OBTAIN and EXTRACT commands 36performance group degradation data keywords for

the COMPEXT command 36performance group degradation data, exporting 32performance group keywords 36performance group resource keyword 37PERIOD data element 263PERIODCT data element 263PERIODNM data element 263PGMNAME data element 263PGN data element 264PGNFLAG data element 264PGNTYPE data element 264PGP data element 264PGPRSWPI data element 264PGPRSWPO data element 265PIOPRSEC data element 265PJESCLAS data element 265PJOBNAME data element 265plot scale keyword 37

Index 311

POLACTDT data element 265POLACTTM data element 265POLDESC data element 265POLNAME data element 265POLSWTCH data element 266PPGMNAME data element 266PPGN data element 266PPGNTYPE data element 266PPGP data element 266PPRODIDX data element 266printing problems 14PROCNAME data element 267PRODIDX data element 267PROFNAME data element 267PSDATTIM data element 267PSMFID data element 267PSTCNAME data element 267PSWPRSEC data element 268PSYMBNAM data element 268PTSOUSER data element 268PWAITPCT data element 268PWAITTME data element 268PWKLNAME data element 269

Qqueuing information, I/O 35

Rrange|band keywords 23RCTTIM data element 270RDHITCFW data element 270RDHITNM1 data element 270RDHITNM2 data element 270RDHITSQ1 data element 270RDHITSQ2 data element 271RDHITTOT data element 271RDRTIME data element 271RDWRTRT data element 271READYIN data element 271READYOUT data element 271REAL data element 271reason codes, wait 25

See wait reason codes, EPILOGreason codes, wait detail 44REOPEN command, buffer keywords 23reporter commands 25, 37reporting format keywords 39reporting keywords, exception filter 32reporting utility commands 41reporting with SAS commands 41reporting, historical 34reporting, utility 27

REPTCNTL data element 272RESGDESC data element 272RESGMAX data element 272RESGMIN data element 272RESGNAME data element 272resource display keywords 42resource exception filter keyword 42resource exceptions, filtering keyword 34Resource group name associated with service class

name data element 276resource keyword, DASD 23resource, channel 23resource, performance group 37RESP data element 272RESPUNIT data element 272reverse displays 77RMF data element 273ROLL mode 79

SSAS, reporting 41SDATE data element 277SET 190severity levels

customer support 299shared-DASD degradation display keywords 42started task degradation data keywords 43started task degradation data, exporting 33statistics, cache subsystem 23statistics, VLF class 44summary wait categories 43summary, wait categories 44swapping information keywords 43

Ttelephone support

customer support 298time and date keywords 23time keywords 25, 43TSO user session degradation data keywords 44TSO user session degradation data, exporting 33

Uunderscored displays 77user session degradation data keywords, TSO 44utilities commands, batch 22utility reporting commands 27, 44utilization, CPU 23

VVLF class statistics keyword 44


Wwait categories, summary 44wait reason codes 25wait reason codes, detail 44wait reason codes, EPILOG

ACTIVEIO or AIO 51AIO 53ENQ 95ENQUEUE or ENQ 95QIO 160QUEUEDIO or QIO 158

wait, summary 43workload display options keywords 45workload exception filter keywords 46workload exceptions, filtering keywords 34workload keywords 46workload keywords, batch 22Workload name associated with service class name

data element 277workload profile facility (WPF) commands 47WPF commands 47

command language reference manual -...

Documents