OMEGAMON XE for Sysplex Reference Guide, V220 -...

Reference GuideOMEGAMON® XE for Sysplex

Version 220

GC32-9319-00

March 2002

Candle Corporation201 North Douglas Street

El Segundo, California 90245-9796

2 OMEGAMON XE for Sysplex Reference Guide, V220

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

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

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

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

Contents 3

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

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

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Contents of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . 14

What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Chapter 1. Introducing OMEGAMON XE for Sysplex Attributes . . . . . . . .21OMEGAMON XE for Sysplex Attributes . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 2. CF_Clients Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25CF_Clients Group Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 3. CF_Path Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31CF_Path Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 4. CF_Policy Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35CF_Policy Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 5. CF_Structure_To_MVS_System Attributes . . . . . . . . . . . . . . . . 39CF_Structure_To_MVS_System Attribute Definitions . . . . . . . . . . . . . 40

Chapter 6. CF_Structures Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45CF_Structures Group Attribute Definitions. . . . . . . . . . . . . . . . . . . . . 47

Chapter 7. CF_Systems Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65CF_Systems Attribute Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Contents


Chapter 8. Global_Enqueues Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Global_Enqueues Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . . 80

Chapter 9. GRS Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87GRS Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Chapter 10. Local_Time Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93Local_Time Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Chapter 11. Report_Classes Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Report_Classes Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . . . 100

Chapter 12. Resource_Groups Attributes . . . . . . . . . . . . . . . . . . . . . . . . . .103Resource_Groups Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . 104

Chapter 13. Service_Class_Address_Spaces Attributes. . . . . . . . . . . . . . . .107Service_Class_Address_Spaces Attribute Definitions . . . . . . . . . . . . 108

Chapter 14. Service_Class_Enqueue_Workflow_Analysis Attributes . . . . . .113Service_Class_Enqueue_Workflow_Analysis Attribute Definitions . . 114

Chapter 15. Service_Class_I/O_Workflow_Analysis Attributes . . . . . . . . . .117Service_Class_I/O_Workflow_Analysis Attribute Definitions. . . . . . . 118

Chapter 16. Service_Class_Subsys_Workflow_Analysis Attributes . . . . . . .123Service_Class_Subsys_Workflow_Analysis Attribute Definitions. . . . 125

Chapter 17. Service_Definition Attributes. . . . . . . . . . . . . . . . . . . . . . . . . .133Service_Definition Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . 134

Chapter 18. Sysplex_DASD Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . .137Sysplex_DASD Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . . . 138

Chapter 19. Sysplex_DASD_Group Attributes . . . . . . . . . . . . . . . . . . . . . .145Sysplex_DASD_Group Attribute Definitions . . . . . . . . . . . . . . . . . . 146

Contents 5

Chapter 20. Sysplex_DASD_Device Attributes . . . . . . . . . . . . . . . . . . . . . .155Sysplex_DASD_Device Attribute Definitions . . . . . . . . . . . . . . . . . . 156

Chapter 21. Sysplex_DASD_Device_Collection_Filtering Attributes . . . . . .169Sysplex_DASD_Device_Collection_Filtering Attribute Definitions . . 171

Chapter 22. Sysplex_WLM_Service_Class_Period Attributes . . . . . . . . . . .183Sysplex_WLM_Service_Class_Period Attribute Definitions. . . . . . . . 185

Chapter 23. Universal_Time Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . .207Universal_Time Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . . . 208

Chapter 24. WLM_Environment Attributes. . . . . . . . . . . . . . . . . . . . . . . . .213WLM_Environment Attribute Definitions . . . . . . . . . . . . . . . . . . . . . 214

Chapter 25. XCF_Group Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215XCF_Group Attribute Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Chapter 26. XCF_Members Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . .219XCF_Members Attribute Definitions. . . . . . . . . . . . . . . . . . . . . . . . . 220

Chapter 27. XCF_Paths Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227XCF_Paths Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Chapter 28. XCF_System Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237XCF_System Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Chapter 29. XCF_System_Statistics Attributes . . . . . . . . . . . . . . . . . . . . . .241XCF_System Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Appendix A. Guide to Candle Customer Support . . . . . . . . . . . . . . . . . . . .247Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Customer Support Contact Information. . . . . . . . . . . . . . . . . . . . . . 256

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257

List of Tables 7

Table 1. Contents of this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

List of Tables

Preface 9

Preface

Introduction

The OMEGAMON® XE for Sysplex Reference Guide provides detailed information about the OMEGAMON XE for Sysplex attributes. Attributes are available with the CandleNet Command Center™ (CCC) interface CandleNet Portal™.

Who should use this guideThis guide serves the following audiences:

� operators� system programmers� system administrators� network administrators� Candle sales force and field support

Why you should use this guideThis guide will help you understand how to use the OMEGAMON XE for Sysplex attributes to set up situations to monitor your Sysplex.

Candle recommends that you refer to this guide whenever you need additional information about the attributes.

P

Contents of This Guide



OverviewThis unit describes the contents of each chapter of this manual, as shown in the following table.

Table 1. Contents of this guide

Chapter Name Content

“Introducing OMEGAMON XE for Sysplex Attributes” on page 21

This chapter introduces you to OMEGAMON XE for Sysplex attributes.

“CF_Clients Attributes” on page 25 This chapter defines the attributes in the CF_Clients attribute group.

“CF_Path Attributes” on page 31 This chapter defines the attributes in the CF_Path attribute group.

“CF_Policy Attributes” on page 35 This chapter defines the attributes in the CF_Policy attribute group.

“CF_Structure_To_MVS_System Attributes” on page 39

This chapter defines the attributes in the CF_Structure_To_MVS_System attribute group.

“CF_Structures Attributes” on page 45

This chapter defines the attributes in the CF_Structures attribute group.

“CF_Systems Attributes” on page 65 This chapter defines the attributes in the CF_Systems attribute group.

“Global_Enqueues Attributes” on page 79

This chapter defines the attributes in the Global_Enqueues attribute group.

“GRS Attributes” on page 87 This chapter defines the attributes in the GRS attribute group.

“Local_Time Attributes” on page 93 This chapter defines the attributes in the Local_Time attribute group.

“Report_Classes Attributes” on page 99

This chapter defines the attributes in the Report_Classes attribute group.

“Resource_Groups Attributes” on page 103

This chapter defines the attributes in the Resource_Groups attribute group.

Preface 11


“Service_Class_Address_Spaces Attributes” on page 107

This chapter defines the attributes in the Service_Class_Address_Spaces attribute group.

“Service_Class_Enqueue_ Workflow_Analysis Attributes” on page 113

This chapter defines the attributes in the Service_Class_Enqueue_Workflow_Analysis attribute group.

“Service_Class_I/O_ Workflow_Analysis Attributes” on page 117

This chapter defines the attributes in the Service_Class_I/O_Workflow_Analysis attribute group.

“Service_Class_Subsys_ Workflow_Analysis Attributes” on page 123

This chapter defines the attributes in the Service_Class_Subsys_Workflow_Analysis attribute group.

“Service_Definition Attributes” on page 133

This chapter defines the attributes in the Service_Definition attribute group.

“Sysplex_DASD Attributes” on page 137

This chapter defines the attributes in the Sysplex_DASD attribute group.

“Sysplex_DASD_Device Attributes” on page 155

This chapter defines the attributes in the Sysplex_DASD_Device attribute group.

“Sysplex_DASD_Group Attributes” on page 145

This chapter defines the attributes in the Sysplex_DASD_Group attribute group.

“Sysplex_DASD_Device_ Collection_Filtering Attributes” on page 169

This chapter defines the attributes in the Sysples_DASD_Device_Collection_Filtering attribute group.

“Sysplex_WLM_Service_ Class_Period Attributes” on page 183

This chapter defines the attributes in the Sysplex_WLM_Service_Class_Period attribute group.

“Universal_Time Attributes” on page 207

This chapter defines the attributes in the Universal_Time attribute group.

“WLM_Environment Attributes” on page 213

This chapter defines the attributes in the WLM_Environment attribute group.

“XCF_Group Attributes” on page 215

This chapter defines the attributes in the XCF_Group attribute group.

“XCF_Members Attributes” on page 219

This chapter defines the attributes in the XCF_Members attribute group.





“XCF_Paths Attributes” on page 227 This chapter defines the attributes in the XCF_Paths attribute group.

“XCF_System Attributes” on page 237

This chapter defines the attributes in the XCF_System attribute group.



Preface 13

Documentation Set

Documentation Set

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

� OMEGAMON XE for Sysplex User’s Guide V220, OS54-6429

� OMEGAMON XE for Sysplex Reference Guide V220, OS53-6430

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

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

Adobe Portable Document Format



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

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

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

3. On the Print pop-up, select one of the Print Range options for� All� Current page� Pages from: [ ] to: [ ]

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

Printing problems?The print quality of your output is ultimately determined by your printer. Sometimes printing problems can occur. If you experience printing problems, potential areas to check are:� 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.

Preface 15


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

http://www.adobe.com



What’s New 17

What’s New

IntroductionThis section details the enhancements for the Version 220 release of OMEGAMON® XE for Sysplex.

HighlightsVersion 220 provides support for recent enhancements for the new versions of

� CandleNet Portal™

� Candle Management Server® (CMS™)

Changes made to Version 220 For Version 220, the name of the product was changed from Candle Command Center® for Sysplex to OMEGAMON® XE for Sysplex.

Enhancements made to Version 220 for workspacesVersion 220 includes these new workspaces with the columns listed.

� Statistics Report for CF List or Lock Structure

– Percent of Total Requests - Synch

– Percent of Total Requests - Asynch

– Synch to Asynch Conversions per min

– Total Request Count this interval

W

18 OMEGAMON XE for Sysplex User’s Guide, V220

� XCF System Statistics

– Buffer Length

– Percent Fit

– Percent Larger

– Percent Smaller

– Signals Sent

– Signals Received

– System From

– System To

– Times Path Unavailable

– Times Buffer Unavailable

– Transport Class

The following columns have been added to the existing workspace for Service Definition.

� Definition Install Time

� Policy Activate Time

The following columns have been added to the existing workspace for Statistics for CF System.

� Asynchronous Request Per Minute

� Synchronous Requests Per Minute

� Synch to Asynch Conversions Per Min

� Percent Converted

� Total Request Count This Interval

� Percent of Total Requests Synch

� Percent of Total Requests Asynch

� Highest 1 Asynch Request Structure


What’s New 19


� Highest 1 Synch Request Structure



Enhancements made to Version 220 for attribute groupsVersion 220 includes the new attribute group XCF_System_Statistics. The attribute group includes the following attributes.

– Buffer_Length

– Default_Sequence

– Managed_System

– Percent_Degraded

– Percent_Fit

– Percent_Larger

– Percent_Smaller

– Signals_Recevied

– Signals_Sent

– System_From

– System_To

– Times_Buffer_Unavailable

– Time_Paths_Unavailable

– Transport_Class

The following attributes have been added to the existing attribute group for Service Definition.

� Definition_Install_Time

� Policy_Activate_Time

20 OMEGAMON XE for Sysplex User’s Guide, V220

The following attributes have been added to the existing attribute group for CF_ Systems.

� Percent_Total_Requests_Synch

� Synch_Asynch_Convs_Per_Min

� Synchronous_Requests_Per_Minute

� Total_Control_Space

� Total_Request_Cnt_This_Interval

The following attributes have been added to the existing attribute group for CF_ Structures.

� Percent_Total_Requests_Asynch

� Percent_Total_Requests_Synch

� Synch_Asynch_Convs_Per_Min

� Total_Request_Cnt_This_Interval

Introducing OMEGAMON XE for Sysplex Attributes 21

IntroducingOMEGAMON XE for Sysplex

Attributes

IntroductionThis chapter introduces you to the OMEGAMON XE for Sysplex attributes.

Chapter ContentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Attribute groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Associating attributes with workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Attributes in a multi-instance group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

1

OMEGAMON XE for Sysplex Attributes



OverviewIn this unit, you learn about the OMEGAMON XE for Sysplex attributes.

You can use the OMEGAMON XE for Sysplex to build situations that monitor the performance of your Sysplex network.

All of these attributes are found under Managed Systems, “The MVS Sysplex”.

Attribute groupsOMEGAMON XE for Sysplex provides the following 26 attribute groups:

� CF_Clients

� CF_Path

� CF_Policy

� CF_Structure_To_MVS_System

� CF_Structures

� CF_Systems

� Global_Enqueues

� GRS

� Local_Time

� Report_Classes

� Resource_Groups

� Service_Class_Address_Spaces

� Service_Class_Enqueue_Workflow_Analysis

� Service_Class_I/O_Workflow_Analysis

� Service_Class_Subsys_Workflow_Analysis

� Service_Definition

Introducing OMEGAMON XE for Sysplex Attributes 23


� Sysplex_DASD

� Sysplex_DASD_Device

� Sysplex_DASD_Group

� Sysplex_DASD_Device_Collection Filtering

� Sysplex_WLM_Service_Class_Period

� Universal_Time

� WLM_Environment

� XCF_Group

� XCF_Members

� XCF_Paths

� XCF_System

For each OMEGAMON XE for Sysplex attribute group there are one or more attribute items.

The following chapters describe each attribute group and the purpose and valid values for all attribute items in each attribute group.

Associating attributes with workspacesThere is a direct relationship between the attributes and the workspaces. An attribute group in most cases corresponds to a workspace. A few attribute groups cover more than one workspace. The attribute items correspond to workspace columns.

The workspaces provide real-time information on many of the attributes. The workspaces are available to you at any time, independent of whether you are using OMEGAMON XE for Sysplex to monitor situations.

See the OMEGAMON XE for Sysplex User’s Guide for more information about the OMEGAMON XE for Sysplex attributes and for detailed information about the OMEGAMON XE for Sysplex workspaces.



Attributes in a multi-instance groupThe attribute groups are multi-instance attribute groups. When creating situations, you can mix attributes from a single group only. You can combine situations if you want to mix attributes from different groups.

CF_Clients Attributes 25

CF_Clients Attributes

IntroductionThis chapter defines the attributes in the CF_Clients attribute group.

AttributesOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Address_Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26ASID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Connection_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Connection_Problem_Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Connection_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Structure_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Structure_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28System_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2

CF_Clients Group Attribute Definitions



OverviewIn this unit you learn about the attributes in the CF_Group_Name attribute group. Use these attributes to create situations that monitor user connections to coupling facility structures.

Address_SpaceThe address space name.

Valid Format

� Simple text strings

� 1 - 8 characters

Example

JES2

ASIDThe hexadecimal address space ID.

Valid Format

� Numeric values, including the use of the *MAX, *MIN, or *SUM functions.

� The range in hex is 0 - FFFF or, in decimal, 0 - 65535. If used in a situation, ASID must be specified in its decimal form.

Example

ASID x 1F is entered as:

31



Connection_NameThe name of the connection between the address space and the CF structure.

Valid Format

� Simple text strings� 1 - 16 characters

Example

JES2_SYSA

Connection_Problem_FlagThe flag indicating whether or not this connection is in a problem state. A Connection_Status of FAILEDPERS or FAILING is considered a problem.

Valid Values

� 1 (problem)

� 0 (no problem)

Example

0

Connection_StatusThe status of the current CF connection.

Valid Values

� Active - the connection is currently active.� FailedPers - the connection has failed but is being maintained because the

connector specified connection disposition of keep. It is expected that the failed connector will attempt to reconnect.

� Failing - the connection is attempting to fail but some connected users of the structure have not yet responded to the fail/disconnect event.



� Disconnecting - The user is attempting to disconnect from the structure but some connected users of the structure have not yet responded to the fail/disconnect event.

� ConnectedKeep - Connected with CONDISP=KEEP (that is, a persistent connection).

� ConnectedRebuild - Connected to both structures during structure rebuild.

Example

Active

Structure_NameThe name of the coupling facility structure.

Valid Format


Example

IXCSTR1

Structure_TypeThe structure type.

Valid Values

� Cache� List

Example

Cache

System_NameThe name of the coupling facility system. In this case, the name of the MVS system where the address space is located.



Valid Format


Example

SYSA

CF_Path Attributes 31

CF_Path Attributes

IntroductionThis chapter defines the attributes in the CF_Path attribute group.

AttributesOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32CF_Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Contention_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32I/Os_Per_Second . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Sub_Channel_Path_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33System_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3

CF_Path Attribute Definitions



OverviewIn this unit you learn about the attributes in the CF_Path attribute group. Use this attribute group to create situations that monitor channel path activity between MVS systems and Coupling Facilities.

CF_NameThe name of the Coupling Facility system to which this MVS system is connected.

Valid Format


Example

COUPLER1

Contention_PercentThe percent of requests started on this path that were delayed because the path is busy.

Valid Format

� Numeric values, including the use of the *AVG, *MAX, *MIN, or *SUM functions.

� In the range of 0.0 to 100.0, one decimal point precision.

Example

10.2

CF_Path Attributes 33


I/Os_Per_SecondThe I/O rate for the channel path.

Valid Format


� In the range of 0 to 2147483647, one decimal point precision.

Example

25.2

StatusThe current status of the path.

Valid Values

� NotOperationl - the path, although defined, can not be activated.

� Inactive - the path is currently offline but could be brought into service.

� Active - path is currently available for service.

Example

Active

Sub_Channel_Path_IDThe hexadecimal channel path ID.

Valid Format


� A 4-digit hexadecimal number. The decimal range is 0 - 65535 in hex (0 to FFFF). Hex notation does not work on input. The user must substitute the decimal equivalent for a hex subchannel address.

Example

The decimal equivalent of hex “0150” is:



336

System_NameThe name of the MVS image connected to the facility.

Valid Format



Example

SYSA

CF_Policy Attributes 35

CF_Policy Attributes

IntroductionThis chapter defines the attributes in the CF_Policy attribute group.

AttributesDate_Time_Activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Policy_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Reformat_Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4

CF_Policy Attribute Definitions



OverviewIn this unit you learn about the attributes in the CF_Policy attribute group. Use this attribute group to create situations that monitor the active Coupling Facility Policy.

Date_Time_ActivateThe date and time that the CF policy was activated.

Valid Format

� Simple text strings� The date and time format for situations is CYYMMDDHHMMSSTTT

(progressing from C representing century to T representing thousands of seconds).

Example

December 21, 1998 at 3:30pm is:

0981221153000000

Policy_NameThe coupling facility policy name.

Valid Format


Example

CFRMPOL1

CF_Policy Attributes 37


Reformat_RequiredThe coupling facility policy that indicates whether a reformat of the CFRM is required.

Valid Values

� Yes - reformat required. � No - reformat not required.

Example

No

CF_Structure_To_MVS_System Attributes 39

CF_Structure_To_MVS_SystemAttributes

IntroductionThis chapter defines the attributes in the CF_Structure_To_MVS_System attribute group.

AttributesAverage_Asynchronous_Request_Time . . . . . . . . . . . . . . . . . . . . . . . . . . 40Average_Queued_Request_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Average_Synchronous_Request_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Request_Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Requests_Converted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Structure_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42System_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Total_Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42User_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5

CF_Structure_To_MVS_System Attribute Definitions



OverviewIn this unit you learn about the attributes in the CF_Structure_To_MVS_System attribute group. Use this attribute group to create situations that monitor the request activity from an MVS image to a Coupling Facility structure.

Average_Asynchronous_Request_TimeThe average time that an asynchronous request takes to complete. During an asynchronous request, the requesting application does not perform operations while waiting for the result of the request. The application waits to be notified of the completion by either an ECB post or entry into an exit routine. This is issued when the request is expected to take significant time to complete.

Valid Format



Example

1,234.0 microseconds is specified as: 1234.0

Average_Queued_Request_TimeThe average time that a request was queued at this MVS image.

Valid Format



Example




Average_Synchronous_Request_TimeThe average time that a synchronous request takes to complete. The time units are in micro-seconds. A synchronous request is one which is expected to complete so quickly that the requesting application would rather wait for completion than do other work and be interrupted when the request completes.

Valid Format� Numeric values, including the use of the *AVG, *MAX, *MIN, or *SUM

functions.� In the range of 0 to 2147483647, one decimal point precision.

Example


Request_RatesThe number of requests per second from this system to this structure.

Valid Format



Example

12.8

Requests_ConvertedThe total number of requests over the last observation interval from this system to this structure that were issued as synchronous and were converted to asynchronous.



Valid Format


� Integer, in the range of 0 to 2147483647.

Example

25

Structure_NameThe name of a structure that has connected users in the associated MVS image.

� Simple text strings� 1 to 16 characters

Example

IXSTR1

System_NameThe name of the MVS image connected to the Sysplex.

Valid Format

� Simple text strings� 1 to 8 characters

Example

SYSA

Total_Requests

The total number of requests from this system to this structure over the last observation interval.




functions.� Integer, in the range of 0 to 2147483647, one decimal point precision.

Example

182

User_CountThe number of users on this image connected to the structure.

Valid Format



Example

4

CF_Structures Attributes 45

CF_Structures Attributes

IntroductionThis chapter defines the attributes in the CF_Structures attribute group.

AttributesAsynchronous_Requests_per_Minute . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47CF_Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Data_Area_Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Data_Element_Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Directory_Element_Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Directory_Entry_Count. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Dump_Contention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Dump_Table_Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Element_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Entry_Element_Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50False_Lock_Table_Entry_Contention_Count. . . . . . . . . . . . . . . . . . . . . . . 51First_Castout_Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51In_Use_List_Set_Entry_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Last_Castout_Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52List_Set_Element_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Lock_Table_Entry_Contention_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Lock_Table_Entry_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Maximum_Data_List_Entry_Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6


Maximum_List_Set_Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Maximum_List_Set_Entry_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Minimum_Structure_Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Maximum_Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Maximum_Structure_Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Percent_CF_Storage_Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Percent_Converted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Percent_Queued_Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Percent_Total_Requests_Asynch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Percent_Total_Requests_Synch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Problem_Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Rebuild_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Storage_Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Storage_Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Structure_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Structure_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Structure_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Synch_Asynch_Convs_Per_Min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Synch_Asynch_Convs_Per_Min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Synch_Asynch_Convs_Per_Min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Total_Request_Cnt_This_Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Total_Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Utilized_Storage_Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64


CF_Structures Group Attribute Definitions


OverviewIn this unit you learn about the attributes in the CF_Structures attribute group. Use this attribute group to create situations that monitor activity and storage demands of Coupling Facility structures.

Asynchronous_Requests_per_MinuteThe rate of asynchronous operations for this structure during the last interval. During an asynchronous request, the requesting application does not perform operations while waiting for the result of the request. The application waits to be notified of the completion by either an ECB post or entry into an exit routine. This is issued when the request is expected to take significant time to complete.

Valid Format

� Numeric

� Real number, maximum of 4 digits to one decimal point precision

Example

839.2

CF_NameThe name of the coupling Facility where the structure is allocated.

Valid Format



Example

COUPLER1



Data_Area_ElementThe number of data area elements in the cache structure.

Valid Format



Example

880

Data_Element_SizeThe size in bytes of data elements in this structure.

Valid Format



Example

2048

Directory_Element_RatioThe directory-to-element target ratio for cache structures.

Valid Format



Example

224:880



Directory_Entry_CountThe number of directory entries in the cache structure.

Valid Format



Example

224

Dump_ContentionThe count of operations that were queued for dump serialization.

Valid Format



Example

0

Dump_Table_SizeThe size in 4K blocks of the dump table space used for this structure.

Valid Format



Example

0



Element_CountThe number of data elements in a cache or queues list.

Valid Format



Example

880

Entry_Element_RatioThe entry-to-element target ratio for list structures.

Valid Format



Example

193:167



False_Lock_Table_Entry_Contention_CountThe number of lock requests that encountered contention due to storage constraints. If this number is high, more list table entries should be allocated.

Valid Format



Example

4

First_Castout_ClassThe name of the castout class found in the cache structure.

Valid Format


� Integer, in the range of 0 to 32767. Castout classes are integers (0, 1, 2, etc.). This attribute lists the first one assigned to this structure, if any.

Example

0



In_Use_List_Set_Entry_CountThe number of list set entries currently in use in the structure.

Valid Format



Example

19

Last_Castout_ClassThe name of the last castout class found in the cache structure.

Valid Format


� Integer, in the range of 0 to 32767. Castout classes are integers (0, 1, 2, etc.). This attribute lists the first one assigned to this structure, if any.

Example

0

List_Set_Element_CountThe number of elements in the list structure currently in use.

Valid Format



Example

24



Lock_Table_Entry_Contention_CountThe number of lock requests that encountered contention on a lock table entry.

Valid Format



Example

0

Lock_Table_Entry_CountThe number of lock table entries in the list structure.

Valid Format



Example

0



Maximum_Data_List_Entry_SizeThe maximum number of data elements per list entry.

Valid Format



Example

10

Maximum_List_Set_ElementsThe maximum number of data elements in the list structure.

Valid Format



Example

167



Maximum_List_Set_Entry_CountThe maximum number of list set entries in the structure.

Valid Format



Example

193

Maximum_Structure_SizeThe maximum size of the structure.

Valid Format



� Value is expressed in 4K pages for attribute purposes. The workspace shows the numbers scaled to K or Mega bytes.

Example

256

Maximum_UsersThe maximum number of users that may connect to the structure.

Valid Format





Example

64

Minimum_Structure_SizeThe minimum size of the structure.

Valid Format


� Integer, in the range of 0 to 2147483647. This value is expressed in 4K pages for attribute purposes. The workspace shows the number scaled to K or Mega pages.

Example

128

Percent_CF_Storage_SizeThe percentage of the total coupling facility allocated to the structure.

Valid Format


� In the range of 0.0 - 100.0, one decimal point precision.

Example

35.5



Percent_ConvertedThe percentage of total requests for this structure in the last interval that were converted from synchronous requests to asynchronous requests.

Valid Format


� In the range of 0.0 - 2147483647, one decimal point precision.

Example

0.0

Percent_Queued_RequestsThe percentage of total requests for this structure over the last interval that were queued.

Valid Format


� In the range of 0.0 - 2147483647, one decimal point precision.

Example

41.3

Percent_Total_Requests_Asynch The percentage of the total requests that were asynchronous operations for this structure during this interval period.

Valid Format





Example

20.0

Percent_Total_Requests_Synch The percentage of the total requests that were synchronous operations for this structure during this interval period.

Valid Format



Example

30.0

Problem_UsersThe number of users connected to the structure in an exception state. The address space is not in an exception state, but the connection is.

Valid Format



Example

2

Rebuild_PercentThe percentage of failed weighted connections at which rebuild should be automatically started by the system.

Valid Format





Example

35.5

Storage_ClassesThe highest storage class used by the structure. Storage classes are in the range of 0 to this value.

Valid Format



Example

128

Storage_SizeThe storage size currently allocated to the structure.

Valid Format


� Integer, in the range of 0 to 2147483647. This value is expressed in 4K pages; 128 pages = 512.0 Kbytes. The workspace shows the value in K or Mega bytes, but the attribute must be expressed in 4K pages.

Example

128



Structure_NameThe name of the structure.

Valid Format



Example

IXCSTR1

Structure_StatusThe current status of the structure.

Valid Values

� ActiveDuplexPrimary - The structure is active and is being duplexed. This is the primary copy of the structure.

� ActiveDuplexAlternate - The structure is active and is being duplexed. This is the alternate copy of the structure.

� ActiveInUse - The structure is active with connected users.

� ActivePersistent - The structure is active with STRDISP=KEEP specified. This Indicates that the structure remains allocated after all connectors have disconnected from the structure.

� Defined - Structure is defined in the CF policy.

� PolicyChange - There is a change pending for the CF policy (CFRM) for this structure.

� Transitional - Structure is in the process of either being allocated in a coupling facility or deleted from a coupling facility.

� Failed - Structure failure has been recognized for this version of the structure.

� HoldingConnectivity - Structure was being deleted from the coupling facility but connectivity was lost.



� HoldingDumpPend - Structure can not be de-allocated since a dump table is associated with the structure.

Note: We would not normally expect to see any of the following statuses for a structure. They should exist for very brief periods of time. If one of these statuses persists for more than 5 minutes it would indicate a sever problem with either the structure or the monitoring facility.

� RebuildActive - Structure rebuild process is in progress.

� RebuildStopped - A structure rebuild process has been stopped usually by operator command.

� RebuildOldStr - This is the original structure in a rebuild process.

� RebuildNewStr - This is the new structure in a rebuild process.

� RebuildQuiesce - A structure rebuild has been initiated. Connections need to stop usage of the structure and confirm. This phase will be complete when all connections have issued IXLEERSP for the Rebuild Quiesce event.

� RebuildComplete - A structure rebuild is in progress. Connections can connect to new structure. This phase will be complete when all connections have issued IXLREBLD REQUEST=COMPLETE.

� RebuildCleanup - A structure rebuild is in progress. Connections have completed their part of the process and final cleanup is in progress. This phase will be complete when all connections have issued IXLEERSP for the Rebuild Cleanup event.

� RebuildStartOperator - A rebuild process was started by the operator.

� RebuildStartConnector - A rebuild process was started by one of the connecting applications.

� RebuildLostOldFacility - A rebuild process was stopped because connectivity was lost to the coupling facility containing the original structure.

� RebuildFailed - A rebuild process failed.

� RebuildStoppedOperator - A rebuild process was stopped by operator command.



� RebuildStoppedConnector - A rebuild process was stopped by one of the connected users.

� RebuildLostNewFacility - A rebuild process was stopped because connectivity was lost to the coupling facility containing the new structure.

� RebuildOldStrFailed - A rebuild process stopped because the original structure failed.

Example

ActiveInUse

Structure_TypeThe type of structure, cache or list

Valid Values

� Cache

� List

Example

List

Synch_Asynch_Convs_Per_Min Rate of synchronous operations that were converted to asynchronous requests for this structure during a one minute period.

Valid Format


� Integer, in the range of 0 to 2147483647, to one decimal point precision.

Example

15.5



Synchronous_Requests_per_minuteThe rate of synchronous operations for this structure during the last interval. A synchronous request is a request that completes so quickly that the requesting application would rather wait for completion than do other work and be interrupted when the request completes.

Valid Format


� Integer, in the range of 0 to 2147483647, to one decimal point precision.

Example

9.2

Total_Queued_RequestsThe count of all operations that were queued in the last interval.

Valid Format



Example

1389

Total_Request_Cnt_This_Interval Total number of synchronous and asynchronous operations for this structure during this interval period.

Valid Format





Example

25

Total_UsersThe total number of users connected to the structure.

Valid Format



Example

6

Utilized_Storage_SizeThe percentage of the structure storage actually in use.

Valid Format



Example

42.3

CF_Systems Attributes 65

CF_Systems Attributes

IntroductionThis chapter defines the attributes in the CF_Systems attribute group.

AttributesAllocated_Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Average_Failed_Operation_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Average_Sync_Operation_Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68CF_Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68CF_Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Connected_MVS_System_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69CPU_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Dump_Table_In_Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Dump_Table_Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Free_Control_Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71I/Os_Per_Second . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Maximum_Sub_Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Percent_Total_Requests_Synch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Structure_Count_In_Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Structure_Count_Out_Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Sub_Channels_Allocated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Sub_Channels_In_Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Synch_Asynch_Convs_Per_Min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Total_Control_Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

7


Total_Request_Cnt_This_Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Volatility_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76


CF_Systems Attribute Definitions


OverviewIn this unit you learn about the attributes in the CF_Systems attribute group. Use this attribute group to create situations that monitor Coupling Facility CPU and storage demands.

Allocated_StorageThe amount of the storage allocated to the Coupling Facility currently in use. Allocated storage is the total number of 4K pages assigned to the Coupling Facility.

Valid Format



Example

59328

Average_Failed_Operation_TimeThe average service time for unsuccessful operations.

Valid Format


� Integer, in the range of 0 to 2147483647, one decimal point precision.

Example

0.0



Average_Sync_Operation_DelayThe average waiting time for a subchannel to be available for a synchronous operation.

Valid Format



Example

38.7

CF_LevelThe Coupling Facility architected function level.

Valid Format



Example

3

CF_NameThe name of the Coupling Facility.

Valid Format



Example

COUPLER1



Connected_MVS_System_CountThe number of MVS images connected to the facility.

Valid Format



Example

6

CPU_PercentThe percentage of CPU utilization by the Coupling Facility.

Valid Format



Example

37.5



Dump_Table_In_UseThe amount of the reserved dump storage in the Coupling Facility currently holding dumps. The size is expressed as a 4K page count. It is not a percentage

Valid Format



Example

0

Dump_Table_SizeThe amount of storage in the Coupling Facility reserved for dump tables. The size is expressed as 4K page count.


functions.


Example

512



Free_Control_SpaceThe amount of control storage in the named Coupling Facility that is not assigned to structures or dump space. The value is a 4K page count.

Valid Format



Example

4416

I/Os_Per_SecondThe sustained I/O rate (I/O requests per second) by the Coupling Facility.

Valid Format



Example

27.6



Maximum_Sub_ChannelsThe count of available subchannels that can be used for operations.

Valid Format

� Integer

� 0 to 2 billion (Values are rarely above 10.)

Example

4

Percent_Total_Requests_SynchThe percentage of the total requests that were synchronous operations for this system during this interval period.

Valid Format



Example

20.0

Percent_Utilized_StorageThe percentage of storage currently being utilized.

Valid Format



Example

63.5



StatusThe current status of the facility.

Valid Values

� Okay - This coupling facility is functioning properly.

� Failed - This coupling facility has failed.

� Reconcile - The coupling facility to CFRM policy reconcile process is in progress. When this bit is on IXLCONNs to structures in this coupling facility are not permitted.

� PolChg - Policy change pending which will delete this coupling facility from the CFRM active policy when all allocated structures are gone from this coupling facility.



Example

Okay

Structure_Count_In_PolicyThe number of structures in the Coupling Facility which are contained in the current Coupling Facility Resource Management policy.

Valid Format



Example

31

Structure_Count_Out_PolicyThe number of structures in the Coupling Facility which cannot be added to the current Coupling Facility Resource Management policy.

Valid Format



Example

0



Sub_Channels_AllocatedThe count of subchannels that this facility has been allocated.

Valid Format

� Integer


Example

4

Sub_Channels_In_UseThe count of subchannels available for use.

Valid Format

� Integer


Example

4

Synch_Asynch_Convs_Per_Min The rate of synchronous operations that were converted to asynchronous requests for this system during a one minute period.

Valid Format



Example

60.0



Total_Control_SpaceThe total amount of storage in the named coupling facility that can be used as control storage.

Valid Format



Example

59238

Total_Request_Cnt_This_Interval The total number of synchronous and asynchronous operations for this system during this interval period.

Valid Format



Example

99

Volatility_StatusA one-byte flag representing the volatility state of storage in the LPAR housing the Coupling Facility.

Valid Format

� Non-volatile

� Volatile

Example



Non-volatile

Global_Enqueues Attributes 79

Global_Enqueues Attributes

IntroductionThis chapter defines the attributes in the Global_Enqueues attribute group.

AttributesASID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Major_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Maximum_Wait_Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Minor_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Owning_Address_Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Owning_Task_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82System_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Wait_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Waiting_Address_Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Waiting_Task_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

8

Global_Enqueues Attribute Definitions



OverviewIn this unit you learn about the attributes in the Global_Enqueues attribute group. Use this attribute group to create situations that monitor enqueue conflicts within the Sysplex.

ASIDThe hexadecimal address space ID.

Valid Format


� Integer, in the range of 0 to 2147483647. In situations, this value must be expressed in decimal terms. For hex, the range is 0 - FFFF (0 - 65535 in decimal). A hex ASID of “1F” is “31” in decimal.

Example

1F

Major_NameThe major name (qname) of the resource.

Valid Format



Example

SYSDSN



Maximum_Wait_TimeThe longest time that the task has been waiting for the resource.

Valid Format



Example

45

Minor_NameThe minor name (rname) of the resource.

Valid Format



Example

SYS1.PROCLIB

Owning_Address_SpaceThe name of the job containing the task that owns the resource.

Valid Format



Example

PRODJOB1



Owning_Task_CountThe number of tasks owning the resource.

Valid Format



Example

3

Status Status of each system in the global resource serialization complex.

Valid Format� Inactive - The system is not part of the ring. INACTIVE appears when a

ring disruption has occurred. The system has current information about global resources but is not currently processing global resource requests. Users of global resources retain ownership, but any users who try to obtain or release a global resource are suspended. Multiple systems can be INACTIVE, and an inactive system can restart the ring. A system will restart the ring as soon as possible.

� Active - The system is part of the ring and is actively participating in global resource serialization. ACTIVE is the normal condition.

� Joining - The system is joining the ring as part of its IPL process.

� Restarting - The system is re-entering the ring after a ring disruption.

� Quiesced - The system is temporarily suspended from the ring, in response to a ring disruption. The system does not have current information about global resources and is not currently processing global resource requests. Users of global resources retain ownership, but any users who try to obtain or free a global resource are suspended. The system should restart and become active as soon as it is able.



SwappedThe swap status of the address space in which the task is executing.

Valid Values

� Swapped

� Not swapped

Example

Not Swapped

System_NameThe SYSNAME or SMF ID of the MVS image where the task is executing.

Valid Format



Example

SYSA



TypeThe type of ENQ the task issued for the resource.

Valid Values

� Exclusive - The requester requires that no other processes have access to this resource.

� Share - The requester is capable of sharing access to the resource with other processes.

Example

Exclusive

Wait_TimeThe time in seconds that the task has been waiting for the resource.

Valid Format



Example

45

Waiting_Address_SpaceThe name of the address space currently waiting on the resource.

Valid Format



Example

PRODJOB2



Waiting_Task_CountThe number of tasks waiting for the resource.

Valid Format



Example

1

GRS Attributes 87

GRS Attributes

IntroductionThis chapter defines the attributes in the GRS attribute group.

AttributesActual_Response_Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Current_RSA_Message_Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Expected_Response_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Maximum_RSA_Message_Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Resident_Milliseconds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Ring_Acceleration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90System_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Tolerance_Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

9

GRS Attribute Definitions



OverviewIn this unit you learn about the attributes in the GRS attribute group. Use this attribute group to create situations that monitor ring status and ring message delays.

Actual_Response_TimeThe actual measured ring response time in milliseconds.

Valid Format



Example

33

Current_RSA_Message_SizeThe current size, in bytes, of the outgoing RSA message.

Valid Format



Example

144

GRS Attributes 89


Expected_Response_TimeThe anticipated (or average) time, in milliseconds, a requester must wait for access to a global resource.

Valid Format



Example

78

Maximum_RSA_Message_SizeThe maximum size of the RSA message, in bytes.

Valid Format



Example

32768

Resident_MillisecondsThe minimum amount of time, in milliseconds, the RSA message is delayed in each MVS image in the GRS complex.

Valid Format



Example

3



Ring_AccelerationThe number of consecutive MVS images in the GRS complex that must process the RSA-message before GRS grants access to a global resource.

Valid Format



Example

2

StatusThe status of each system in the global resource serialization complex.

Valid Values

� Inactive

� Active

� Joining

� Restarting

� Quiesced

Example

Active

GRS Attributes 91


System_NameThe name of the MVS image connected to the facility.

Valid Format


Example

SYSA

Tolerance_IntervalThe maximum amount of time, in milliseconds, GRS waits before it detects an overdue RSA-message.

Valid Format



Example

75000

Local_Time Attributes 93

Local_Time Attributes

IntroductionThis chapter defines the attributes in the Local_Time attribute group.

AttributesDate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Day_Of_Month. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Day_Of_Week . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Hours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Minutes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Month_Of_Year . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

10

Local_Time Attribute Definitions



OverviewThe Local_Time attributes show the time and date at the agent location. For example, if you are running CandleNet Portal in London and monitoring a system in Cairo, the local Cairo time and date will be returned. These attributes are useful for action situations triggered by time, or views that correlate the local time of systems in different time zones.

Note: When making date comparisons, in order to achieve accurate results, you must use the Timestamp attribute rather than either the Local_Time or Universal_Time attribute.

DateThe date attribute is no longer valid. In the situations you created, replace the Date attribute with the Timestamp attribute.

Day_Of_MonthThe day in the month the CMS samples the data at the agent location.

Valid Format

A numeric value in the range 01 to 31.

Example

01



Day_Of_WeekThe day in the week the CMS samples the data at the agent location.

Valid Format

A 2-digit value in the range 01 (Sunday) to 07 (Saturday).

Example

02

HoursThe hour in the day the CMS samples the data at the agent location.

Valid Format

A 2-digit value in the range 00 to 23.

Example

10

MinutesThe minutes into the hour the CMS samples the data at the agent location.

Valid Format


Example

05



Month_Of_YearThe month in the year the CMS samples the data at the agent location.

Valid Format

A numeric value in the range 01 (January) to 12 (December).

Example

04

Seconds The second in the minute the CMS samples the data at the agent location.

Valid Format


Example

02

Timestamp The date and time when the CMS samples the data at the agent location.

Valid Format

The timestamp format for the SCAN and STR functions is CYYMMDDHHMMSSmmm (as in 1020415074501000 for April 15, 2002 at 07:45:01) where:

C = Century (0 for 20th, 1 for 21st)Y = YearM = MonthD = DayH = HourM = MinuteS = Secondm = millisecond



Example

1020415074501000

Report_Classes Attributes 99

Report_Classes Attributes

IntroductionThis chapter defines the attributes in the Report_Classes attribute group.

AttributesAddress_Space_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100I/O_Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Page_Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Report_Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

11

Report_Classes Attribute Definitions



OverviewIn this unit you learn about the attributes in the Report_Classes attribute group. Use this attribute group to create situations that monitor workload activity accumulated by report class rather than service class.

Address_Space_CountThe number of address spaces for this report class.

Valid Format



Example

211

I/O_RateThe number of I/Os per second experienced by the report class during the current interval.

Valid Format


� In the range of 0 to 2147483647, one decimal precision.

Example

1.4

Page_RateThe number of page faults per second experienced by all address spaces in the report class during the report period.

Report_Classes Attributes 101


Valid Format



Example

2.5

Report_ClassThe name of the report class.

Valid Format


Example

REPORTA

VelocityThe percentage of processor utilization for all address spaces in this report class.

Valid Format



Example

25.5

Resource_Groups Attributes 103

Resource_Groups Attributes

IntroductionThis chapter defines the attributes in the Resource_Groups attribute group.

AttributesDescription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Group_Capacity_Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Maximum_Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Minimum_Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Percent_Maximum_Group_Capacity_Used. . . . . . . . . . . . . . . . . . . . . . . 106Service_Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

12

Resource_Groups Attribute Definitions



OverviewIn this unit you learn about the attributes in the Resource_Groups attribute group. Use this attribute group to create situations that monitor service class resource limits.

DescriptionThe description of the resource group.

Valid Format


Example

Resource group to allow 4 MIPs

Group_Capacity_UtilizationThe number of unweighted service units that are currently being consumed per second by the resource group.

Valid Format



Example

25

Resource_Groups Attributes 105


Maximum_CapacityThe maximum unweighted number of service units that can be consumed per second by all service classes within the resource group.

Valid Format



Example

200

Minimum_CapacityThe minimum unweighted number of service units that can be consumed per second by all service classes within the resource group.

Valid Format



Example

50

NameThe name of the resource group.

Valid Format


Example

FOURMIT



Percent_Maximum_Group_Capacity_UsedThe percentage of CPU service units defined as the maximum consumable by the resource group currently being consumed by all service classes associated with the resource group.

Valid Format


� In the range of 0.0 to 100.0 one decimal point precision.

Example

25.5

Service_ClassThe name of a service class that is in the resource group.

Valid Format


Example

STC

Service_Class_Address_Spaces Attributes 107

Service_Class_Address_SpacesAttributes

IntroductionThis chapter defines the attributes in the Service_Class_Address_Spaces attribute group.

AttributesAddress_Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108ASID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108CPU_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109CSTOR_Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109ESTOR_Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109I/O_Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Page_Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Report_Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Service_Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111System_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

13

Service_Class_Address_Spaces Attribute Definitions



OverviewIn this unit you learn about the attributes in the Service_Class_Address_Spaces attribute group. Use this attribute group to create situations that monitor resource consumption of address spaces with service classes.

Address_SpaceThe name of the service class that is running work in the service class.

Valid Format



Example

PLDSOS1

ASIDThe hexadecimal address space identification.

Valid Format


� Integer, in the range of -2147483647 to 2147483647. When you are using the attribute in a situation, the ASID must be entered in its decimal form. If the hex ASID is “1F”, enter the decimal equivalent “31.”

Example

1F



CPU_PercentThe percentage of CPU consumed by the address space over the current interval.

Valid Format



Example

25.5

CSTOR_FramesThe number of working set frames in central storage for the address space.

Valid Format



Example

213

ESTOR_FramesThe number of working set frames in expanded storage for the address space.

Valid Format



Example

0



I/O_RateThe I/O rate experienced by the address space over the current interval (I/Os per second).

Valid Format



Example

25.2

Page_RateThe number of page faults per second experienced by the address space over the reporting period.

Valid Format



Example

10.2

PeriodThe service class period in which this address space is currently running.

Valid Format

� Numeric� 0 - 65535

Example

1



Report_ClassThe name of the report class to which this address space is assigned.

Valid Format


Example

REPORTA

Service_ClassThe name of the service class to which the associated address space is assigned.

Valid Format


Example

STC

System_NameThe SMF ID of the system that is associated with the address space.

Valid Format


Example

SYSA



VelocityThe velocity achieved for the work running in the service class from the address space.

Valid Format


� In the range of 0.0 to 100.0, one decimal point precision.

Example

75.1

Service_Class_Enqueue_ Workflow_Analysis Attributes 113

Service_Class_Enqueue_Workflow_Analysis

Attributes

IntroductionThis chapter defines the attributes in the Service_Class_Enqueue_Workflow_Analysis attribute group.

AttributesLevel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Major_Queue_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Queued_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Service_Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116System_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

14

Service_Class_Enqueue_Workflow_Analysis Attribute Definitions



OverviewIn this unit you learn about the attributes in the Service_Class_Enqueue_Workflow_Analysis attribute group. Use this attribute group to create situations that monitor service class delays due to specific enqueue resources.

LevelThe aggregation at an MVS image level. Data can be aggregated for an individual MVS system or for an entire Sysplex.

Valid Values

� SYSTEM - to aggregate at an MVS image level

� SYSPLEX - to aggregate over an entire Sysplex

Example

SYSTEM

Major_Queue_NameThe resource major name.

Valid Format



Example

SYSDSN

Service_Class_Enqueue_ Workflow_Analysis Attributes 115


PeriodThe period number.

Valid Format


� Integer, in the range of 0 to 8. If the situation is to be at the service class level rather than the period level, use Period = “SUM.”

Example

1

Queued_PercentThe percentage of time queued for a major resource for a service class. This indicates the percentage of time transactions for this service class spent waiting to acquire this enqueue.

Valid Format



Example

25.5



Service_ClassThe service class name.

Valid Format



Example

STC

System_NameThe name of the MVS system being reported on.

Valid Format



Example

SYSA

Service_Class_I/O_ Workflow_Analysis Attributes 117

Service_Class_I/O_Workflow_Analysis

Attributes

IntroductionThis chapter defines the attributes in the Service_Class_I/O_Workflow_Analysis attribute group.

AttributesDevice_Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Device_Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118I/O_Active_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119I/O_Wait_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Service_Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121System_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Volser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

15

Service_Class_I/O_Workflow_Analysis Attribute Definitions



OverviewIn this unit you learn about the attributes in the Service_Class_I/O_Workflow_Analysis attribute group. Use this attribute group to create situations that monitor service class delays due to specific device I/O activity.

Device_NumberThe number of the device that the service class is currently using.

Valid Format

� Numeric

� Integer, in the range of 0 - 65535. For situations, the value must be entered in its decimal equivalent. For example, device X “150” should be entered as its decimal equivalent “336”.

Example

336

Device_TypeThe type of the device that the service class is currently using.

Valid Format



Example

DASD



I/O_Active_PercentThe percentage of active I/O rate for the service class. This is the percentage of the transaction elapsed time spent actively doing I/O on the subject device.


functions.


Example

25.5

I/O_Wait_PercentThe percentage of I/O wait rate for the service class. This is the percentage of the transaction elapsed time spent waiting for I/O on the subject device.

Valid Format



Example

25.5




Valid Values



Example

SYSTEM

PeriodThe service class period number.

Valid Format


� Integer, in the range of 1 - 8. In addition, the user may specify Period = “SUM.” This indicates that the user wants the data summarized at the service class level for this situation.

Example

1



Service_ClassThe name of the service class.

Valid Format



Example

STC


Valid Format



Example

SYSA

VolserThe Volser number of the device that the service class is using.

Valid Format



Example

LST004

Service_Class_Subsys_ Workflow_Analysis Attributes 123

Service_Class_Subsys_Workflow_Analysis

Attributes

IntroductionThis chapter defines the attributes in the Service_Class_Subsys_Workflow_Analysis attribute group.

AttributesActive_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Continuation_In_Network_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Continuation_In_Sysplex_Percent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Continuation_On_Local_MVS_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . 126Conversation_Wait_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Distribution_Wait_Percent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127I/O_Wait_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Idle_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Local_Session_Wait_Percent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Lock_Wait_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Network_Session_Wait_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Other_Product_Wait_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Ready_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Service_Class_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Sysplex_Session_Wait_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

16


Attributes (continued)System_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Timer_Wait_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Unidentified_Resource_Wait_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . 132


Service_Class_Subsys_Workflow_Analysis Attribute Definitions


OverviewIn this unit you learn about the attributes in the Service_Class_Subsys_Workflow_Analysis attribute group. Use this attribute group to create situations that monitor the percent of time that transaction-oriented service classes spend in specific execution states.

Active_PercentThe percentage of samples in active state.

Valid Format



Example

25.5

Continuation_In_Network_PercentThe percentage of samples in a state representing transactions for which there are logical continuations somewhere within the network.

Valid Format



Example

25.5



Continuation_In_Sysplex_PercentThe percentage of samples in a state representing transactions for which there are logical continuations from another MVS image in the Sysplex.

Valid Format



Example

25.5

Continuation_On_Local_MVS_PercentThe percentage of samples in a state representing transactions for which there are logical continuations on an MVS image.

Valid Format



Example

25.5

Conversation_Wait_PercentThe percentage of samples waiting for conversation state.

Valid Format





Example

25.5

Distribution_Wait_PercentThe percentage of samples waiting in a “distributed request” state.

Valid Format



Example

25.5

I/O_Wait_PercentThe percentage of samples waiting for I/O state.

Valid Format



Example

25.5



Idle_PercentThe percentage of samples in idle state. This indicates tasks in this class that are waiting for terminal output.

Valid Format



Example

25.5


Valid Values� SYSTEM - to aggregate at an MVS image level


Example

SYSTEM

Local_Session_Wait_PercentThe percentage of samples waiting for a session to be established locally.

Valid Format



Example

25.5



Lock_Wait_PercentThe percentage of samples waiting for lock state.

Valid Format



Example

25.5

Network_Session_Wait_PercentThe percentage of samples waiting for a session to be established somewhere in the network.

Valid Format



Example

25.5



Other_Product_Wait_PercentThe percentage of samples waiting for another product state.

Valid Format



Example

25.5

PhaseTransaction states sampled in the phase of transactions defined by RCAEEFLG.

Valid Values

� Begin-to-End

� Execution

Example

Execution

Ready_PercentThe percentage of samples in ready state.

Valid Format



Example

25.5



Service_Class_NameThe name of the service class being reported on.

Valid Format



Example

CICSTRN

SubsystemThe type of subsystem where the samples are processed.

Valid Format


� 1 to 4 characters

Example

CICS

Sysplex_Session_Wait_PercentThe percentage of samples waiting for a session to be established somewhere in the Sysplex.



Example

25.5




Valid Format



Example

SYSA

Timer_Wait_PercentThe percentage of samples waiting for timer state.

Valid Format



Example

25.5

Unidentified_Resource_Wait_PercentThe percentage of samples waiting for an unidentified resource.

Valid Format



Example

25.5

Service_Definition Attributes 133

Service_DefinitionAttributes

IntroductionThis chapter defines the attributes in the Service_Definition attribute group.

AttributesService_Definition_Install_Date_Time. . . . . . . . . . . . . . . . . . . . . . . . . . . 134Service_Definition_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Service_Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Service_Policy_Activate_Date_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Service_Policy_Activate_System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Service_Policy_Activate_User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

17

Service_Definition Attribute Definitions



OverviewIn this unit you learn about the attributes in the Service_Definition attribute group. Use this attribute group to create situations that monitor Workload Manager service definition and service policy activation dates.

Service_Definition_Install_Date_TimeThe date and time that the service definition was installed.

Valid Format


� The date and time format for situations is CYYMMDDHHMMSSTTT (progressing from C representing century to T representing thousands of seconds).

Example

For example, January 21, 1999 at 2:35pm is: 0990121143500000

Service_Definition_NameThe name of the service definition.

Valid Format


Example

PLEXADEF

Service_Definition Attributes 135


Service_PolicyThe name of the service policy.

Valid Format


Example

POLPRIME

Service_Policy_Activate_Date_TimeThe date and time that the service policy was activated.

Valid Format


� The date and time format for situations is CYYMMDDHHMMSSTTT (progressing from C representing century to T representing thousands of seconds).

Example

For example, January 21, 1999 at 4:15pm is:

0990121161500000

Service_Policy_Activate_SystemThe system where the service policy was activated

Valid Format

� Simple text strings� 1- 8 characters

Example

SYSA



Service_Policy_Activate_UserThe user that activated the service policy

Valid Format


Example

JSMITH

Sysplex_DASD Attributes 137

Sysplex_DASDAttributes

IntroductionThis chapter defines the attributes in the Sysplex_DASD attribute group.

AttributesUsing attributes to create DASD on demand custom workspaces . . . . . . 138Primary and secondary attributes for on demand custom workspaces. . . 138Average_Device_Contention_Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Average_True_Percent_Busy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Bypass_Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Group_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Highest_Device_Contention_Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Highest_Device_Contention_Index_Volser . . . . . . . . . . . . . . . . . . . . . . . 141Highest_True_Percent_Busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Highest_True_Percent_Busy_Volser . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Volume_Serial_Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

18

Sysplex_DASD Attribute Definitions



OverviewIn this unit you learn about the attributes in the Sysplex_DASD attribute group. Use this attribute group to create situations that monitor sysplex-wide activity of groups of DASD devices.

Using attributes to create DASD on demand custom workspacesYou can use the attributes in this group to create DASD on demand custom workspaces. When you create a DASD on demand custom workspace, the program uses the filtering criteria you specify to create the workspace. For additional information about DASD device collection filtering, see the chapter on filtering in the OMEGAMON XE for Sysplex User’s Guide.

Primary and secondary attributes for on demand custom workspacesThe attributes in Sysplex_DASD are either primary attributes or secondary attributes. The program uses

� primary attributes to gather the data from the MVS image

� secondary attributes to filter the data (after the data is gathered from the MVS image)



Average_Device_Contention_IndexThe average of the device level contention indexes for devices of the group. Device contention is an indicator of I/O delay for this group caused by inter- system contention for the device. The larger the number, the more severe is the contention.

Valid Format


� In the range of 0 to 2147483647, two decimal point precision.

Example

1.35

Usage

The attribute is a secondary attribute that you can use to create DASD on demand custom workspaces.

Average_True_Percent_BusyThe average of true busy calculated for devices in the group. True percent busy is a measure of the busy time accumulated for the group by all systems in the Sysplex.

Valid Format



Example

25.5

Usage




Bypass_Filtering For DASD on demand custom workspaces, specifies whether or not the program bypasses DASD device collection filtering specified in the situation and gathers data for all devices directly from the MVS image.

Valid Values

� YES (DASD device collection filtering is bypassed and data is gathered directly from the MVS image to meet the criteria in the custom workspace.)

� NO (DASD device collection filtering is used and data is filtered further for the custom workspace. The default is NO.)

Example

NO

Group_NameThe name of the DASD group.

Valid Format



Example

SGDB2X

Usage

The attribute is a primary attribute that you can use to create DASD on demand custom workspaces.



Highest_Device_Contention_IndexThe highest of the device level contention indexes for devices in the group.

Valid Format



Example

4.25

Usage


Highest_Device_Contention_Index_VolserThe volser of the device contributing the largest device contention index.

Valid Format



Example

VOL001

Usage




Highest_True_Percent_BusyThe largest true busy observed for a device in the group.

Valid Format



Example

25.5

Usage


Highest_True_Percent_Busy_VolserThe volser of the device contributing to the largest true busy.

Valid Format

� Simple text strings.

� 1 to 6 characters.

Example

VOL001

Usage




Volume_Serial_NumberThe volume serial number.

Valid Format



Example

VOL001

Usage


Sysplex_DASD_Group Attributes 145

Sysplex_DASD_GroupAttributes

IntroductionThis chapter defines the attributes in the Sysplex_DASD_Group attribute group.

AttributesUsing attributes to create DASD on demand custom workspaces . . . . . . 146Primary and secondary attributes for on demand custom workspaces. . . 146Bypass_Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Control_Unit_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Cumulative_I/O_Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Device_Contention_Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Device_Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150True_Percent_Busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Volume_Serial_Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Worst_Disconnect_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Worst_Disconnect_Time_System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Worst_Response_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Worst_Response_Time_System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

19

Sysplex_DASD_Group Attribute Definitions



OverviewIn this unit you learn about the attributes in the Sysplex_DASD_Group attribute group. Use this attribute group to create situations that monitor sysplex-wide activity of individual shared DASD devices.

Using attributes to create DASD on demand custom workspaces You can use the attributes in this group to create DASD on demand custom workspaces. When you create a DASD on demand custom workspace, the program uses the filtering criteria you specify to create the workspace.For additional information about DASD device collection filtering, see the chapter on filtering in the OMEGAMON XE for Sysplex Reference Guide, V220User’s Guide.

Primary and secondary attributes for on demand custom workspacesThe attributes in Sysplex_DASD_Group are either primary attributes or secondary attributes. The program uses






Valid Values


� NO (DASD collection filtering is used and data is filtered further for the custom workspace. The default is NO.)

Example

NO



Control_Unit_TypeThe control unit type.

Valid Values

� Unknown

� 2105

� 3880-23

� 3990-1

� 3990-2

� 3990-3

� 3990-6

Example

3990-2

Usage




Cumulative_I/O_RateThe sum of the I/O rate, in seconds, as seen from each sharing system.

Valid Format



Example

45.1

Usage


Device_Contention_IndexThe device contention index value. Device contention is an indication of I/O delay for this group caused by inter-system contention for the device. The larger the number, the more severe is the contention.

Valid Format



Example

1.35

Usage




Device_TypeThe device type.

Valid Format

� 3380

� 3390

Example

3380

Usage


True_Percent_BusyThe device true busy value.

Valid Format



Example

25.5

Usage





Valid Format



Example

VOL001

Usage


Worst_Disconnect_TimeThe worst disconnect time, in milliseconds, as seen from one system.


functions.


Example

2.8

Usage




Worst_Disconnect_Time_SystemThe system where the worst disconnect time was observed.

Valid Format



Example

SYSA

Usage


Worst_Response_TimeThe worst response seen from one MVS system.

Valid Format



Example

242.8

Usage




Worst_Response_Time_SystemThe system where the worst response time was noted.

Valid Format



Example

SYSA

Usage


Sysplex_DASD_Device Attributes 155

Sysplex_DASD_DeviceAttributes

IntroductionThis chapter defines the attributes in the Sysplex_DASD_Device attribute group.

AttributesUsing attributes to create DASD on demand custom workspaces . . . . . . 156Primary and secondary attributes for on demand custom workspaces. . . 156Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Average_Response_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Bypass_Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Cache_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Connect_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Disconnect_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161I/O_Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Indexed_VTOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162IOSQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Mount_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Pending_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Reconfiguration_Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166True_Percent_Busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Vary_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

20

Sysplex_DASD_Device Attribute Definitions



OverviewIn this unit you learn about the attributes in the Sysplex_DASD_Device attribute group. Use this attribute group to create situations that monitor MVS image-by-image activity for individual DASD devices.

Using attributes to create DASD on demand custom workspaces You can use the attributes in this group to create DASD on demand custom workspaces. When you create a DASD on demand custom workspace, the program uses the filtering criteria you specify to create the workspace.For additional information about DASD device collection filtering, see the chapter on filtering in the OMEGAMON XE for Sysplex Reference Guide, V220User’s Guide.

Primary and secondary attributes for on demand custom workspacesThe attributes in Sysplex_DASD_Device are either primary attributes or secondary attributes. The program uses





AddressThe device address for the system.

Valid Format

� Hexadecimal values.

� In the range 0000-FFFF

� When using this attribute group, use the hexadecimal format for device addresses. If you want to specifically collect device o5A1, then specify the value in the situation as 05A1.

Example

“05A1”

Usage




Average_Response_TimeThe average I/O response time, in milliseconds, of the device as seen by the system.

Valid Format



Example

“55.2”

Usage



Valid Values


� NO (DASD device collection filtering is used and data is filtered further for the custom workspace. The default is NO.)

Example

“NO”



Cache_StatusThe cache status of the device for the system.

Valid Format

� Active

� Inactive

� PendingActive

� PendingInactive

� TimedOut

Example

“Active”

Usage




Connect_TimeThe average connect time, in milliseconds, for a typical I/O.

Valid Format



Example

“21.1”

Usage




Disconnect_TimeThe average disconnect time, in milliseconds, for a typical I/O.

Disconnect time is the time that the I/O searches for the data that has been requested. It includes

� moving the device to the requested cylinder and track (SEEK + SET SECTOR)

� waiting for the record to rotate under the head (LATENCY)

� possible rotational delay as the device waits to reconnect to the channel (RPS delay)

Valid Format



Example

“11.3”

Usage




I/O_RateThe average I/O rate for the device.

Valid Format



Example

“12.8”

Usage


Indexed_VTOCThe status of indexed VTOC as seen from the system.

Valid Values

� DataUnavailable

� Enabled

� Disabled

� NotIndexed

Example

“Disabled”

Usage


On heavily used volumes with many data sets, an index to a volume table of contents may improve I/O performance.



IOSQThe average IOS queue time, in milliseconds, for a typical I/O.

Valid Format



Example

“15.5”

Usage


Mount_StatusThe mount status of the device for the system.

Valid Values� Public

� Private

� Storage

Example

“Public”

Usage




Pending_TimeThe average pending time, in milliseconds, for a typical I/O.


functions.


Example

“5.5”

Usage




Reconfiguration_StatusThe dynamic reconfiguration status of device for the system.

Valid Values� Static

� Dynamic

� InstallationStatic

� PinStatusUnknownStatic

� PinStatusUnknownDynamic

� PinStatusUnknownInstallationStatic

� PinnedStatic

� PinnedDynamic

� PinnedInstallationStatic

Usage




SystemThe name of the system that shares access to this device.

Valid Format



Example

“SYSA”

Usage


True_Percent_BusyThe device true busy value aggregated over all systems in the Sysplex.

Valid Format



Example

“25.5”

Usage




Vary_StatusThe vary status of device for the system.

Valid Values

� Online

� Offline

� PendingOffline

� Boxed

� NotReady

Example

“Online”

Usage


Sysplex_DASD_Device_ Collection_Filtering Attributes 169

Sysplex_DASD_Device_Collection_Filtering

Attributes

IntroductionThis chapter defines the attributes in the Sysplex_DASD_Device_Collection Filtering attribute group.

AttributesUsing attributes for DASD device collection filtering . . . . . . . . . . . . . . . . 171Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Average_Response_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Cache_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Connect_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Control_Unit_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Device_Contention_Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Device_Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Disconnect_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Group_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177I/O_Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Indexed_VTOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178IOSQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Mount_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Pending_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Reconfiguration_Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180True_Percent_Busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

21


Vary_Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Volume_Serial_Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182


Sysplex_DASD_Device_Collection_Filtering Attribute Definitions


OverviewIn this unit you learn about the attributes in the Sysplex_DASD_Device_Collection_Filtering attribute group. Use this attribute group to create situations that filter DASD devices.

Using attributes for DASD device collection filtering You can use the attributes in this group to create situations for DASD device collection filtering. When you create a situation for DASD device collection filtering, the program limits the amount of DASD device data sent to the CMS to the devices that meet the criteria of the situation. For additional information about DASD device collection filtering, see the chapter on filtering in the OMEGAMON XE for Sysplex Reference Guide, V220User’s Guide.



AddressThe device address for the system.

Valid Format

� Hexadecimal values.

� In the range 0000-FFFF

� When using this attribute group, use the hexadecimal format for device addresses. If you want to specifically collect device o5A1, then specify the value in the situation as 05A1.

Example

05A1

Usage


This attribute is not recommended for use in selecting devices. DASD volumes may be reorganized over device addresses from time to time.



Average_Response_TimeThe average I/O response time, in milliseconds, of the device as seen by the system.

Valid Format



Example

55.2

Usage

Use this attribute to select devices that might have problems.



Cache_StatusThe cache status of the device for the system.

Valid Format

� Active

� Inactive

� PendingActive

� PendingInactive

� TimedOut

Example

Active

Connect_TimeThe average connect time, in milliseconds, for a typical I/O.

Valid Format



Example

21.1



Control_Unit_TypeThe control unit type.

Valid Values

� Unknown

� 2105

� 3880-23

� 3990-1

� 3990-2

� 3990-3

� 3990-6

Example

3990-2

Device_Contention_IndexThe device contention index value. Device contention is an indication of I/O delay for this group caused by inter system contention for the device. The larger the number the more severe is the contention.

Valid Format



Example

1.35



Device_TypeThe device type.

Valid Format

� 3380

� 3390

Example

3380

Disconnect_TimeThe average disconnect time, in milliseconds, for a typical I/O.

Disconnect time is the time that the I/O searches for the data that has been requested. It includes

� moving the device to the requested cylinder and track (SEEK + SET SECTOR)

� waiting for the record to rotate under the head (LATENCY)

� possible rotational delay as the device waits to reconnect to the channel (RPS delay)

Valid Format



Example

11.3



Group_NameThe name of the DASD group.

Valid Format



Example

SGDB2X

I/O_RateThe average I/O rate for the device.

Valid Format



Example

12.8

Usage

Use this attribute for device filtering.



Indexed_VTOCThe status of indexed VTOC as seen from the system.

Valid Values

� DataUnavailable

� Enabled

� Disabled

� NotIndexed

Example

Disabled

Usage

On heavily used volumes with many data sets, an index to a volume table of contents may improve I/O performance.

IOSQThe average IOS queue time, in milliseconds, for a typical I/O.

Valid Format



Example

15.5



Mount_StatusThe mount status of the device for the system.

Valid Values� Public

� Private

� Storage

Example

Public

Pending_TimeThe average pending time, in milliseconds, for a typical I/O.


functions.


Example

5.5

Usage

Although shared DASD often causes high pending time, it can be caused by channel, control unit, or head of string being busy. Use this attribute for filtering.



Reconfiguration_StatusThe dynamic reconfiguration status of device for the system.

Valid Values� Static

� Dynamic

� InstallationStatic

� PinStatusUnknownStatic

� PinStatusUnknownDynamic

� PinStatusUnknownInstallationStatic

� PinnedStatic

� PinnedDynamic

� PinnedInstallationStatic

SystemThe name of the system that shares access to this device.

Valid Format



Example

SYSA

Usage

When used in a situation, this attribute will name the system that this filter should apply to. For example, you could construct a situation targeted for SYSA by including a predicate in the situation that indicates System=SYSA.

Candle does not recommend that you build situations using this attribute.



True_Percent_BusyThe device true busy value aggregated over all systems in the Sysplex.

Valid Format



Example

25.5

Vary_StatusThe vary status of device for the system.

Valid Values

� Online

� Offline

� PendingOffline

� Boxed

� NotReady

Example

Online




Valid Format



Example

VOL001

Usage

When used in a situation, insures that certain devices are included for collection. It should be specified as a predicate that is joined by the OR operator to all other predicates. You can also include a group of devices by ending the volume serial number with a asterisk (*). For example, SYS*, would select all devices beginning with the characters SYS*.

Sysplex_WLM_Service_ Class_Period Attributes 183

Sysplex_WLM_Service_Class_Period

Attributes

IntroductionThis chapter defines the attributes in the Sysplex_WLM_Service_Class_Period attribute group.

AttributesActive_I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Actual_Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Actual_Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Actual_Total . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Average_Response_Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Common_Page-In_Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Class_Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187CPU_Wait. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Cross_Memory_Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190ECB_Wait. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Enqueue_Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Goal_Importance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Goal_Percentile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Goal_Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Hiperspace_Page-In_Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

22


Attributes (continued)HSM_Backup/Migrate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194HSM_Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195HSM_Recall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195I/O_Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196JES_Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197MVS_Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Other_Waits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Performance_Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Private_Page-In_Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Resource_Group_Capping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Service_Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Stimer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Stimer_ECB_Wait. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201SWP_Not_Ready . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202SWP_Ready . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202System_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Tape_Mount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Transaction_Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Using_CPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205VIO_Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Worst_Performance_Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206WTOR_Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206


Sysplex_WLM_Service_Class_Period Attribute Definitions


OverviewIn this unit you learn about the attributes in the Sysplex_WLM_Service_Class_Period attribute group. Use this attribute group to create situations that monitor service class period performance relative to goals

Active_I/OIndicates the percent of time transactions in this service class period spent doing active I/O over all devices.

Valid Format



Example

5.4



Actual_HostActual host is the measured result for this service class period. Depending on the goal type, it is either a response time or a velocity.

Valid Format


� In the range of 0 to 2147483647, one decimal point precision. If you are setting thresholds for response time goals, express the value in milliseconds. For example, show 1.5 seconds as 1500 milliseconds. For velocity goals, the value should be between 0 and 100.

Example(s)

Velocity example:

85.3

Response time example:

1500

Actual_NetworkThe average network response time, in milliseconds, for the service class.

Valid Format


� Integer, in the range of 0 to 2147483647. If you use this value in a situation, this value should be entered in milliseconds.

Example

1200



Actual_TotalThe total actual value, in milliseconds, for the service class period. This indicates the total actual value for the service class period. Actual Total presents the measured result including network delay when applicable (for response time oriented goals). The average measured network delay is added to the measured host response time.

Valid Format


� Integer, in the range of 0 to 2147483647. If you use this to set a situation threshold, this value should be expressed in milliseconds.

Example

2200

Average_Response_TimeThe average host response time of transactions in this service class.

Valid Format


� Integer, in the range of 0 to 2147483647. If you use this as a threshold in a situation, this value should be expressed in milliseconds.

Example

1200

Class_Flag Categorizes the service class based on the general types of transactions that are managed by it.

Valid Format



� Transaction - service class manages subsystem transactions such as CICS transactions or IMS transactions.

� Address Space - service class handles workloads such as batch jobs and started tasks.

� TSO- service class handles TSO users.

Example

TSO



Common_Page-In_WaitThe wait time for PLPA or common page-in. This indicates the percentage of time transactions in this service class spent waited for page in delays for common storage pages.

Valid Format


� In the range of -2147483647 to 2147483647, one decimal point precision.

Example

10.3

CPU_WaitThe total wait time on the active CPU dispatching queue.

Valid Format


� In the range of -2147483647 to 2147483647, one decimal point precision. This indicates the percentage of time transactions in this service class waited for CPU access.

Example

21.8



Cross_Memory_WaitThe total wait time for a cross-memory request. This indicates the percentage of time transactions in this service class waited for cross memory request delays.

Valid Format



Example

3.4

DurationThe number of CPU service units the period may use before work is passed to the next period.

Valid Format



Example

200



ECB_WaitThe total time waiting for some unknown event. This indicates the percentage of time transactions in this service class waited for an unspecified event.

Valid Format



Example

30.4

Enqueue_WaitIndicates the percentage of time transactions in this service class spent waiting for enqueue delays.

Valid Format



Example

5.7



GoalDescribes the service class period’s goal as a complete text string, such as “Pct Resp 95% < 400.0ms”.

Valid Format



Example

Pct Resp 95% < 400.0 ms

Goal_ImportanceThe importance level goal for the service class period. Goal importance for the service class is set as part of the WLM policy. When WLM cannot satisfy all goals, it will try to meet goals for more important service class periods first.

Valid Values

� Highest

� High

� Medium

� Low

� Lowest

Example

Medium



Goal_PercentileThe percentage of work in the service class period that completed within the expected response time. Goal percentile is valid for percentile response time goals only. It is the percentage of transactions that should complete within the goal value. This is set by the system administrator for this service class when the WLM policy is defined. It is not a measured result.

Valid Format


� Integer, in the range of 0 - 65535.

Example

90

Goal_TypeThe type of goal for the service class period.

Valid Values� SysGoal

� Discret

� Velocity

� AveResp

� PctResp

Example

PctResp



Hiperspace_Page-In_WaitIndicates the percentage of time transactions in this service class spent waiting for page in delays for hiperspace pages.

Valid Format



Example

3.4

HSM_Backup/MigrateThe total wait time for HSM backup and/or migrate requests. This indicates the percentage of time transactions in this service class waited for Hierarchical Storage Manager backup and migrate delays.

Valid Format



Example

1.4



HSM_OtherThe total wait time for other HSM requests and processing. This indicates the percentage of time transactions in this service class waited for Hierarchical Storage Manager miscellaneous delays such as recovery, JES3 control, interval locate, read control record, etc.

Valid Format



Example

0.4

HSM_RecallIndicates the percentage of time transactions in this service class spent waiting for Hierarchical Storage Manager recall delays.

Valid Format



Example

2.4



I/O_WaitThe I/O wait rate for the service class period. This indicates the percentage of time transactions in this service class waited for I/O over all devices.

Valid Format



Example

12.1

JES_WaitThe total wait time for JES. This indicates the percentage of time transactions in this service class waited for JES delays.

Valid Format



Example

2.4




Valid Values



Example

SYSTEM

MVS_LockThe wait time for MVS locks. This indicates the percentage of time transactions in this service class waited the MVS lock.

Valid Format


� In the range of 0 to100, one decimal point precision.

Example

1.1



Other_WaitsThe total wait time for other reasons. This entry should be uncommented. It indicates the percentage of time transactions in this service class spent waiting for miscellaneous other conditions, like disk mounts, task quiescence, mass storage devices, etc.

Valid Format



Example

3.1

Performance_IndexA measure of how the class and period are performing in relation to the goal. Values less than or equal to 1.00 indicate that the goal has been achieved. Values greater than 1.00 indicate that the goal has been missed. The larger the index, the further the service class period from the goal.

Valid Format



Example

0.85



PeriodThe service class period number. If specifying a situation where the values should represent the service class as a whole, then specify Period =”SUM”. This is used when building a situation for workflow thresholds at the service class level.

Valid Format


� Integer, in the range of 1 - 8.

Example

1

Private_Page-In_WaitThe wait time for a private area page-in. This indicates the percentage of time transactions in this service class are waiting for page-in delays for private area pages.

Valid Format



Example

0.5



Resource_Group_CappingThe total wait time for CPU due to resource group maximum. This indicates the percentage of time transactions in this service class are waiting for Resource Group Capping delays.

Valid Format



Example

0.3

Service_ClassThe name of the service class being reported on.

Valid Format



Example

TSO



StimerThe total percentage of time waiting for the stimer. This indicates the percentage of time transactions in this service class waited for a time limit.

Valid Format



Example

10.3

Stimer_ECB_WaitThe total wait time for some unknown event and the stimer. This indicates the percentage of time transactions in this service class waited for an unspecified event or a time limit.

Valid Format



Example

65.1



SWP_Not_ReadyThe time is swapped and not ready for swap-in. This indicates the percentage of time transactions in this service class waited in a “not ready” swapped state.

Valid Format



Example

0.1

SWP_ReadyThe total time waiting and ready for swap-in. This indicates the percentage of time transactions in this service class waited in a “ready” swapped state.

Valid Format



Example

0.7



System_NameThe name of the MVS system to which the data in this row applies.

Valid Format



Example

SYSA

Tape_MountThe total percentage of time waiting for tape mounts. This indicates the percentage of time transactions in this service class waited for tapes to be mounted.

Valid Format



Example

3.6



Transaction_RateThe number of transactions per second currently being processed in the service class period.

Valid Format



Example

3.7

Using_CPUThe total time using the CPU. This indicates the percentage of time transactions in this service class spent using the CPU.

Valid Format



Example

2.3



VelocityThe velocity of the service class period.

Valid Format



Example

65.3

VIO_WaitThe wait time for virtual I/O processing. This indicates the percentage of time transactions in this service class are waiting for virtual I/O delays.

Valid Format



Example

0.2



WorkloadThe name of the workload that contains the service class.

Valid Format



Example

BATCH

Worst_Performance_IndexThe performance index value scaled to hundredths, calculated for this service class on an individual MVS image.

Valid Format



Example

2.75

WTOR_WaitThe wait time for a reply to operator message. This indicates the percentage of time transactions in this service class are waiting for virtual I/O delays.

Valid Format



Example

2.2

Universal_Time Attributes 207

Universal_Time Attributes

IntroductionThis chapter defines the attributes in the Universal_Time attribute group.

AttributesDate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Day_Of_Month. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Day_Of_Week . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Hours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Minutes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Month_Of_Year . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

23

Universal_Time Attribute Definitions



OverviewThe Universal_Time attributes show the time and date at the hub CMS to which the agent is connected. For example, if you are running CandleNet Portalin London and monitoring a system connect to the CMS in Cairo, the local Cairo time and date will be returned. These attributes are useful for action situations triggered by time, or views that correlate the local time of systems in different time zones.

Note: When making date comparisons, in order to achieve accurate results, you must use the Timestamp attribute rather than either the Local_Time or Universal_Time attribute.

DateThe date attribute is no longer valid. In the situations you created, replace the Date attribute with the Timestamp attribute.

Day_Of_MonthThe day in the month at the hub CMS location when the data was sampled.

Valid Format


Example

01



Day_Of_WeekThe numeric representation for the day in the week at the hub CMS location when the data was sampled.

Valid Format

A 2-digit value in the range 01 (Sunday) to 07 (Saturday).

Example

02

HoursThe hour in the day at the hub CMS location when the data was sampled.

Valid Format


Example

10

MinutesThe minute in the hour at the hub CMS location when the data was sampled.

Valid Format


Example

05



Month_Of_YearThe numeric representation of the month in the year at the hub CMS location when the data was sampled.

Valid Format

A numeric value in the range 01 (January) to 12 (December).

Example

04

Seconds The seconds into the minute at the hub CMS location when the data was sampled.

Valid Format


Example

02

Timestamp The date and time the CMS samples the data.

Valid Format

The timestamp format for the SCAN and STR functions is CYYMMDDHHMMSSmmm (as in 1020415074501000 for April 15, 2002 at 07:45:01) where:

C = Century (0 for 20th, 1 for 21st)Y = YearM = MonthD = DayH = HourM = Minute



S = Secondm = millisecond

Example

1020415074501000

WLM_Environment Attributes 213

WLM_Environment Attributes

IntroductionThis chapter defines the attributes in the WLM_Environment attribute group.

AttributesMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214MVS_System_Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

24

WLM_Environment Attribute Definitions


WLM_Environment Attribute Definitions

OverviewIn this unit you learn about the attributes in the WLM_Environment attribute group. Use this attribute group to create situations that monitor Workload Manager mode on MVS images.

ModeThe workload manager mode.

Valid Values� Goal

� Compatibility

Example

Goal

MVS_System_NameThe name of the MVS system.

Valid Format



Example

SYSA

XCF_Group Attributes 215

XCF_Group Attributes

IntroductionThis chapter defines the attributes in the XCF_Group attribute group.

AttributesGroup_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Member_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Problem_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

25

XCF_Group Attribute Definitions



OverviewIn this unit you learn about the attributes in the XCF_Group attribute group. Use this attribute group to create situations that monitor connected user counts and problem counts for XCF groups.

Group_NameThe name of the group to which the member belongs.

Valid Format



Example

SYSJES

Member_CountThe number of members in the group.

Valid Format


� In the range of 0 to 2147483647.

Example

6

XCF_Group Attributes 217


Problem_CountThe number of members in the group reporting a problem status.

Valid Format



Example

1

XCF_Members Attributes 219

XCF_Members Attributes

IntroductionThis chapter defines the attributes in the XCF_Members attribute group.

AttributesGroup_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220Job_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220Member_Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221Signals_Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221Signals_Sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Status_Checking_Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222System_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

26

XCF_Members Attribute Definitions



OverviewIn this unit you learn about the attributes in the XCF_Members attribute group. Use this attribute group to create situations that monitor the status and activity of XCF group member address spaces.

Group_NameThe name of the group to which the member belongs.

Valid Format



Example

SYSJES

Job_NameA string that describes the address space job name of the task using this XCF member name.

Valid Format

� Simple text string

� 1 - 8 characters, starting with an alphabetic character and using only special characters as described in the MVS JCL manual.

Example

JESXCF



Member_NameThe name of the member itself.

Valid Format



Example

SYSA

Signals_ReceivedThe number of signals received by the member.

Valid Format



Example

4

Signals_SentThe number of signals sent by the member.

Valid Format



Example

2



StatusThe status of the member.

Valid Values

� Missing - Information about this member's status is missing.

� Created - A member in a created state is known to XCF, but cannot use XCF services. It can become an active user through the IXCJOIN macro.

� ActiveState - An active member is known to XCF and can use XCF services.

� Quiesced - A member in the quiesced state is disassociated from XCF services, but XCF still maintains a record of the member's existence. The IXCQUIES macro places a member in the quiesced state.

� Failed - A member in the failed state is one whose associated task, job step task, address space, or system terminated before the member was explicitly deactivated by invoking an XCF service. When a member is in the failed state, other members can infer that the member did not have an opportunity to clean up its own resources, and another member should take recovery action.

� MonitorRemoved - Monitoring has been removed for this member.

� SysTermination - XCF system containing member is terminating.

Example

ActiveState

Status_Checking_IntervalAn optional parameter that specifies the status-checking interval in seconds. It determines the length of time that can elapse with no change to the status field before scheduling the user status routine.

Valid Format� Numeric

� Value should be expressed in seconds, a multiple of 100 scaled to two decimal point precision.



Example

A value of 3000 seconds would be shown as:

300.00



System_NameThe name of the MVS image where the member is executing.

Valid Format



Example

“SYSA”

XCF_Paths Attributes 227

XCF_Paths Attributes

IntroductionThis chapter defines the attributes in the XCF_Paths attribute group.

AttributesDestination_Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228Message_Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Origin_Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Restart_Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Retry_Limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Retry_Percent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Signals_Pending_Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Signals_Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Signals_Sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Storage_In_Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233System_From . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234System_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234System_To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Times_Buffer_Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Times_Path_Busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Transport_Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

27

XCF_Paths Attribute Definitions



OverviewIn this unit you learn about the attributes in the XCF_Paths attribute group. Use this attribute group to create situations that monitor the status and activity of XCF signaling paths between MVS images.

Destination_DeviceThe device number of the destination device. Destination devices may be coupling facility structures as well as CTC devices. In this case the designation can be either ListStructure (which implies the System_To value is unknown) or “CFList”. It is also possible that the destination device is unknown at the time the data is collected.

Valid Format


� To designate a structure in a situation for Destination Devices use “CFST” to represent “ListStructure” or “LIST” to represent “CFList”.


Example

CTC Device example:

07F6

Structure example:

LIST

Goal_Value_Host The goal value for the service class period. If the goal type is an average or percentile response time, then this value is the target time in milliseconds. If the goal type is velocity, then this is the target percentage.

Valid Format





Example

25



Message_LimitThe maximum number of messages allowed to be sent by the signalling path. This is the maximum number of messages concurrently in progress.

Valid Format



Example

750

Origin_DeviceThe device number of the originating device. Origin devices may be coupling facility structures as well as CTC devices. In this case the designation can be either “ListStrcucture” (which implies the System_To value is unknown) or “CFList”.

Valid Format


� To designate a structure in a situation for Origin Device use “CFST” to represent ListStructure or “LIST” to represent “CFList”.


Example

CTD device example:

07F6

Structure example:

LIST



Restart_CountThe number of times XCF restarted the signalling path.

Valid Format



Example

1

Retry_LimitThe retry limit for the signalling path.

Valid Format



Example

60

Retry_PercentThe percentage of the retry limit reached by the signalling path.

Valid Format


� Integer, in the range of 0.0 to 100.0, one decimal point precision.

Example

25.5



Signals_Pending_TransferThe number of messages waiting to be sent through the signalling path.

Valid Format



Example

2

Signals_ReceivedThe number of messages received through the signalling path.

Valid Format



Example

1582

Signals_SentThe number of messages sent through the signalling path.

Valid Format



Example

2176



StatusThe status of the signalling path.

Valid Values

� Starting - Validating and initializing path hardware.

� Restarting - Making path ready (again) for use.

� Working - Path is capable of being used.

� Stopped - Stopping use, in the process of being removed from service.

� WaitingForComp - Waiting for completion of initial protocol used to establish communication link.

� NotOperational - Not operational. Path defined to XCF but not usable until hardware and/or definition problems are resolved.

� Failed - Stop failed, intervention required.

� Rebuilding -

� Quiescing

� Quiesced

Example

Starting

Storage_In_UseThe amount of storage that is in use by the path.

Valid Format



� Value is expressed as a count of 1K buffers.

Example

280 KB is expressed as:



Storage_In_Use=280

System_FromThe name of the MVS image from which the signalling path originates.

Valid Format



Example

SYSA

System_Name Path as seen from the system. Each path has a sending and receiving system. This attribute indicates which of these systems is providing the data observation.

Valid Format



Example

SYSA

System_ToThe name of the MVS image that is the destination of the signalling path.

Valid Format



Example

SYSB



Times_Buffer_UnavailableThe number of times message receipt was delayed because no buffer was available.

Valid Format



Example

1

Times_Path_BusyThe number of sends issued when the path was busy.


functions.


Example

1

Transport_ClassThe name of a transport class associated with the signalling path.

Valid Format



Example

DEFAULT

XCF_System Attributes 237

XCF_System Attributes

IntroductionThis chapter defines the attributes in the XCF_System attribute group.

AttributesMonitoring_Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Operator_Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Systemically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239System_Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

28

XCF_System Attribute Definitions



OverviewIn this unit you learn about the attributes in the XCF_System attribute group. Use this attribute group to create situations that monitor the status of MVS images in a Sysplex as it relates to the XCF communication feature.

Monitoring_IntervalThe length of time, in seconds, it takes XCF to detect a failure in the Sysplex.

Valid Format


� Number, in the range of 0 to 2147483647, with two decimal point precision. When you use the attribute in situations, specify the value in seconds with precision to hundredth of seconds.

Example

90.00

Operator_IntervalThe length of time, in seconds, it takes XCF to notify the operator of a failure in the Sysplex.

Valid Format


� Number, in the range of 0 to 2147483647, with two decimal point precision. When you use the attribute in situations, specify the value in seconds with precision to hundredth of seconds.

Example

90.00

XCF_System Attributes 239


StatusThe status of the MVS image.

Valid Values

� Active

� BeingRemoved

� Missing

� Local

� Cleanup

� Unknown

Example

Active

SystemicallyThe MVS release level running on this system image.

Valid Format



Example

OS/390 02.05.00



System_NameThe name of an MVS image in the Sysplex.

Valid Format



Example

SYSA

XCF_System_Statistics Attributes 241

XCF_System_StatisticsAttributes

IntroductionThis chapter defines the attributes in the XCF_System_Statistics attribute group.

AttributesBuffer_Length. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Percent_Fit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Percent_Degraded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Percent_Smaller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Percent_Larger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Signals_Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Signals_Sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244System_From . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245System_To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Transport_Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Times_Buffer_Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Times_Path_Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

29




OverviewUse the XCF System Statistics attributes to create situations that monitor XCF signals (messages) sent between MVS systems in the sysplex and transport class buffer utilization. The situations you create using these attributes let you identify where changes to transport class definitions can be made to optimize XCF performance and resource utilization.

Buffer_Length Buffer length for the indicated transport class.

Valid Format



Example

50

Percent_Fit Percent of messages sent where the message length fit the transport class buffer length. Valid value is a percentage with one decimal point precision.

Valid Format



Example

32.0



Percent_Degraded Percent of messages sent where the message length was larger than the transport class buffer length and caused degraded performance.

Valid Format



Example

13.0

Percent_Smaller Percent of messages sent where the message length was smaller than the transport class buffer length.

Valid Format



Example

55.0

Percent_Larger Percent of messages sent where the message length was larger than the transport class buffer length.

Valid Format





Example

32.0

Signals_Received Number of messages received.

Valid Format



Example

50

Signals_Sent Number of messages sent.

Valid Format



Example

70

System_From Name of the MVS System where the messages originated.

Valid Format



Example



WLAG

System Name of the MVS System on which data was collected.

Valid Format



Example

SYSA

System_To Name of the MVS System that is the destination of the messages.

Valid Format



Example

SYSGT

Transport_Class Transport class used for messages sent. Transport classes are used to segregate message traffic according to message size or performance needs, and may be used to dedicate signalling paths to particular workloads.

Valid Format



Example

CLASSA



Times_Buffer_Unavailable Number of times a 'no buffer' condition occurred for the indicated transport class.

Valid Format



Example

25

Times_Path_Unavailable Number of times a 'no path' condition occurred for the indicated transport class.

Valid Format



Example

32

Guide to Candle Customer Support 247

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249– 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254– Assigned Support Center Representative (ASCR)

– Maintenance Assessment Services (MAS)

– Multi-Services Manager (MSM)

A


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


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, via 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

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



set their own Severity Levels when contacting a support center. This ensures that we respond according to your individual business requirements.

Candle has established the following service-level objectives:

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.

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

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.



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.

Call Status Severity 1 Goal

Severity 2 Goal

Severity 3 Goal

Severity 4 Goal

Severity 5Goal

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.



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.

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:

� Unlimited multi-language defect, installation and operations support� eSupport using the World Wide Web� Regularly scheduled product updates and maintenance provided at no

additional charge� Over 200 specialized technicians providing expert support for your

Candle products

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:

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

� 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

� 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


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 257

Index

AAdobe portable document format 14Adobe® Portable Document Format 13ASCR

assigned support center representative 254

assigned support center representativeASCR 254

attribute groupsCF_Clients 26CF_Path 32CF_Policy 36CF_Structure_To_MVS_System 40CF_Structures 47CF_Systems 67Global_Enqueues 80GRS 88introduction 21list of 22Report_Classes 100Resource_Groups 104Service_Class_Address_Spaces 108Service_Class_Enqueue_Workflow_Analys

is 114Service_Class_I/O_Workflow_Analysis 11

8Service_Class_Subsys_Workflow_Analysis

125Service_Definition 134Sysplex_DASD 139Sysplex_DASD_Device 157, 172Sysplex_DASD_Group 148, 175Sysplex_WLM_Service_Class_Period 185Universal_Time 208WLM_Environment 214XCF_Group 216XCF_Members 220XCF_Paths 228

XCF_System 238

CCF_Clients Group Attributes 25CF_Path Group Attributes 31CF_Policy Group Attributes 35CF_Structure_To_MVS_System Group

Attributes 39CF_Structures Group Attributes 45CF_Systems Group Attributes 65customer service

telephone support 249customer support

base maintenance plan 249contact information 256enhanced support services 254eSupport 250severity levels 250

Eenhancements

Version 200 17eSupport

customer support 250

GGlobal_Enqueues Group Attributes 79GRS Group Attributes 87

LList

attribute groups 22Local_Time Attributes 93

Mmaintenance assessment service


MAS 254MAS

maintenance assessment service 254MSM

multi-services manager 254multi-services manager

MSM 254

Nnew features

Version 200 17

Pprinting problems 14

RReport_Classes Group Attributes 99Resource_Groups Group Attributes 103

SService_Class_Address_Spaces Group

Attributes 107Service_Class_Enqueue_Workflow_Analysis

Group Attributes 113Service_Class_I/O_Workflow_Analysis

Group Attributes 117Service_Class_Subsys_Workflow_Analysis

Group Attributes 123Service_Definition Group Attributes 133severity levels

customer support 250Sysplex_DASD Group Attributes 137Sysplex_DASD_Device Group

Attributes 155, 169Sysplex_DASD_Group Group

Attributes 145Sysplex_WLM_Service_Class_Period Group

Attributes 183

Ttelephone support

customer service 249

UUniversal_Time Attributes 207

VVersion 200

what’s new 17

Wwhat’s new in Version 200 17WLM_Environment Group Attributes 213workspaces

associating attributes with 23

XXCF_Group Group Attributes 215XCF_Members Group Attributes 219XCF_Paths Group Attributes 227XCF_System Group Attributes 237, 241

OMEGAMON XE for Sysplex Reference Guide, V220 -...

Documents

Transcript of OMEGAMON XE for Sysplex Reference Guide, V220 -...