omegamon xe for storage user’s guidഀ攀Ⰰ...

User’s GuideOMEGAMON® XE for Storage

Version 100

GC32-9317-00

August 2004

Candle Corporation100 Sepulveda Blvd.

El Segundo, California 90245-9796

2 OMEGAMON XE for Storage User’s Guide, Version 100

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/REMOTE, Availability Command Center, Candle, Candle CIRCUIT, Candle Command Center, Candle Direct logo, Candle eDelivery, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management Workstation, CandleLight, CandleNet, CandleNet Command Center, CandleNet eBusiness Platform, CandleNet Portal, CL/CONFERENCE, CL/SUPERSESSION, CommandWatch, CT, CT/Data Server, CT/DS, DELTAMON, DEXAN, eBA, eBA*ServiceMonitor, eBA*ServiceNetwork, eBusiness at the speed of light, eBusiness Assurance, eBusiness Institute, ELX, EPILOG, ESRA, ETEWatch, IntelliWatch, IntelliWatch Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAMON Monitoring Agents, OMEGAVIEW, OMEGAVIEW II, PQEdit, Response Time Network, Roma, SitePulse, Solutions for Networked Applications, Solutions for Networked Businesses, TMA2000, Transplex, and Volcano.Trademarks and service marks of Candle Corporation: AF/Advanced Notification, AF/PERFORMER, Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED FACILITIES, Availability Management Systems, Business Services Composer, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle CommandPro, Candle eSupport, Candle Insight, Candle InterFlow, Candle Managing what matters most, Candle Service Suite, Candle Technologies, CandleNet, CandleNet 2000, CandleNet Conversion, CandleNet eBP, CandleNet eBP Access for S.W.I.F.T., CandleNet eBP Administrator, CandleNet eBP Broker Access for Mercator or MQSI, 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 Administrator, CandleNet eBusiness Platform Connector, CandleNet eBusiness Platform Connectors, CandleNet eBusiness Platform Powered by Roma Technology, CandleNet eBusiness Platform Service Directory, Candle Vision, CCC, CCP, CCR2, 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, e2e, eBA*SE, eBAA, eBAAuditor, eBAN, eBANetwork, eBAAPractice, eBP, eBusiness Assurance Network, eBusiness at the speed of light, eBusiness at the speed of light logo, eBusiness Exchange, eBX, End-to-End, eNotification, ENTERPRISE, Enterprise Candle Command Center, Enterprise Candle Management Workstation, Enterprise Reporter Plus, ER+, ERPNet, ETEWatch Customizer, HostBridge, InterFlow, Candle InterFlow, Lava Console, Managing what matters most, MessageMate, Messaging Mastered, Millennium Management Blueprint, MMNA, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, NC4, NetGlue, NetGlue Extra, NetMirror, NetScheduler, New Times, New Team, New Readiness, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager, OMEGAMON/e, OMEGAMON Management Center, OSM, PathWAI, PC COMPANION, Performance Pac, Powered by Roma Technology, PowerQ, PQConfiguration, PQScope, 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, Tracer, Unified Directory Services, WayPoint, and ZCopy.Trademarks and registered trademarks of other companies: AIX, DB2, MQSeries and WebSphere are registered trademarks of International Business Machines Corporation. Citrix, WinFrame, and ICA are registered trademarks of Citrix Systems, Inc. Multi-Win and MetaFrame are trademarks of Citrix Systems, Inc. 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 may be trademarks or registered trademarks of their respective owners.

Copyright © July 2004, 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

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 1. Introducing OMEGAMON XE for Storage . . . . . . . . . . . . . . . . 13OMEGAMON XE for Storage Operating Environment . . . . . . . . . . . 14OMEGAMON XE for Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 2. Learning About OMEGAMON XE for Storage . . . . . . . . . . . . . 23Understanding Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Understanding OMEGAMON XE for Storage Information . . . . . . . . . 27Creating Take Action Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 31OMEGAMON XE for Storage Predefined Situations . . . . . . . . . . . . . 32

Chapter 3. OMEGAMON XE for Storage Situations . . . . . . . . . . . . . . . . . 35OMEGAMON XE for Storage Situations . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 4. OMEGAMON XE for Storage Workspaces . . . . . . . . . . . . . . . . 51OMEGAMON XE for Storage Workspaces. . . . . . . . . . . . . . . . . . . . . 54Application Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Cache CU Performance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Cache CU Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Channel Path Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61HSM Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Logical Control Unit Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65SMS Configuration Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67SMS Storage Groups Performance Report. . . . . . . . . . . . . . . . . . . . . 68SMS Storage Groups Space Report. . . . . . . . . . . . . . . . . . . . . . . . . . 70Tape Group Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71User DASD Groups Performance Report . . . . . . . . . . . . . . . . . . . . . . 73

Contents


User DASD Groups Space Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Virtual Tape Subsystems Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Preface 5

Preface

This guide provides detailed information about OMEGAMON® XE for Storage.

This guide serves the following audiences:

� system administrators

� system programmers

� network administrators

� operators

� Candle sales force and field support

Why you should use this guideThis guide helps you understand how to use OMEGAMON XE for Storage. It supplements the online Help provided with OMEGAMON XE for Storage.

Candle recommends that you refer to this document whenever you need additional information about the OMEGAMON XE for Storage product, its attributes, workspaces and situations.

P


Contents of this guideThis manual contains

� an introduction to OMEGAMON XE for Storage

� an introduction to the OMEGAMON XE for Storage attributes, workspaces, and predefined situations

� detailed information about OMEGAMON XE for Storage workspaces

� information that will assist you in contacting Candle Customer Support

Preface 7

Documentation Set

Documentation Set

OverviewCandle provides this User’s Guide for OMEGAMON XE for Storage. It supplements the online help provided with the product.

You may wish to review manuals that comprise the OMEGAMON II for SMS documentation set. These manuals are useful should you need to review information provided by the underlying OMEGAMON II for SMS product.

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

� technical documentation CD-ROM that came with your product

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

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

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

We would like to hear from youCandle welcomes your comments and suggestions for changes or additions to the documentation set. A user comment form, located at the back of each manual, provides simple instructions for communicating with the Candle Information Development department. You can also send email to [email protected]. Please include "OMEGAMON XE for Storage User’s Guide, Version 100" in the subject line.

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 9


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



Documentation Conventions



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

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

Required blanksThe slashed-b (!) character in examples represents a required blank. The following example illustrates the location of two required blanks.

!!!!eBA*ServiceMonitor!!!!0990221161551000

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

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

LOGON APPLID (cccccccc)

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

Note: In ordinary text, variable names appear in italics.

Preface 11


SymbolsThe following symbols may appear in command syntax:

Table 1. Symbols in Command Syntax

Symbol Usage

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

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

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

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

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

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

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

_ Default values are underscored. Example:

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

Introducing OMEGAMON XE for Storage 13

IntroducingOMEGAMON XE for Storage

IntroductionThis chapter introduces you to OMEGAMON XE for Storage.

Chapter contents

OMEGAMON XE for Storage Operating Environment . . . . . . . . . . . . . . . . . . . . . 14

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14What is OMEGAMON XE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Components of the environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15What is CandleNet Portal? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15What is the Candle Management Workstation?. . . . . . . . . . . . . . . . . . . . . . . . 16Further Information about the CMW and CandleNet Portal . . . . . . . . . . . . . . 16

OMEGAMON XE for Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17User interface to OMEGAMON XE for Storage. . . . . . . . . . . . . . . . . . . . . . . . 17Advanced monitoring facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Reporting capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Historical data collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18What is OMEGAMON DE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19The Workflow Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Benefits of using OMEGAMON XE for Storage. . . . . . . . . . . . . . . . . . . . . . . . 20Prerequisite knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Planning and installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

1

OMEGAMON XE for Storage Operating Environment



Overview

OMEGAMON XE for Storage can help you to address the increasing challenges presented by today’s technical environment. In this unit you learn about the operating environment in which the OMEGAMON XE for Storage resides.

What is OMEGAMON XE?OMEGAMON XE is a suite of products that assists you in monitoring your mainframe and distributed systems on a variety of platforms using a variety of workstations.

It provides a way to monitor the availability and performance of all the systems in your enterprise from one or several designated workstations. It provides many useful reports you can use to track trends and understand and troubleshoot system problems. You can use OMEGAMON XE to

� establish your own performance thresholds� create situations, which are conditions to monitor� create and send commands to systems in your managed enterprise by

means of the Take Action feature. Take Action enables you to, for instance, restart a process that is not functioning properly or send a message

� create comprehensive reports about system conditions� monitor for alerts on the systems and platforms you are managing� trace the causes leading up to an alert

� define your own queries, using the attributes provided by OMEGAMON XE for Storage, to monitor conditions of particular interest to you



Components of the environmentThe client-server-agent implementation includes

� a client, that can be

– a CandleNet Portal™ workstation

– a Candle Management Workstation® (CMW™), used to manage work groups and work lists, data items, and managed system lists

� a server, known as the Candle Management Server® (CMS™)

� a CandleNet Portal server that performs common CandleNet Portal functions and serves to lighten the CandleNet Portal client

� monitoring agents that collect and distribute data to a CMS. The OMEGAMON XE for Storage is such an agent.

An additional feature package, OMEGAMON® DE, is available with OMEGAMON XE. This feature package provides all the capability of OMEGAMON XE, plus additional capabilities as described later in this chapter.

What is CandleNet Portal?CandleNet Portal is the user interface into your OMEGAMON XE product set. It provides a view of your enterprise from which you can drill down to more closely examine components of your systems environment. Its application window consists of a Navigator that shows all the systems in your enterprise where Candle agents are installed, and a workspace that includes table and chart views of system and application conditions.

CandleNet Portal runs situations at regular intervals to check that your applications and system resources are running, and running well. A failed test causes event indicators to appear in the Navigator.

CandleNet Portal offers two modes of operation: desktop and browser. In desktop mode, the application software is installed on your system. In browser mode, the system administrator installs the application on the web server and you start CandleNet Portal from your browser. In browser mode, the software is downloaded to your system the first time you log on to CandleNet Portal, and thereafter only when there are software updates.



What is the Candle Management Workstation?When using OMEGAMON XE for Storage, you use the Candle Management Workstation (CMW) to manage work groups and work lists, data items, and managed system lists.

Further Information about the CMW and CandleNet PortalFor further information about CandleNet Portal, refer to the product’s online Help and to Administering OMEGAMON Products: CandleNet Portal.

Further information about using the CMW for user administration can be found in the Candle Management Workstation Administrator’s Guide as well as in the CMW online Help.

If you are an experienced CMW user, you should review the CandleNet Portal help topic called “CMW Users.” This topic addresses the similarities and differences of these user interfaces, provides guidance about each interface’s functionality, and a cross-reference listing that clarifies the products’ terminology.


OMEGAMON XE for Storage


OverviewThis unit describes OMEGAMON XE for Storage and the benefits it can provide to your organization.

User interface to OMEGAMON XE for StorageOMEGAMON XE for Storage uses the CandleNet Portal interface on Windows NT, Windows 98, or Windows 2000.

Through the user interface, you have a consolidated view of multiple instances of OMEGAMON XE for Storage, each running on an individual image. This permits you to monitor your MVS environment and resolve performance issues using

� product-specific attributes

� product-specific reports

Advanced monitoring facilitiesOMEGAMON XE for Storage includes these advanced monitoring facilities:

� an at-a-glance picture providing the status of various aspects of your system

� the ability to simultaneously monitor multiple instances of MVS, each running on an individual image, from one or more designated workstations

� the ability to define situations based on user-specified thresholds or on the status of a given resource to raise different types of alerts; for example, critical, warning, and informational



Reporting capabilityOMEGAMON XE for Storage includes a reporting capability that provides information displayed in the following named workspaces:

� Application Summary Report

� Cache CU Performance Report

� Cache CU Status Report

� Channel Path Report

� HSM Status Report

� Logical Control Unit Report

� SMS Configuration Report

� SMS Storage Groups Performance Report

� SMS Storage Groups Space Report

� Tape Group Report

� User DASD Groups Performance Report

� User DASD Groups Space Report

� Virtual Tape Systems Report

Within a given workspace, information may appear in tabular form like a CMW report. CandleNet Portal refers to this tabular format for information as a table view. Information may also be displayed in the workspace as charts, graphs, or other formats you can specify. All of the OMEGAMON XE for Storage workspaces can record history.

For a complete list and description of all of the OMEGAMON XE for Storage workspaces, see Chapter 4 of this book.

Historical data collectionYou can use the facilities of CandleNet Portal’s historical data collection function to store and save the data being collected by your OMEGAMON XE for Storage agent or agents. The historical data collection function permits you to specify

� the attribute group or groups for which data is to be collected



� the interval at which data is to be collected

� the interval at which data is to be warehoused (if you choose to do so)

� the location (either at the agent or at the CMS) at which the collected data is to be stored

Information about using the Historical Data Collection function can be found in the CandleNet Portal online Help and in the Historical Data Collection Guide for OMEGAMON XE and CandleNet Command Center.

To ensure that data samplings are saved to populate your predefined historical workspaces, you must first configure and start historical data collection.This requirement does not apply to workspaces using attributes groups that are historical in nature and show all their entries without you having to start data collection. See the Historical Data Collection Guide for OMEGAMON XE and CandleNet Command Center for more information.

What is OMEGAMON DE?The OMEGAMON® DE feature package for CandleNet Portal offers a dashboard view of your enterprise. This feature provides a single point of control from which you can manage the resources your business-critical applications rely on, including a range of operating systems, servers, databases, mainframes, and Web components. It enables you to pull together the data and functionality built into all the Candle monitoring solutions, such as OMEGAMON XE for Storage. OMEGAMON DE provides all the capability of OMEGAMON XE, plus these additional capabilities:

� Multiple applications can be displayed in one workspace

In a single workspace, you can build a table or chart with data from one type of monitoring agent, and another table or chart with data from a different agent. Within that workspace, you can show views from as many different agent types as are included on that branch of the Navigator.

� You can link application workspaces

You can define a link from a workspace associated with one type of monitoring agent to a workspace associated with another type of agent.

� You can define enterprise-specific Navigator views



The Navigator physical view shows the hierarchy of your managed enterprise by operating platform and type of Candle agent. The Navigator business view shows the hierarchy of any managed objects defined through the CMW. You can also define Navigator views for any logical grouping, such as a departmental or site hierarchy.

� You can define a graphic view

The graphic view enables you to retrieve and display real-time monitoring data from Candle agents. Using the graphic view, you can create a background image or import one, then place objects (Navigator items) on the image or have it done automatically using geographical coordinates. You can zoom in and you can add such graphics as floor plans and organization charts.

� You can integrate information provided by Candle’s Universal Agent

Candle’s Universal Agent is an agent you can configure to monitor any data you collect. It lets you integrate data from virtually any platform and any source, such as custom applications, databases, systems, and subsystems. Your defined data providers are listed in the Navigator, and default workspaces are automatically created.

OMEGAMON DE Policy Management adds automation capabilities. The Workflow editor enables you to design sets of automated system processes, called policies, to resolve system problems. A policy performs actions, schedules work to be performed by users, or automates manual tasks.

Detailed information about OMEGAMON DE is provided in the CandleNet Portal online Help.

The Workflow EditorIf your product supports the use of the Workflow Editor, you can find information about its use in CandleNet Portal Help and Administering OMEGAMON Products: CandleNet Portal. The Workflow Editor permits you to create new policies or modify any predefined policies for your product or policies created using the Candle Management Workstation.

Benefits of using OMEGAMON XE for Storage OMEGAMON XE for Storage provides these benefits:



� Increases knowledge—with extensive reporting capabilities that provide real-time access to reliable, up-to-the-minute data. Thus, you can make faster, better informed operating decisions.

� Enhances system performance—by letting you integrate, monitor, and manage your system, environment, console, and mission-critical applications. OMEGAMON XE for Storage alerts you when conditions in your environment meet threshold-based conditions. These alerts notify your system administrator to limit and control system traffic.

� Simplifies application and system management—by managing applications, platforms, and resources across your system.

Prerequisite knowledgeIn order to understand the capabilities of the Candle Command Center, you should review the references cited in “Further Information about the CMW and CandleNet Portal” on page 16. You should also be familiar with the capabilities of IBM’s MVS operating system as described in the OS/390 MVS library.

Planning and installationFor information on planning for and installing this product, refer to the installation documentation appropriate to your environment.

Learning About OMEGAMON XE for Storage 23

Learning AboutOMEGAMON XE for Storage

IntroductionThis chapter introduces you to the facilities of OMEGAMON XE for Storage.

Chapter contentsUnderstanding Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

What are attributes? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Using attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Using attributes in situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25For more information on attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Understanding OMEGAMON XE for Storage Information. . . . . . . . . . . . . . . . . . . 27Workspaces and table views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27What is a workspace? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Formats for information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Associating workspaces with attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28For more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Using OMEGAMON XE for Storage information . . . . . . . . . . . . . . . . . . . . . . 28Defining workspace properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Investigating an event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Filtering information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Sorting Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Adding a workspace to your favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Creating Take Action Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31The Take Action feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Executing a saved Take Action command. . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2


More information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31OMEGAMON XE for Storage Predefined Situations . . . . . . . . . . . . . . . . . . . . . . . 32

What is a situation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32What is a predefined situation?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Using Situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32


Understanding Attributes


What are attributes?

OMEGAMON XE for Storage gathers data from remote agents residing on the managed systems of your network and stores this data in system elements called attributes. You can use these attributes to build situations to monitor the performance of the managed systems you are concerned with.

Attributes correspond to the column names contained on the table views in associated OMEGAMON XE for Storage workspaces. Related attributes are grouped into attribute groups. A given table view contains information provided by a single attribute group.

Using attributesTo use attributes effectively, you must first understand the structure of an attribute.

� An attribute is made up of an attribute group and an attribute item.

� An attribute group associates attributes that refer to some unique characteristic of the data that is being stored.

� An attribute item stores data for a particular property of an attribute group.

For example, in the attribute

ADDRESS_SPACE_CPU_UTILIZATION.CPU_Percent

CPU_percent is an attribute item that stores a value representing the percentage of CPU utilized by the address space over the current interval in the ADDRESS_SPACE_CPU_UTILIZATION attribute group.

Using attributes in situationsYou use attributes to create situations that monitor the state of your OS/390 operating systems. A situation describes a condition you want to test. When you start a situation, CandleNet Portal compares the values you have assigned for the situation’s attributes with the values collected by



OMEGAMON XE for Storage and registers an event if the condition is met. You are alerted to events by indicator icons that appear in the Navigator.

For more information on attributesFor complete descriptions of the attributes for OMEGAMON XE for Storage, refer to the OMEGAMON XE for Storage’s online Help.


Understanding OMEGAMON XE for Storage Information


Workspaces and table viewsWhen using CandleNet Portal, information is displayed in workspaces. Within a given workspace, information is displayed in tabular form. CandleNet Portal refers to this tabular format for information as a table view. Information may also be displayed in the workspace as a chart, graph, or other format you can specify.

What is a workspace?A workspace is the working area of the CandleNet Portal application window. At the left of the workspace is a Navigator that permits you to select the workspace you want to display. As part of the application window, the right side of the status bar shows the CandleNet Portal server name and port number to which the displayed information applies, as well as the ID of the current user.

As you select items in the Navigator, the workspace presents views pertinent to your selection. Each workspace has at least one view.

Every workspace has a set of properties associated with it. You can customize the workspace by working in the Properties editor to change the style and content of each view.

Another way to customize the workspace is to change the type of view or to add views to the workspace.

Be aware that the changes you make to the workspace are lost when you switch to another workspace unless you save them first.

Formats for informationInformation can be presented to you in any of the views below:

� Table view

� Pie chart view

� Bar chart view

� Plot chart view



� Needle gauge view

� Thermometer gauge view

� Notepad view

� Event console view, that shows the status of the situations associated with the system.

� Take Action view, that is used to send a command to the system.

� Terminal view, that enables you to start a 3270 or 5250 work session.

� Browser view, that permits you to open a browser to see HTML pages and Web sites.

Associating workspaces with attributesThere is a direct relationship between attributes and workspaces. An attribute group typically corresponds to a table view within a named workspace and attribute items correspond to columns in the table view.

Each CandleNet Portal workspace displays real-time information for many of the attributes. The information is available to you, independent of whether you are using OMEGAMON XE for Storage to monitor situations.

For more information Continue reading to learn how to manipulate information presented to you by CandleNet Portal. For descriptions of the individual workspaces, see “OMEGAMON XE for Storage Workspaces” on page 51.

Using OMEGAMON XE for Storage informationYou can view information about each managed system that you are monitoring. Use this information to

� monitor the performance of each managed system, helping you to identify bottlenecks and evaluate tuning decisions

� select the most effective threshold values for situations you create

� review status information when a change in the state of a given resource occurs, such as from OK to Warning or Critical



Defining workspace propertiesEvery workspace has a set of properties associated with it. You can customize the workspace by working in the Properties editor to change the style and content of each view. Changes you make to workspace properties, such as adding or editing a view are only temporary. They will be lost when you exit CandleNet Portal unless you save the workspace.

The properties of a workspace may be some or all of the following

Investigating an event When the conditions of a situation have been met, the situation evaluates True, causing an event indicator to appear in the Navigator. You can investigate the event by opening its workspace.

The event workspace shows two table views, one with the values of the attributes when the situation evaluated True, and the other with the attributes’ current values.

The event workspace can also display a text view with any expert advice written by the situation's author, and the Take Action view so you can send a command to the application started on that system.

Filtering informationTo manually set up filtering for a given table view, place the cursor on the table view, press the right mouse button, and select Properties. From the displayed dialog, select the Filters tab. Here you can select the columns to display as well as set up the criteria for which rows to display. To save your filtering specifications, you must save the workspace before exiting.

Query Specify what data should go in the chart or table

Filters Refine the view by filtering out unwanted data from the chart or table

Thresholds Establish threshold values and color indicators for a table view

Configuration Specify the script to run or the connection to make whenever you open the terminal view

Style Change the behavior and appearance of the view



Sorting InformationSorting is handled by simply clicking on a column heading. Click once and the report will be sorted in ascending order. Click a second time to resort the report into descending order. A third click returns you to the report’s default sort.

Adding a workspace to your favoritesWhen using CandleNet Portal in browser mode, you can start it from any workstation by entering the URL for the web server where the browser mode client is installed. Each CandleNet Portal workspace also has a URL so that you can save the workspace to your Favorites list or specify it as your home page.


Creating Take Action Commands

Creating Take Action Commands

The Take Action featureThe Take Action feature lets you issue a command to any system in your network where one or more Candle agents are installed. You can implement Take Action commands from a workspace, from a situation, in an ad hoc mode, or by recalling a saved Take Action command.

Executing a saved Take Action commandHere is an example of using a saved Take Action command:

1. Right-click an item in the Navigator.

2. From the popup menu, select Take Action to display the Take Action dialog.

3. In the Take Action dialog’s Action area, select a saved Take Action command. To edit the command’s argument values, select the Arguments button. When you’re done, click OK.

4. In the Take Action dialog’s Destination System(s) area, select the target system or systems to which you want to send the Take Action command and click OK. This causes the command to be sent to the system or systems where it is executed.

More informationFor detailed information about creating and using Take Action commands, see the CandleNet Portal Administrator’s Guide or the online Help provided with CandleNet Portal.

OMEGAMON XE for Storage Predefined Situations



What is a situation?

A situation is a logical expression involving one or more system conditions. Situations are used to monitor the condition of systems in your network. You can manage situations from CandleNet Portal by using the Situation editor.

What is a predefined situation?

OMEGAMON XE for Storage agents you use to monitor your system environment are shipped with a set of predefined situations that you can use as-is or modify to meet your requirements.

Predefined situations are precoded to check for system conditions common to many enterprises. Using predefined situations can improve the speed with which you can begin using OMEGAMON XE for Storage. You can examine and, if necessary, change the conditions or values being monitored by a predefined situation to those best suited to your enterprise.

Note: Candle suggests that, if you choose to modify a predefined situation, you first make a copy to ensure fallback if necessary.

Using Situations You manage situations from CandleNet Portal using the Situation editor. Using the Situation editor, you can:

� Create a situation

� Save a situation

� Display a situation

� Edit a situation

� Start, stop, or delete a situation

� Investigate the event workspace for a situation

For the most current information about situations and details about using the Situation editor, refer to the CandleNet Portal Administrator’s Guide or the



online Help provided with CandleNet Portal. OMEGAMON XE for Storage predefined situations

A list of the predefined situations provided with OMEGAMON XE for Storage, together with the situations’ descriptions and formulas, can be found in chapter 3 of this book and in the online Help distributed with OMEGAMON XE for Storage.

OMEGAMON XE for Storage Situations 35

OMEGAMON XE for StorageSituations

IntroductionThis chapter presents the OMEGAMON XE for Storage predefined situations.

Chapter contents

OMEGAMON XE for Storage Situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

What is a predefined situation?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Predefined situations descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3

OMEGAMON XE for Storage Situations



You can use the predefined situations shipped with OMEGAMON XE for Storage as-is or modify them to meet your requirements. Candle suggests that if you choose to modify a predefined situation, you first make a copy to ensure a fallback, if necessary. You can also create your own situations using the attributes provided by OMEGAMON XE for Storage.

What is a predefined situation?A situation is a logical expression involving one or more system conditions. OMEGAMON XE for Storage uses situations to monitor the systems in your network. To improve the speed with which you begin using OMEGAMON XE for Storage, Candle had precoded situations that check for system conditions common to many enterprises. You can examine and if necessary, change the conditions or values being monitored to those best suited to your enterprise. Note that all situations are shipped disabled and you must activate them to use them.

Predefined situations descriptionsFollowing, in alphabetical order, is a list of the predefined situations shipped with OMEGAMON XE for Storage.

KS3_Applic_Resp_Time_Critical:

If VALUE S3_Application_Monitoring.High_Dataset_MSR GE 50monitor the response time components to determine the reason for a poor response time when an application is accessing a dataset and the response time is greater than the critical threshold. Also examine the volume for over-utilization, cache settings, and the response time components at the volume level.

KS3_Applic_Resp_Time_Warning:

If VALUE S3_Application_Monitoring.High_Dataset_MSR GE 40 andVALUE S3_Application_Monitoring.High_Dataset_MSR LT 50monitor the response time components to determine the reason for a poor response time when an application is accessing a dataset and the response time is greater than the warning threshold. Also examine the volume for



over-utilization, cache settings, and the response time components at the volume level.

KS3_Cachecu_Cache_Stat_Critical:

If VALUE S3_Cache_Control_Unit.Cache_Status NE Activemonitors for the condition where caching is not active for the control unit. Use the SETCACHE command to activate caching, if appropriate.

KS3_Cachecu_DFW_Retry_Critical:

If VALUE S3_Cache_Control_Unit.DFW_Retry_Percent GE 2monitors for the percent of DASD fast write attempts that could not be satisfied due to a shortage of available non-volatile storage (NVS) space. Check for pinned NVS and correct the problem if NVS is pinned. Otherwise, if the impact on performance is not acceptable, you may need to move a volume or dataset to another cache control unit or add NVS to this control unit.

KS3_Cachecu_DFW_Retry_Warning:

If VALUE S3_Cache_Control_Unit.DFW_Retry_Percent GE 1 andVALUE S3_Cache_Control_Unit.DFW_Retry_Percent LT 2monitors for the percent of DASD fast write attempts that could not be satisfied due to a shortage of available non-volatile storage (NVS) space. Check for pinned NVS and correct the problem if NVS is pinned. Otherwise, if the impact on performance is not acceptable, you may need to move a volume or dataset to another cache control unit or add NVS to this control unit.

KS3_Cachecu_Inact_Vols_Critical:

If VALUE S3_Cache_Control_Unit.Deactivated_Volumes GE 15monitors for the condition where the number of deactivated volumes on the control unit exceeds the critical threshold. You can use the SETCACHE command to activate caching on the volumes, if necessary.

KS3_Cachecu_Inact_Vols_Warning:

If VALUE S3_Cache_Control_Unit.Deactivated_Volumes GE 10 andVALUE S3_Cache_Control_Unit.Deactivated_Volumes LT 15monitors for the condition where the number of deactivated volumes on the



control unit exceeds the warning threshold. You can use the SETCACHE command to activate caching on the volumes, if necessary.

KS3_Cachecu_NVS_Stat_Critical:

If Value_S3_Cache_Control_Unit.NVS_Status NE Activemonitors for the condition where non-volatile storage is not active for the control unit. All writes to volumes on the control unit are written directly to DASD. Use the SETCACHE command to activate NVS, if appropriate.

KS3_Cachecu_NVS_Stat_Critical:

If Value_S3_Cache_Control_Unit.NVS_Status NE Activemonitors for the condition where non-volatile storage is not active for the control unit. All writes to volumes on the control unit are written directly to DASD. Use the SETCACHE command to activate NVS, if appropriate.

KS3-Cachecu_Read_HitP_Critical:

If VALUE S3_Cache_Control_Unit.Read_Hit_Percent LE 50 andVALUE S3_Cache_Control_Unit.Read_Hit_Percent GT 0monitors for a condition where the percent of read I/O requests resolved from cache has fallen below acceptable thresholds. If performance is a problem, look for volume with a low read hit percent and consider moving them to another control unit to balance the load. This may be caused by cache-unfriendly applications or a shortage of cache.

KS3-Cachecu_Read_HitP_Warning:

If VALUE S3_Cache_Control_Unit.Read_Hit_Percent LE 60 andVALUE S3_Cache_Control_Unit.Read_Hit_Percent GT 50monitors for a condition where the percent of read I/O requests resolved from cache has fallen below acceptable thresholds. If performance is a problem, look for volume with a low read hit percent and consider moving them to another control unit to balance the load. This may be caused by cache-unfriendly applications or a shortage of cache.

KS3_Cachecu_Trk_Dstg_Critical:

If VALUE S3_Cache_Control_Unit.Track_Destaging_Rate GE 70monitors for the rate at which tracks are being removed from cache and written to DASD. If performance is being impacted, you may need to migrate



datasets or volumes to another cache control unit. An alternative is to increase the cache capacity.

KS3_Cachecu_Trk_Dstg_Warning:

If VALUE S3_Cache_Control_Unit.Track_Destaging_Rate GE 50 andVALUE S3_Cache_Control_Unit.Track_Destaging_Rate LT 70monitors for the rate at which tracks are being removed from cache and written to DASD. If performance is being impacted, you may need to migrate datasets or volumes to another cache control unit. An alternative is to increase the cache capacity.

KS3_Cachecu_Write_HitP_Critical:

If VALUE S3_Cache_Control_Unit.Wrtie_Hit_Percent LE 45 andVALUE S3_Cache_Control_Unit.Wrtie_Hit_Percent GE 0monitors to determine the percent of DASD/Cache fast write commands that were successfully processed without accessing the volume. If performance is impacted it may be necessary to move a volume or dataset to another control unit to balance the workload.

KS3_Cachecu_Write_HitP_Warning:

If VALUE S3_Cache_Control_Unit.Wrtie_Hit_Percent LE 50 andVALUE S3_Cache_Control_Unit.Wrtie_Hit_Percent GT 45monitors to determine the percent of DASD/Cache fast write commands that were successfully processed without accessing the volume. If performance is impacted it may be necessary to move a volume or dataset to another control unit to balance the workload.

KS3_Channel_Busy_Pct_Critical:

If VALUE S3_Channel_Path.Complex_Percent_Utilized GE 85monitors for high response time for I/O requests to volumes being serviced by the channel due to over utilization of that channel. It may be necessary to balance the workload between channels by moving volumes or datasets.

KS3_Channel_Busy_Pct_Warning:

If VALUE S3_Channel_Path.Complex_Percent_Utilized GE 70 andVALUE S3_Channel_Path.Complex_Percent_Utilized LT 85monitors for high response time for I/O requests to volumes being serviced by



the channel due to over utilization of that channel. It may be necessary to balance the workload between channels by moving volumes or datasets.

KS3_HSM_Backup_Held_Critical:

If VALUE S3_HSM_Function_Summary.Function_Status EQ Held andVALUE S3_HSM_Function_Summary.Function EQ Backupmonitors the HSM backup function to see if it is being held. If the hold is inadvertent, issue the HSM RELEASE BACKUP command to allow the backup function to continue processing.

KS3_HSM_Backup_Queue_Critical:

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 50 andVALUE S3_HSM_Function_Summary.Function EQ Backupmonitors the HSM backup queue for a condition where the number of backup requests waiting exceeds the critical threshold. If the number of backup tasks is not at the maximum, use the HSM SETSYS MAXBACKUPTASKS command to increase the number of backup tasks, thus increasing the processing rate. Keep in mind that the number of available backup volumes serves as a constraint on the number of active backup tasks.

KS3_HSM_Backup_Queue_Warning:

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 15 andVALUE S3_HSM_Function_Summary.Waiting_Requests LT 50 andVALUE S3_HSM_Function_Summary.Function EQ Backupmonitors the HSM backup queue for a condition where the number of backup requests waiting exceeds the warning threshold. If the number of backup tasks is not at the maximum, use the HSM SETSYS MAXBACKUPTASKS command to increase the number of backup tasks, thus increasing the processing rate. Keep in mind that the number of available backup volumes serves as a constraint on the number of active backup tasks.

KS3_HSM_Dump_Held_Critical:

If VALUE S3_HSM_Function_Summary.Function_Status EQ Held andVALUE S3_HSM_Function_Summary.Function EQ Dumpmonitors the HSM dump function to see if it is being held. If the hold is inadvertent, issue the HSM RELEASE DUMP command to allow dump processing to continue.



KS3_HSM_Dump_Queue_Critical:

If VALUE S3_HSM_Function_Summary.Function_Status EQ Held andVALUE S3_HSM_Function_Summary.Function EQ Dumpmonitors the HSM dump queue for a condition where the number of dump requests waiting exceeds the critical threshold. If the number of dump tasks is not at the maximum, use the HSM SETSYS MAXDUMPTASKS command to increase the number of dump tasks, thus increasing the processing rate. Keep in mind that the number of available tape drives serves as a constraint on the number of active dump tasks.

KS3_HSM_Dump_Queue_Warning:

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 15 andVALUE S3_HSM_Function_Summary.Function EQ Dump andVALUE S3_HSM_Function_Summary.Waiting_Requests LT 50monitors the HSM dump queue for a condition where the number of dump requests waiting exceeds the warning threshold. If the number of dump tasks is not at the maximum, use the HSM SETSYS MAXDUMPTASKS command to increase the number of dump tasks, thus increasing the processing rate. Keep in mind that the number of available tape drives serves as a constraint on the number of active dump tasks.

KS3_HSM_Migrate_Held_Critical:

If VALUE S3_HSM_Function_Summary.Function_Status EQ Held andVALUE S3_HSM_Function_Summary.Function EQ Migrationmonitors the migrate function to see if it is being held. If the hold on the function is inadvertent, issue the HSM RELEASE MIGRATION command to allow migration to continue.

KS3_HSM_Migrate_Queue_Critical:

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 50 andVALUE S3_HSM_Function_Summary.Function EQ Migrationmonitors the HSM migration queue for a condition where the number of migration requests waiting exceeds the critical threshold. If the number of migrate tasks is not at the maximum, use the HSM SETSYS MAXMIGRATIONTASKS command to increase the number of migration tasks, thus increasing the processing rate. Note that this will affect only those



migrations requested by automatic functions. Only one task is available to process command migration requests.

KS3_HSM_Migrate_Queue_Warning:

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 15 andVALUE S3_HSM_Function_Summary.Waiting_Requests LT 50 andVALUE S3_HSM_Function_Summary.Function EQ Migrationmonitors the HSM migration queue for a condition where the number of migration requests waiting exceeds the warning threshold. If the number of migrate tasks is not at the maximum, use the HSM SETSYS MAXMIGRATIONTASKS command to increase the number of migration tasks, thus increasing the processing rate. Note that this will affect only those migrations requested by automatic functions. Only one task is available to process command migration requests.

KS3_HSM_Recall_Held_Critical:

If VALUE S3_HSM_Function_Summary.Function_Status EQ Held andVALUE S3_HSM_Function_Summary.Function EQ Recallmonitors the recall function to see if it is being held. If the hold on the function is inadvertent, issue the HSM RELEASE RECALL command to allow recalls to resume.

KS3_HSM_Recall_Queue_Critical:

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 50 andVALUE S3_HSM_Function_Summary.Function EQ Recallmonitors the HSM recall queue for a condition where the number of recall requests waiting exceeds the critical threshold. If the number of recall tasks is not at the maximum, use the HSM SETSYS MAXRECALLTASKS command to increase the number of recall tasks, thus increasing the processing rate.

KS3_HSM_Recall_Queue_Warning:

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 15 andVALUE S3_HSM_Function_Summary.Waiting_Requests LT 50 andVALUE S3_HSM_Function_Summary.Function EQ Recallmonitors the HSM recall queue for a condition where the number of recall requests waiting exceeds the critical threshold. If the number of recall tasks is not at the maximum, use the HSM SETSYS MAXRECALLTASKS command to increase the number of recall tasks, thus increasing the processing rate.



KS3_HSM_Recovery_Held_Critical:

If VALUE S3_HSM_Function_Summary.Function_Status EQ Held andVALUE S3_HSM_Function_Summary.Function EQ Recoverymonitors the recovery function to see if it is being held. If the hold on the function is inadvertent, issue the HSM RELEASE RECOVER command to allow recovery function to resume.

KS3_HSM_Recovery_Queue_Critical:

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 50 andVALUE S3_HSM_Function_Summary.Function EQ Recoverymonitors the HSM recovery queue for a condition where the number of recover requests waiting exceeds the critical threshold. If the number of recovery tasks is not at the maximum, use the HSM SETSYS MAXDSRECOVERTASKS command to increase the number of recover tasks, thus increasing the processing rate. Keep in mind that the number of backup tape cartridges serves as a constraint on the number of active recovery tasks.

KS3_HSM_Recovery_Queue_Warning:

If VALUE S3_HSM_Function_Summary.Waiting_Requests GE 15 andVALUE S3_HSM_Function_Summary.Waiting_Requests LT 50 andVALUE S3_HSM_Function_Summary.Function EQ Recovery monitors the HSM recovery queue for a condition where the number of recover tasks waiting exceeds the warning threshold. If the number of recovery tasks is not at the maximum, use the HSM SETSYS MAXDSRECOVERTASKS command to increase the number of recover tasks, thus increasing the processing rate. Keep in mind that the number of backup tape cartridges serves as a constraint on the number of active recovery tasks.

KS3_HSM_Status_Inactive_Critical:

If VALUE S3_HSM_Status.HSM_Status EQ InActivemonitors for the status of the HSM. If status is not active, restart HSM.

KS3_LCU_Av_Delay_Q_Critical:

If VALUE S3_Logical_Control_Unit.Average_Delay_Queue GE 0.500monitors for the condition where the average number of requests queued to devices assigned to a logical control unit due to busy conditions on physical paths has exceeded the critical threshold. If performance is impacted, you



may be able to balance the workload across multiple LCUs by moving a volume or dataset. Otherwise, you may need to add physical paths to the LCU.

KS3_LCU_Av_Delay_Q_Warning:

If VALUE S3_Logical_Control_Unit.Average_Delay_Queue GE 0.2 and VALUE S3_Logical_Control_Unit.Average_Delay_Queue LT 0.500monitors for the condition where the average number of requests queued to devices assigned to a logical control unit due to busy conditions on physical paths has exceeded the warning threshold. If performance is impacted, you may be able to balance the workload across multiple LCUs by moving a volume or dataset. Otherwise, you may need to add physical paths to the LCU.

KS3_LCU_Cont_Rate_Critical:

If VALUE S3_Logical_Control_Unit.Contention_Rate GE 1.001monitors for the condition where the rate at which I/O requests are being queued to devices on a logical control unit (LCU) due to busy conditions on physical paths has exceeded the critical threshold. If performance is impacted, you may need to migrate volumes or datasets to another LCU, otherwise, you may need to add physical paths to the LCU.

KS3_LCU_Cont_Rate_Warning:

If VALUE S3_Logical_Control_Unit.Contention_Rate GE 0.2 andVALUE S3_Logical_Control_Unit.Contention_Rate LT 1.001monitors for the condition where the rate at which I/O requests are being queued to devices on a logical control unit (LCU) due to busy conditions on physical paths has exceeded the warning threshold. If performance is impacted, you may need to migrate volumes or datasets to another LCU, otherwise, you may need to add physical paths to the LCU.

KS3_LCU_IO_Rate_Sec_Critical:

If VALUE S3_Logical_Control_Unit.Channel_Path_I/O_Rate GE 600monitors for the condition where the I/O rate per second to volumes in the logical control unit (LCU) has exceeded the critical threshold. If performance is impacted, you may need to balance the workload across multiple LCUs by moving volumes or datasets.



KS3_LCU_IO_Rate_Sec_Warning:

If VALUE S3_Logical_Control_Unit.Channel_Path_I/O_Rate GE 200 andVALUE S3_Logical_Control_Unit.Channel_Path_I/O_Rate LT 600monitors for the condition where the I/O rate per second to volumes in the logical control unit (LCU) has exceeded the warning threshold. If performance is impacted, you may need to balance the workload across multiple LCUs by moving volumes or datasets.

KS3_VTS_Disconnect_Time_Critical:

If VALUE S3_VTS_Overview.Virtual_Disconnect_Time GE 500monitors for the condition where the logical control unit disconnect time for the virtual tape server exceeds the critical threshold. This is often an indication that the tape volume cache capacity is being exceeded.

KS3_VTS_Host_GB_Warning:

If VALUE S3_VTS_Overview.Host_Channel_Activity_GB GE 18monitors for the condition where the activity between the MVS system and the virtual tape server on the host channels exceeds 19 GB over the hour interval. This could be an indication that the virtual tape server is being overloaded.

KS3_VTS_Recall_Pct_Warning:

If VALUE S3_VTS_Overview.Volume_Recall_Percent GE 20monitors for the condition where the percent of virtual tape mounts that required a physical tape mount to be satisfied exceeded the warning threshold. This may lead to unacceptably large virtual mount times. If so, then investigate the reason for the recalls. If rescheduling or removing the application workload is not possible, you may need to increase the cache capacity of the VTS.

KS3_VTS_Virt_MtPend_Av_Warning:

If VALUE S3_VTS_Overview.Average_Virtual_Mount_Pend_Time GE 300monitors for the condition where the average seconds required to satisfy a virtual mount in the virtual tape subsystem exceeded the warning threshold. If this persists, then further study is required to determine the cause for the



elongated mount times. It may be due to VTS-hostile applications or to a shortage of VTS resources.

KS3_VTS_Virt_MtPend_Mx_Warning:

VALUE S3_VTS_Overview.Maximum_Virtual_Mount_Pend_Time EQ 900monitors for the condition where the maximum seconds required to satisfy a virtual mount in the virtual tape subsystem exceeded the warning threshold. If this persists, then further study is required to determine the cause for the elongated mount times. It may be due to VTS-hostile applications or to a shortage of VTS resources.

KS3_Vol_Cache_DFW_Retry_Critical:

If VALUE S3_Cache_Devices.DFW_Retry_Percent GE 2 and VALUE S3_Cache_Devices.I/O_Count GE 25monitors for the condition where the percentage of DASD fast write attempts for a volume that could not be satisfied due to a shortage of available non-volatile storage (NVS) space exceeded the critical threshold. Check for pinned NVS and correct the problem if NVS is pinned. Otherwise, if the impact on performance is not acceptable, move a volume or dataset to another cache control unit or to add NVS to this control unit.

KS3_Vol_Cache_DFW_Retry_Warning:

If VALUE S3_Cache_Devices.DFW_Retry_Percent GE 1 andVALUE S3_Cache_Devices.DFW_Retry_Percent LT 2 andVALUE S3_Cache_Devices.I/O_Count GE 25monitors for the condition where the percentage of DASD fast write attempts for a volume that could not be satisfied due to a shortage of available non-volatile storage (NVS) space exceeded the warning threshold. Check for pinned NVS and correct the problem if NVS is pinned. Otherwise, if the impact on performance is not acceptable, move a volume or dataset to another cache control unit or to add NVS to this control unit.

KS3_Vol_Cache_Read_HitP_Critical:

If VALUE S3_Cache_Devices.Read_Hit_Percent LE 45 andVALUE S3_Cache_Devices.Read_Hit_Percent GE 0 andVALUE S3_Cache_Devices.I/O_Count GE 25monitors for the condition where the cache read hit percent is below the



critical threshold. If performance is impacted determine the reason for the low read hit percent. Common problems are cache-unfriendly applications and over-utilization of the control unit.

KS3_Vol_Cache_Read_HitP_Warning:

If *VALUE S3_Cache_Devices.Read_Hit_Percent LE 55 andVALUE S3_Cache_Devices.Read_Hit_Percent GT 45 andVALUE S3_Cache_Devices.I/O_Count GE 25monitors for the condition where the cache read hit percent is below the warning threshold. If performance is impacted determine the reason for the low read hit percent. Common problems are cache-unfriendly applications and over-utilization of the control unit.

KS3_Vol_Cache_Writ_HitP_Critical:

If VALUE S3_Cache_Devices.Write_Hit_Percent LE 20 andVALUE S3_Cache_Devices.Write_Hit_Percent GE 0 andVALUE S3_Cache_Devices.I/O_Count GE 25monitors for the condition where the cache write hit percent for a volume is below the critical threshold. Check the status of the non-volatile storage in the cache control unit. You can move volumes or datasets to balance the workload.

KS3_Vol_Cache_Writ_HitP_Warning:

If VALUE S3_Cache_Devices.Write_Hit_Percent LE 30 andVALUE S3_Cache_Devices.Write_Hit_Percent GT 20 andVALUE S3_Cache_Devices.I/O_Count GE 25monitors for the condition where the cache write hit percent for a volume is below the warning threshold. Check the status of the non-volatile storage in the cache control unit. You can move volumes or datasets to balance the workload.

KS3_Vol_Disabled_VTOC_Critical:

If VALUE S3_DASD_Volume_Space.VTOC_Index_Status EQ Disabledmonitors for the condition where a VTOC index has been disabled. This can degrade performance on the volume. Enable the VTOC index.

KS3_Vol_Fragment_Index_Critical:



If VALUE S3_DASD_Volume_Space.Fragmentation_Index GE 850monitors for the condition where a volume has a fragmentation index that exceeds the critical threshold. The volume should be defragged so that free extents are combined to help prevent dataset allocation failures.

KS3_Vol_Fragment_Index_Warning:

If VALUE S3_DASD_Volume_Space.Fragmentation_Index GE 650 andVALUE S3_DASD_Volume_Space.Fragmentation_Index LT 850monitors for the condition where a volume has a fragmentation index that exceeds the warning threshold. The volume should be defragged so that free extents are combined to help prevent dataset allocation failures.

KS3_Vol_Free_Space_Pct_Critical:

If VALUE S3_DASD_Volume_Space.Percent_Free_Space LE 5 andVALUE S3_DASD_Volume_Space.Percent_Free_Space GE 0monitors for the condition where the percentage of free space on a volume is below the critical threshold. If datasets on the volume will require more space on this volume, then either migrate some datasets to another volume or release space form datasets that may be over-allocated.

KS3_Vol_Free_Space_Pct_Warning:

If VALUE S3_DASD_Volume_Space.Percent_Free_Space LE 10 andVALUE S3_DASD_Volume_Space.Percent_Free_Space GT 5monitors for the condition where the percentage of free space on a volume is below the critical threshold. If datasets on the volume will require more space on this volume, then either migrate some datasets to another volume or release space form datasets that may be over-allocated.

KS3_Vol_Perf_Resp_Time_Critical:

If VALUE S3_DASD_Volume_Performance.Response_Time GE 55 andVALUE S3_DASD_Volume_Performance.I/O_Count GE 25monitors for the condition where response time for the volume exceeds the critical threshold. Look at the volume to see if high utilization is a problem. If so, it may be necessary to migrate datasets from the volume to reduce utilization. Also check the cache status of the volume. Look at the components of I/O to determine where the time is being spent and address the problem accordingly.



KS3_Vol_Perf_Resp_Time_Warning:

If VALUE S3_DASD_Volume_Performance.Response_Time GE 35 andVALUE S3_DASD_Volume_Performance.Response_Time LT 55 andVALUE S3_DASD_Volume_Performance.I/O_Count GE 25monitors for the condition where response time for the volume exceeds the warning threshold. Look at the volume to see if high utilization is a problem. If so, it may be necessary to migrate datasets from the volume to reduce utilization. Also check the cache status of the volume. Look at the components of I/O to determine where the time is being spent and address the problem accordingly.

OMEGAMON XE for Storage Workspaces 51

OMEGAMON XE for StorageWorkspaces

IntroductionThis chapter introduces discusses the OMEGAMON XE for Storage workspaces.

Chapter contentsOMEGAMON XE for Storage Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Application Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Application table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Applications with DSN MSR > 40 bar graph . . . . . . . . . . . . . . . . . . . . . . . . . 55Applications with volume MSR > 25 bar graph . . . . . . . . . . . . . . . . . . . . . . . 55Defining applications to monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Cache CU Performance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Cache performance table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Read hit percent bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57WRITE hit percent bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57DFW hit % bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58DFW retry % bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Track destaging rate bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Cache CU Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Cache status table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Available cache bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59NVS pinned bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4


Deactivated volumes bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Channel Path Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Channel path table view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Complex % utilization bar graph. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61LPAR % utilization DASD bar graph. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62LPAR MB/Sec WRITE - DASD bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62LPAR MB/Sec READ - DASD bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

HSM Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63HSM function status table view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63HSM control dataset table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63HSM status table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Waiting requests bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Logical Control Unit Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Logical control unit table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Average delay queue bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Average contention rate bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

SMS Configuration Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67SMS base configuration table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Storage groups table view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Data classes table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Management classes table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Storage classes table view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

SMS Storage Groups Performance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68SMS storage groups performance table view . . . . . . . . . . . . . . . . . . . . . . . . . 68High volume response time > 25 bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . 68Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

SMS Storage Groups Space Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70SMS storage groups space table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Storage groups with free space % < 10 bar graph . . . . . . . . . . . . . . . . . . . . . 70Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Tape Group Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Tape group table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71


Mount pend time > 5 minutes bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

User DASD Groups Performance Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73User DASD groups performance table view . . . . . . . . . . . . . . . . . . . . . . . . . . 73High volume response time > 25 bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . 73Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

User DASD Groups Space Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74User DASD groups space table view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74User DASD groups with free space % < 10 bar graph . . . . . . . . . . . . . . . . . . 74Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Virtual Tape Subsystems Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Virtual tape subsystems table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Volume recall % > 20 bar graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Average virtual mount pending time > 300 bar graph . . . . . . . . . . . . . . . . . . 75Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

OMEGAMON XE for Storage Workspaces


OMEGAMON XE for Storage Workspaces

OMEGAMON XE for Storage includes a reporting capability that provides information displayed in the following named workspaces:

� Application Summary Report

� Cache CU Performance Report

� Cache CU Status Report

� Channel Path Report

� HSM Status Report

� Logical Control Unit Report

� SMS Configuration Report

� SMS Storage Groups Performance Report

� SMS Storage Groups Space Report

� Tape Group Report

� User DASD Groups Performance Report

� User DASD Groups Space Report

� Virtual Tape Systems Report


Application Summary Report


The sections below describe various components of this workspace. For a description of the attributes used as column headings in the workspace’s table view, review the attribute group definitions for this workspace in the OMEGAMON XE for Storage online Help.

Application table viewThe tabular portion of this workspace displays one row of data for each active address space for which monitoring has been requested. The display contains:

� the name of the job or started task

� the decimal ASID number

� the I/O rate for the job

� the number of datasets allocated for the job

� the worst response time suffered by any of those datasets

� the name of the dataset suffering the worst response time and the volume on which it resides

� the number of volumes in use by the job and the worst response time on any of those volumes along with the name of the volume incurring that response time.

Applications with DSN MSR > 40 bar graphThis graph contains a bar for each monitored application that had a dataset whose average millisecond response time since the beginning of the RMF interval exceeded 40 milliseconds. The height of the bar indicates the worst dataset response time for the application.

Applications with volume MSR > 25 bar graphThis graph contains a bar for each monitored application that had a volume whose average millisecond response time in the prior RMF interval exceeded 25 milliseconds. The height of the bar indicates the worst volume response time for the application.



Defining applications to monitorThe monitored applications list is controlled by the user setting a situation. The situation can be named anything, however, it must be written against the APPL table, object name S3_Application Monitoring. The attributes that must be set in the situation to control monitoring of the application are as follows:

To collect dataset performance statistics for all datasets accessed by an application set the 'I/O Monitor Status' attribute to 'Start' when defining the situation that starts monitoring for the application. Datasets performance statistics are gathered for all datasets accessed by the application regardless of the volume on which the datasets reside and the dataset performance options in effect for that volume. To discontinue the collection of dataset performance statistics for the application, change the value of the 'I/O Monitor Status' attribute to 'Stop'. Depending on the dataset collection status of the volumes being accessed by the application, some dataset performance statistics may still be collected.

LinksRight-clicking on the link to the left of each row of tabular data produces a popup menu with links to the following workspaces that are not discussed further in this document:

� Application Dataset Performance Report

� Application Volume Performance Report

� Application Volume Cache Report

� Application Dataset Space Utilization

� Application Volume Space Utilization

Object Value

Application Name of the application for which monitoring is to be started or stopped.

Status Start - start monitoringStop - stop monitoring


Cache CU Performance Report


The sections below describe various components of this workspace. For a description of the attributes used as column headings in the workspace's table view, review the attribute group definitions for this workspace in the OMEGAMON XE for Storage online Help.

Cache performance table viewThe tabular portion of this workspace displays one row of data for each cache control unit configured to the reporting LPAR. The display contains:

� the subsystem ID of the control unit

� the control unit model

� the read and write hit percentages for the control unit

� the read I/O percent

� the bypass and inhibit percents

� the DASD Fast Write hit and retry percents

� the Cache Fast Write read and write percents

� the track destaging rate

� the control unit type.

Read hit percent bar graphThis graph contains a bar for each cache control unit that had a read hit percent greater than zero. The height of the bar indicates the read hit percentage.

WRITE hit percent bar graphThis graph contains a bar for each cache control unit that had a write hit percent greater than zero. The height of the bar indicates the write hit percentage.



DFW hit % bar graphThis graph contains a bar for each cache control unit whose DASD Fast Write hit percent was greater than zero. The height of the bar indicates the DASD Fast Write hit percentage.

DFW retry % bar graphThis graph contains a bar for each cache control unit whose DASD Fast Write retry percent was greater than zero. The height of the bar indicates the DASD Fast Write retry percentage.

Track destaging rate bar graphThis graph contains a bar for each cache control unit whose track destaging rate was greater than zero. The height of the bar indicates the track destaging rate.

LinksRight-clicking on the link to the left of each row of tabular data produces a popup menu with links to the following workspaces that are not discussed further in this document.

� Cache CU Volume Cache

� Cache CU Volume Performance

� Symmetrix Configuration

Note: Obtaining EMC Symmetric data can only be done in conjunction with the applicable EMC hardware and software. The hardware required is an EMC Symmetrix at the appropriate microcode level. Also required are the EMC Symmetrix Control Facility runtime libraries available from EMC.

� Cache CU Performance Trend

� Cache CU Raid Rank


Cache CU Status Report



Cache status table viewThe tabular portion of this workspace displays one row of data for each cache control unit configured to the reporting LPAR. The display contains:

� the subsystem ID of the control unit

� the control unit model

� the number of active volumes

� the number of deactivated volumes

� the cache status

� the amount of cache configured in the control unit and the amount currently available

� the Non-Volatile Storage status, the amount of NVS configured and the amount pinned

� the control unit type.

Available cache bar graphThis graph contains a bar for each cache control unit. The height of the bar indicates the amount of cache (in megabytes) configured in the unit.

NVS pinned bar graphThis graph contains a bar for each cache control unit. The height of the bar indicates the amount of NVS (in kilobytes) pinned in the unit.

Deactivated volumes bar graphThis graph contains a bar for each cache control unit. The height of the bar indicates the number of deactivated volumes on that control unit.




� Cache CU Volume Cache Performance

� Cache CU Volume Performance

� Symmetrix Configuration

Note: Obtaining EMC Symmetric data can only be done in conjunction with the applicable EMC hardware and software. The hardware required is an EMC Symmetrix at the appropriate microcode level. Also required are the EMC Symmetrix Control Facility runtime libraries available from EMC.

� Cache CU Status Trend

� Cache CU Raid Rank


Channel Path Report

Channel Path Report


Channel path table viewThe tabular portion of this workspace displays one row of data for each channel path. The display contains:

� the channel path ID

� its status

� whether or not it is a shared path

� utilization percentage across the complex

� utilization percentage within this LPAR

� the type of connection it is

� whether or not it is DCM managed

� the BUS utilization percentage

� various read and write metrics for both the complex and the reporting LPAR

� the number of SMS volumes, NON-SMS volumes and the total number of volumes configured in the LPAR

� the channel path management facility group number for the path.

Complex % utilization bar graphThis graph contains a bar for each channel path that had any utilization since the start of the RMF interval. The height of the bar indicates the percent to which the path was utilized in the complex.

Channel Path Report


LPAR % utilization DASD bar graphThis graph contains a bar for each channel path for which there are any volumes configured in the reporting LPAR and for which there was any utilization within the reporting LPAR since the beginning of the RMF interval.

LPAR MB/Sec WRITE - DASD bar graphThis graph contains a bar for each channel path for which there are any volumes configured in the reporting LPAR and for which there were any DASD writes performed in the reporting LPAR since the beginning of the RMF interval.

LPAR MB/Sec READ - DASD bar graphThis graph contains a bar for each channel path for which there are any volumes configured in the reporting LPAR and for which there were any DASD reads performed in the reporting LPAR since the beginning of the RMF interval.

LinksRight-clicking on the link to the left of each row of tabular data produces a popup menu with links to the following workspaces which are not discussed further in this document. The link offered depends on the type of channel path from which you are linking.

� Channel Path Trend

� Channel Volume Performance (restricted to channels with DASD devices attached)

� Channel Volume Cache (restricted to channels with DASD devices attached)


HSM Status Report

HSM Status Report


HSM function status table viewThe tabular report in the top center portion of this workspace contains one row for each HSM function. Each row displays the status of that function for the reporting LPAR, the number of dataset requests and volume requests for that function and how many are active and how many waiting.

HSM control dataset table viewThe tabular report covering the entire width of the workspace in the vertical center contains one for each of the HSM control datasets. Each row displays:

� the DD name of the dataset

� the number of extents for the data and index components

� the percent of Available Space for the data and index components of the dataset

� the percent of Free Space for the data and index components of the dataset

� the total size of the data and the index components of the dataset.

HSM status table viewThe tabular report covering the entire width of the workspace at the bottom of the screen contains a single row of data describing HSM status in the reporting LPAR. This row indicates:

� whether HSM is active

� the address space ID

� the version of DFHSM

� the interval start time

HSM Status Report


� the number of HSM requests during this collection interval

� the CPU usage during this interval

� the number of requests that abended during this interval

� the number of volume migrations, backups and the number of migration and backup volumes recycled during this interval.

Waiting requests bar graphThis graph contains one bar for each HSM function which has at least one waiting request. The height of the bar indicates the total number of waiting requests for this function.

LinksRight-clicking on the link to the left of each row of tabular data produces a popup menu with a link to the HSM Function Details workspace that is not discussed further in this document.


Logical Control Unit Report



Logical control unit table viewThe tabular portion of this workspace displays one row of data for each logical control unit configured in the reporting LPAR. The display contains:

� the logical control unit number

� the average delay queue

� the contention rate

� the director port busy percent

� the control unit busy percent

� the channel path I/O rate

� the number of attached channels and whether there are DCM channels attached to the control unit

� the high volume utilization rate

� the high volume millisecond response time

� the low read hit percent

� the low write hit percentage

� the high DFW retry percentage

� the number of SMS and non-SMS volumes

� the total number of volumes.

Average delay queue bar graphThis graph contains one bar for each logical control unit. The height of the bar indicates the average number of delayed requests on the control unit header.



Average contention rate bar graphThis graph contains one bar for each logical control unit. The height of the bar indicates the contention rate for the unit.


� LCU Volume Performance

� LCU Channel Detail

� LCU Volume Cache

� LCU DCM Channel Summary

� Logical Control Unit Trend


SMS Configuration Report

SMS Configuration Report

SMS base configuration table viewThe tabular report at the top of this workspace contains a single row of data describing SMS status in the reporting LPAR. Listed are:

� the SMS status and level

� the MVS level

� the TSO ID of the last user to update the SMS configuration

� the date and time of the last update

� the default management class

� the default number of tracks per cylinder, track size and unit type.

Storage groups table viewThis tabular report contains one for each storage group defined in the reporting LPAR. Each row lists:

� the storage group name and type

� the TSO ID of the last user to update the group

� the date and time of that update

� a description of the group.

Data classes table viewThis tabular report links to Data Class Details.

Management classes table viewThis tabular report links to Management Class Details.

Storage classes table viewThis tabular report links to Storage Class Details.

SMS Storage Groups Performance Report




SMS storage groups performance table viewThe tabular portion of this workspace contains one row of data for each SMS storage group defined in the reporting LPAR. The display contains:

� the name of the group

� the type

� the SMS status

� the number of volumes in the group

� the current highest response time for any volume in the group

� the current high busy percent for any volume in the group

� the device multi-processing level

� the low read and write hit percents among all volumes in the group

� the highest DFW retry percentage in the group.

High volume response time > 25 bar graphThis graph contains one bar for each SMS storage group whose highest volume response time exceeds 25 milliseconds. The height of the bar indicates the actual response time for that volume.


� SMS Storage Group Volume Performance

� SMS Storage Group Volume Cache



� Cross System Group Summary

� Storage Group Performance Trend

SMS Storage Groups Space Report


SMS Storage Groups Space Report


SMS storage groups space table viewThe tabular portion of this workspace contains one row of data for each SMS storage group. The display contains:

� the group name

� SMS status

� type and whether or not it is enabled

� the number of volumes in the group

� the status of the VTOC index

� the lowest freespace percent of all volumes in the group

� the highest fragmentation index of all volumes

� the largest free extent

� the total free space and the percent of free space for the group

� the total amount of space for the entire storage group.

Storage groups with free space % < 10 bar graphThis graph contains one bar for each storage group whose combined free space percentage has fallen below 10%.


� SMS Storage Group Volume Space

� SMS Storage Group Space Trend


Tape Group Report

Tape Group Report


Tape group table viewThe tabular portion of this workspace displays one row of data for each tape group (device or tape library) configured in the reporting LPAR. The display contains:

� the library name or device type

� the library ID number

� the library type (or Non_Library for non-library devices)

� the library device type

� the console name

� the library description

� the number of configured drives, online drives and available drives

� the number of pending mounts and the length of time the current mount has been pending

� the total number of slots in the device and the number currently available

� the number of scratch volumes for 3480 type magnetic tape cartridges (Media1), for 3490E type enhanced capacity magnetic tape cartridges (Media2), for 3590 type enhanced capacity magnetic tape cartridges (Media3), and for 3590 type extended tape cartridges (Media 4)

� the I/O rate

� the number temporary and permanent errors encountered on the device.

Mount pend time > 5 minutes bar graphThis graph contains one bar for each tape group which has been waiting more than five minutes for a tape mount. The bar height indicates how long the mount has been pending.

Tape Group Report


LinksRight-clicking on the link to the left of each row of tabular data produces a popup menu with links to the following workspaces which are not discussed further in this document.

� Tape Devices


User DASD Groups Performance Report

User DASD Groups Performance Report


User DASD groups performance table viewThe tabular portion of this workspace contains one row of data for each defined user DASD group. The display contains the name of the group, the number of SMS and non-SMS volumes and the total number of volumes in the group, the current highest response time for any volume in the group, the current high busy percent for any volume in the group, the device multi-processing level, the low read and write hit percentages among all volumes in the group and the highest DFW retry percentage in the group.

High volume response time > 25 bar graphThis graph contains one bar for each user DASD group whose highest volume response time exceeds 25 milliseconds. The height of the bar indicates the actual response time for that volume.


� User DASD Group Volume Performance

� User DASD Group Volume Cache

� Cross System Group Summary

� User DASD Group Performance Trend

User DASD Groups Space Report


User DASD Groups Space Report


User DASD groups space table viewThe tabular portion of this workspace contains one row of data for each user DASD group. The display contains:

� the group name

� the number of SMS and non-SMS volumes and the total number of volumes in the group

� the status of the VTOC index

� the lowest freespace percent of all volumes in the group

� the highest fragmentation index of all volumes

� the largest free extent

� the total free space

� the percentage of free space for the group and the total amount of space for the entire storage group.

User DASD groups with free space % < 10 bar graphThis graph contains one bar for each user DASD group whose combined free space percentage has fallen below 10%.


� User DASD Group Volume Space

� User DASD Group Space Trend


Virtual Tape Subsystems Report



Virtual tape subsystems table viewThe tabular portion of this workspace contains one row of data for virtual tape subsystem. The display contains:

� the VTS name and library type

� the number of physical drives available

� the number of virtual devices online

� the average and maximum virtual mount pending times

� the virtual disconnect time

� the volume data (in gigaBytes) read and written through the host channels to virtual volumes associated with this VTS

� the recall percent

� number of scratch volumes, library type, model and serial number for this VTS.

Volume recall % > 20 bar graphThis graph contains one bar for each VTS for which the percentage of virtual mounts to actual physical mounts exceeds 20%. The bar height indicates the recall percentage.

Average virtual mount pending time > 300 bar graphThis graph contains one bar for each VTS for which the average time spent waiting for a virtual mount exceeded 300 seconds. The height of the bar indicates the actual time spent waiting.




� VTS Physical Devices

� VTS Virtual Devices

� VTS Capacity

� VTS Tape Volume Cache

� VTS Composit Details

� VTS Virtual Drive Summary

Glossary 77

Glossary

AActuator. Mechanism of a direct-access storage device (DASD) that moves the arm, which in turn carries the read and write recording heads and associated electronics. By definition, the actuator includes the arm itself and the assembly of arm(s) and disk(s) that corresponds to a single device address or device number in a DASD subsystem.Address Space Identifier (ASID). Unique number assigned to an address space when it is created. The ASID is used by the operating system as an index to find the main control block of the address space (ASCB).Another use of the ASID is to differentiate between address spaces. This is particularly helpful when there are multiple started tasks with the same name or when a job has been started and stopped throughout the day.Aggregate Group. Datasets under SMS control that are grouped together so that SMS can measure performance and migrate all members of the group at once.

Alert. OMEGAMON XE notification of a non-resource related problem that affects performance. For example, an alert may be issued in response to an HSM function being degraded.Allocation/Migration Thresholds. Upper and lower space limits for space on a DASD volume. Allocation uses the upper threshold to determine if enough free space exists on the volume to allocate a dataset. Migration uses the lower threshold to determine when a dataset should be migrated off the volume because the minimum space threshold has been reached.

Application. Active batch job, started task, or TSO user that has been defined for monitoring by OMEGAMON XE. OMEGAMON XE monitors the volumes and datasets used by an application as a logical entity.

Application Collection Interval. Time interval in which the list of volumes and datasets in use by monitored applications is collected by OMEGAMON XE.

G


Archive. To copy data to another physical medium for safekeeping and possible future use, usually from DASD to tape.

ATLDS. See Automated Tape Library Data Server(ATLDS).

Auto Backup. Specifies whether volumes in an SMS storage group or datasets within a management class are eligible for automatic backup.

Auto Dump. Specifies whether volumes in an SMS storage group are eligible for automatic dumping.

Automatic Class Selection (ACS). Routines Installation-specific storage routines written by the storage administrator that control the assignment of storage class, management class, data class, or storage group for SMS managed datasets.

Automated Tape Library Dataserver(ATLDS). A hardware device that automatically controls the retrieval, storage, and disposition of tape cartridges.

Automigration. Indicates if volumes in an SMS storage group or datasets in a management class are eligible for migration.

Availability Attribute. Storage class attribute used to indicate if datasets require continuous availability in the event of a device failure. Dual copy is required to support availability in the event of a device failure.

Average Delay Queue. Average number of requests queued, due to busy conditions on physical paths, to devices assigned to a specific logical control unit.

AVGREC. Data Control Block (DCB) or JCL parameter used as a scaling factor, indicating if a block length allocation is to be multiplied by 1, 1K, or 1M. See also Scaling Factor.

B

Backup Control Dataset (BCDS). Dataset used by HSM to store information about backed up datasets, volumes under HSM control that contain backups, and other volumes under backup control.

Backup Frequency. Indicates for all datasets in a management class how many days will elapse before datasets that have changed since the last backup will be backed up again.

Bias. Indicates the most frequent type of I/O expected for a dataset. If the MSR value indicates that caching is required, the bias value determines eligibility for caching or DASD fast write. Bias values may be:

If bias is unknown or equal, datasets get cached when required to satisfy the MSR objective.

R Use cache for read operations.

W Use DASD fast write for write operations.

Glossary 79

Block Multiplexor. Parallel channel where data is exchanged in blocks of information (multiple bytes). DASD devices are examples of high speed devices that use block multiplexing.

Block Size. Physical record size for storage of data in a dataset and transfer of that data during an I/O operation.For a DASD dataset, block size is maintained in the Dataset Control Block (DSCB).

Bypass-Cache. Function that forces I/O to go directly to a DASD device regardless of whether the data may be or currently is cached.

Byte Multiplexor. Parallel channel where data is exchanged with byte interleaving (one byte at a time). Printers are examples of slow devices that use byte multiplexing.

C

CA. See Control Area.

Cache. In a storage hierarchy, a small unit of high-speed storage that contains the active elements otherwise found in a larger unit of slower (less expensive) storage. Cache enables fast access to frequently referenced information.

Cache Categories. See May Cache, Must Cache, and Never Cache.

Cache Collection Interval. Time interval in which cache control unit

status and performance data is collected by OMEGAMON XE.

Cache Control Unit. DASD storage control unit that has its own high-speed storage built in. This storage is used for frequently-used data so that access to that data is faster than access to data on DASD.

Cache Fast Write. Function of DASD 3990 model 3 storage controllers that writes data to cache at channel speed. The data is later written to DASD.Cache fast write differs from DASD fast write in that the data is not written to Non-Volatile Storage (NVS).

Cache Reset Interval. Time interval during which cache statistics are sampled and accumulated by OMEGAMON XE prior to a new collection cycle.

Cache Statistics Interval. The time interval during which cache control unit status and performance statistics are sampled. When a new statistics interval begins, data will be refreshed when you press F5 or Enter.One or more cache statistics intervals can occur within the cache reset interval. The default length of the interval is 180 seconds.

Cache Utilization. Overall performance of a cache subsystem. A common measurement is the percentage of total I/O operations that complete in cache without having to reference DASD.


Caching Active. When I/O to a device is eligible to use cache if the device is attached to a cache control unit.

Caching Inactive. When I/O to a device is ineligible to use cache even though the device is connected to a cache control unit.

Cataloged Dataset. Dataset that has an entry in a system catalog which identifies the location (volume) and attributes of the dataset, allowing it to be referenced by name only.

Channel Path. Part of a computer system that performs I/O operations, linking central storage with I/O devices. Also referred to as a channel.

Channel Path Identifier (CHPID). Identifies the channel path to the system.

Channel Path Status. Indicates whether the channel path is active (online) or inactive (offline).

Channel Path Type. Different types of channel paths used in MVS architecture are:� block multiplexor� byte multiplexor� Enterprise Systems Connection

(ESCON)� ESCON with converter

Channel Path Utilization. Percentage of time I/O operations are active on a channel path.

CI. See Control Interval.

Collection Interval. Length of time during which statistics are gathered and summarized by OMEGAMON XE before being reset for the next period of time.Collection intervals affect the following:� accuracy of realtime information� amount of data stored for historical

reporting� amount of system resources used by the

CMS and Candle subsystem components of OMEGAMON XE

Command Backup. Management class attribute indicating whether datasets within a management class can be backed up by HSM command and the type of authority required to issue the backup command.

Common Service Area (CSA). Area of virtual storage that is commonly addressable to all address spaces.

Compress. DFDSS service that recovers fragmented space within a partitioned dataset.

Connect Time. Part of I/O during which data is located on the track and transferred between the DASD device and central storage.

Contention Rate. Rate at which I/O operations are queued, due to busy conditions on physical paths, to devices assigned to a logical control unit.

Control Area (CA). In a VSAM dataset, a group of control intervals used as a unit for formatting a dataset and distributing free space.

Glossary 81

Control Area (CA) Free Space Percent. Percentage of free space to be left within a VSAM CA after a cluster is loaded, or the percentage of free space to be left after a CA split.

Control Interval (CI). Unit of information that VSAM transmits to or from DASD. On DASD, it is a fixed-length area in which VSAM stores records and creates distributed free space.

Control Interval (CI) Free Space Percent. Percentage of free space left when a VSAM cluster is loaded, or the percentage of free space to be left after a CI split.

Control Interval (CI) Size. Physical record length for VSAM datasets.

Control Unit. Device that connects the processor to DASD devices and controls the access to them.

Convert to SMS. Process of converting datasets on a nonSMS-managed volume to SMS managed control.

Cylinder. Same track on each platter, in a stack of platters within a particular DASD device, which forms a cylinder.

D

Daily Space Management. HSM daily process of migrating unreferenced datasets, releasing unused dataset space, and reducing dataset extents on volumes.

DASD Fast Write. Function of 3990 model 3 DASD storage controllers where data is written to both cache and Non-Volatile Storage (NVS) at channel speed.

DASD Fast Write Active. When a volume is defined to be eligible for DASD fast write if it is connected to a cache control unit.

DASD Fast Write Retry. Retry when a DASD fast write cannot complete because of Non-Volatile Storage (NVS) constraint.

DASD Group. Either an SMS storage group or a user-defined DASD group of volumes using the same set of thresholds for monitoring by OMEGAMON XE

DASD Recording Interval. Frequency with which SMF records containing DASD statistics are written by OMEGAMON XE.

Data Class. Describes physical attributes and space requirements for SMS managed datasets.

Data Control Block (DCB). Control block describing dataset attributes that is used by access method routines in storing and retrieving data.

Data Facility Data Set Services (DFDSS). IBM licensed product used to perform utility functions such as copying and moving datasets and defragmenting volumes.


Data Facility Hierarchical Storage Manager (DFHSM). IBM licensed product used for dataset archiving, backup, and recovery, and managing space on volumes.

Dataset Control Block (DSCB). DASD Volume Table of Contents (VTOC) entry describing a dataset and its extents.

Dataset Organization (DSORG). DCB parameter that specifies the physical organization of the dataset.

DCB. See Data Control Block (DCB).

DCM. See Dynamic Cache Management (DCM).

DCME. See Dynamic Cache Management Enhanced (DCME).

Default Device Geometry. SMS uses default device geometry when placing datasets, so that the amount of space will be consistent and most efficiently used no matter what device is chosen. Default device geometry isolates the user from the actual physical device.

Default Profile. A Candle-supplied set of values that define the preferences and thresholds that are used for an OMEGAMON XE session. It does not include applications or user groups defined for monitoring.The default profile is shipped and installed with the product.This is the first profile that is loaded when an OMEGAMON II session begins.

It's values may be overridden by the site profile or a user profile.

Defragment. Relocating dataset extents in order to create larger contiguous areas of free space on a volume.Destage to DASD. When new or updated data is written to DASD from cache or Non-Volative Storage (NVS) by a cache control unit.Device Address. Four hexadecimal digits that define a physical device. Device address has no required relationship to channel path ID (CHPID).

Device Geometry. Describes the number of bytes per track and number of tracks per cylinder for a specific device type.

Device MPL. I/O density for a device, which is the product of the I/O rate, I/O per second, and the device MSR.

Device Type. Model of the DASD device, such as 3380 or 3390.

DFDSS. See Data Facility Data Set Services (DFDSS).

DFHSM. See Data Facility Hierarchical Storage Manager (DFHSM).

Direct Access Storage Device (DASD). Provides data storage that is peripheral to the processor and allows an application to access records in any order.

Glossary 83

Directory Block. Physical portion of a Partitioned Dataset (PDS) that describes its members.

Disconnect Time. Time that I/O spends, freed from the channel, searching for or requesting data. This is the time that the I/O searches for the data that has been requested. This time includes moving the device to the requested cylinder and track, waiting for the record to rotate under the head (rotational delay), and waiting for the channel to become available.

Dual Copy. Function of 3990 model 3 storage controllers where the storage control subsystem maintains two identical copies of a DASD volume, thus increasing the data's availability.

Dummy Storage Group. Contains the volume serial numbers of DASD volumes no longer on the system so that existing JCL referencing these volumes will still work. Volumes on dummy storage groups are treated as SMS managed volumes.

Dump Class. Output class assigned when HSM dumps a volume within a storage group.

Duplex Pairs. Configuration of two physical devices on a 3990 model 3 Storage Controller that composes one logical volume to enable dual copy operations.

Dynamic Cache Management (DCM). A feature of DFP 3.2 that operates on 3990 Model 3 control units. DCM optimizes cache storage by assigning each dataset to a caching category on the basis of its storage class MSR objective.

Dynamic Cache Management Enhanced (DCME). A feature of DFSMS 1.1 that operates on 3990 Model 3 control units. In a DCME environment, cache category assignment and caching operations for must cache and never cache datasets are identical to DCM. DCME improves cache management for may cache datasets by recording read and write hit ratios for an initial forced cache interval of 100 I/Os and comparing them against an internal subsystem threshold.

E

Elapsed Time. Amount of time that has passed since the beginning of an interval.

Enqueue. A service of MVS to protect serial access to a resource, accomplished by forcing release and reserve holds for actuators.

Enqueue Conflict. The result of a task attempting to access an exclusively reserved resource.

Enterprise Systems Connection (ESCON). Channel architecture that provides a direct connection of fiber optic channels to a mainframe processor.


These fiber optic channels allow peripheral devices to transfer data at much higher rates and to be located remotely from the mainframe.Two pieces of hardware facilitate an ESCON connection:

Exception. OMEGAMON XE response to a threshold being exceeded for any monitored object. Exceptions are reported by status indicators, and the actual values that caused the exceptions to be issued are reported on display panels within the product.Expiration Days Non-usage. A management class option that indicates how many days should elapse after the last access to a dataset, before it is eligible for expiration.Extended Common Service Area (ECSA). Part of the Common Service Area (CSA), an area of virtual storage that is commonly addressable to all address spaces, which is allocated above the 16M line.

Extended Private Storage. Portion of private storage that resides above the 16M virtual storage line.Extent. Contiguous DASD space containing part or all of a dataset. When the size of a dataset exceeds its primary space allocation, extentions (extents) will be added using the secondary space allocation.

External Security. A third-party software package that can control access to and to protected functions.External security can replace or work with OMEGAMON II's internal security.

F

Force. DFDSS parameter that bypasses normal move restrictions and allows an unmovable dataset to be moved or copied.

Format 0 Dataset Control Block (DSCB). Empty VTOC entry that is available for use. Also known as a free format DSCB.

Fragmentation. The breaking up of free space on a volume into small, noncontiguous pieces as data is created, moved, and deleted over time.

Fragmentation Index. A numeric value calculated by the operating system that indicates the amount of fragmentation on a volume. The higher the index value, the more fragmentation exists on the volume.

ESCON converter

Hardware that enables a device not supporting fiber optic communication to be hooked into an ESCON configuration.

ESCON director

Hardware that enables multiple systems to share devices by handling the routing of data among different mainframes and devices.

Glossary 85

Free Space. The amount of unused space on a volume or within a storage group. This value is usually expressed as a percentage.

G

Generation Data Group (GDG). Group of datasets where the next incremental number is assigned to the dataset name each time a new version of the dataset is created. This number allows access to current and previous versions as required. Each time a new dataset is created, the oldest member of the group is retired (rolled off).

Generation Data Group (GDG) Elements on Primary. Number of the most recent generations of a GDG to keep on primary storage. Generations exceeding the limit become eligible for early migration during the next daily space management cycle.

Generation Dataset (GDS). One generation of a generation data group (GDG).

Global Resource Utilization (GRS). An IBM system service used to serialize (perform in sequence) the access to resources across multiple systems in order to ensure data integrity.

Global Resource Utilization (GRS) Ring. The group of systems within a complex controlled by GRS.

Guaranteed Backup Frequency. Maximum number of days that can elapse between backups for any given dataset within the storage group.

Guaranteed Space. An SMS storage class attribute used to allocate multivolume datasets or to point to a specific volume for dataset placement.

Guaranteed Synchronous Write. Indicates a synchronous (after) or unsynchronous (before) return, if a wait or BSAM check is issued when writing to a PDSE member, before the data has actually been written to DASD. It ensures that data transfer occurs and is complete between the channel and the device when write operations are issued to a PDSE.

H

Hierarchical Storage Manager (HSM). See DFHSM.

Hit Percent. Ratio of I/O requests that were satisfied from the storage control unit cache without requiring access to DASD.

HSM Backup. HSM process of creating backup copies of a dataset to allow the dataset to be recovered if deleted or damaged.

HSM Control Datasets. The datasets into which HSM writes statistics and control information to keep track of dataset migrations, backups, and dumps.


HSM Dump. HSM process of creating backup copies of all the datasets on a volume to allow the volume to be recovered if deleted or damaged.

HSM Level 0 Storage. Primary or user volumes not owned by HSM. Data is directly accessible.

HSM Level 1 Storage. Volumes (typically DASD) owned by HSM containing data migrated from Level 0.

HSM Level 2 Storage. Volumes (typically tape) owned by HSM containing data migrated from Level 0 or Level 1.

HSM Migration. See Migration.

HSM Recall. HSM process of recalling a dataset from a migrated state so that it can be directly accessed.

HSM Recovery. HSM process of restoring a dataset from a backup copy. If HSM performs daily backups, the recovered dataset will reflect the previous day's status.

I

IDCAMS. The IBM access method services program that can be invoked as a job or jobstep, from a TSO terminal, or from within a user's program.

Incremental Backup. HSM process of making a backup copy of a dataset that has been updated since its last backup.

Index Options. Options that control how VSAM accesses the index component of a keyed VSAM dataset.

Indexed VTOC. Fast-access mechanism to records within the VTOC.

Inhibit Cache Loading. MVS I/O mechanism to prevent a request from being cached, even if it is eligible. If the data is already in cache, the request will be satisfied by cache.

Interval Migration. Automatic migration by HSM that is triggered when the high allocation/migration threshold for a volume is reached or exceeded during a specified time interval.

I/O Rate. Average number of I/Os per second.

IOS Queue Time. Average time that an I/O waits because the device is already busy (signified by the device's UCBBUSY bit being on).

J

Journal Dataset. Accumulation of recent updates (a log of changes) to an HSMcontrol dataset.

K

Key Length. DCB parameter that specifies the length in bytes (0–255) of a record key. The key may be part of the record or, for non-VSAM DASD datasets, may precede the block.

Glossary 87

Key Position. DCB parameter (RKP) that specifies the distance in bytes of the key from the beginning of the data record.

LLocality of Reference. Indicates the placement of a dataset on a volume for good performance. If data can be quickly located and accessed it is said to have good locality of reference.Logical Control Unit (LCU). Representation of either a single control unit, with or without attached devices, or a group of control units that share devices.Logical Control Unit Identifier (LCU ID). System-assigned identifier of a logical control unit.

Logical Record Length (LRECL). Data Control Block (DCB) parameter that specifies the length, in bytes, of each record in the dataset (fixed format), or the maximum record length (variable or undefined format).

MManagement Class. SMS construct which contains attributes that determine migration, backup, and retention objectives for datasets. This class is optional for SMS-managed datasets.Manual Tape Library Dataserver(MTLDS). A set of tape drives and volumes that are connected by a library manager application, and are manipulated manually.

Management Work Element (MWE). HSM control block describing a unit of work within HSM.

May Cache. A cache category assigned to SMS-managed datasets using Dynamic Cache Management (DCM) or Dynamic Cache Management Enhanced (DCME). This status applies to datasets that do not have critical service levels, since they are cached only if space is available in cache memory. Datasets with medium MSR objectives are eligible for this cache category.

Migration. HSM process of moving datasets from one level of storage to a level below it in HSM's hierarchy. See also HSM Level 0 Storage:, HSM Level 1 Storage, and HSM Level 2 Storage.

Migration Control Dataset (MCDS). Dataset used by HSM that contains statistics and control information for migrated datasets and volumes under HSM control that are used in migration.

Migration Days Non-Usage. Minimum number of days that must elapse since a dataset was last accessed before it is eligible for migration to the next lower level of storage in the storage hierarchy. This number will vary depending on the level to which it is migrated.

Millisecond Response (MSR) Objective. Desired response time for a dataset in a storage class. Used to control placement of a dataset on a


volume at allocation time and to control cache eligibility for datasets within the storage class.

Millisecond Response Time (MSR). Amount of time it takes for an I/O request to complete (in milliseconds) to a given DASD. It comprises IOS queue, pending, disconnect, and connect times.

Minimum Secondary Allocation. Smallest secondary allocation quantity that will qualify a dataset for inclusion in the DFDSS space release operation. Datasets whose secondary allocations are defined as less than the specified number of tracks will not undergo the space release operation.

Minimum Unused Space. Smallest amount of unused space remaining in a dataset that will qualify it for inclusion in the DFDSS space release operation. Datasets with less unused space than the number of tracks specified will not undergo the space release operation.

MPL. See Device MPL.

MTLDS. See Manual Tape Library Data Server(MTLDS).

Multi-Volume Dataset. Dataset that occupies space on more than one volume (DASD or tape).

Must Cache. A cache category assigned to SMS-managed datasets using Dynamic Cache Management (DCM) or Dynamic Cache Management Enhanced (DCME). This status is

reserved for datasets whose response time service levels are critical. Datasets with low MSR objectives are eligible for this cache category.

N

Never Cache. A cache category assigned to SMS-managed datasets using Dynamic Cache Management (DCM) or Dynamic Cache Management Enhanced (DCME). This status applies to datasets that are not response-critical and therefore do not require caching. Datasets with high MSR objectives are eligible for this cache category.

No Promote. I/O operations that did not transfer data from DASD to cache because free segments in cache were not available.

Non-sequential I/O. I/O operations that did not specify sequential access in the Define Extent channel command word (CCW). If non-sequential, additional data is not staged to the cache.

Non-Volatile Storage (NVS). High-speed component of 3990 model 3 cache control units used during DASD fast write and dual copy operations. Since it has its own battery power, in the event of a power loss, the data will be preserved up to 48 hours.

Non-Volatile Storage (NVS) Constraint. When there is insufficient space in NVS to complete a DASD fast write or dual copy operation.

Glossary 89

Normal I/O. Channel operations in which specific caching modes (Cache Bypass, Cache Inhibit, Cache Fast Write) were not specified in the Define Extent channel command word (CCW), thus allowing normal cache replacement to occur.

O

Object Backup Storage Group. SMS storage group that describes the physical storage used for backup copies of objects.

Object Storage Group. SMS storage group that describes the physical storage used for objects.

Offline Control Dataset (OCDS). Dataset used by HSM that contains control information for offline storage, including a list of tapes it is currently using and the datasets on these tapes.

P

Partial Release. Management class option for non-VSAM datasets, used to determine when unused allocated space (in cylinders or tracks, depending on the space allocation unit) is to be released.

Partitioned Dataset (PDS). Dataset composed of a directory and members. It is essentially like a set of sequential files grouped together. PDSs may reside only on DASD. Certain system data, such as programs (load modules or source modules), reside in PDS members.

PDS Format. Original (pre-SMS) internal structure of a partitioned dataset (PDS) which periodically requires compression to recover fragmented space. This structure does not have to be SMS managed.

PDSE Format. Improved internal structure for a partitioned dataset (PDS), in which space is allocated in 4K blocks and can only be managed by SMS. PDSE formatted datasets do not require compression.

Pending Time. Time that the I/O is delayed in the path to the device. Pending time may be attributable to channel or control unit path busy.

Percent Busy. Percentage of time a resource is busy processing I/O requests.

Persistent Data Store. Component of OMEGAMON XE that stores historical data. OMEGAMON XE writes data to the PDS at the end of each RMF interval. The length of time for which historical data is available is a function of the size and the archiving characteristics of the PDS, which are specified during product customization.

Pinned Data. Data that is held in NVS, because of an error, until it can be destaged to DASD or explicitly discarded using a host command.

Pool Storage Group. Type of SMS storage group that contains the volume serial numbers of DASD devices to be managed as a single entity.


Preferences. A set of display options that you can specify for all OMEGAMON XE panels. For example, date and time format.

Primary Space Allocation. Initial amount of space that is allocated for the dataset.

Private Storage Below 16M. Portion of virtual storage addressable by a single address space or application, such as HSM.

Private Tape. A magnetic tape that has been assigned to a specific individual or function. The opposite of a scratch tape.

Private Volume Mount Status. Volume mount attribute indicating that datasets must be allocated to the volume only by its specific volume serial number.

Profile. A set of values that define the preferences, thresholds, defined applications, and user groups for an OMEGAMON XE session. There are 3 types of OMEGAMON XE profiles:� default profile� site profile� user profileA typical installation includes one default profile, one site profile, and multiple user profiles. See also Default Profile, Site Profile, and User Profile.

Profile Loading. The process of copying a stored profile from DASD into memory. At logon, OMEGAMON XE

loads profiles in the following order:� default profile� site profile (optional)� user profile (optional)

Profile Ownership. Identifies the user who can save changes to or delete a profile. The profile owner is either the creator of the profile, or the user whose user ID matches the profile name. Only a product administrator can save changes to a profile created by another user. The product administrator will not become the owner of this profile.

Public Volume Mount Status. Volume mount attribute indicating that the volume can be used by the system to allocate temporary datasets and work space.

Pushbutton. Quick way to access OMEGAMON XE panels containing information that is closely related in subject and level of detail to the current display panel. Push buttons appear as short phrases enclosed within brackets at the bottom of display panels, directly above the function key area. To use a push button, place your cursor on the push button and press Enter.

R

Read Hit. When a read request for data is made by the processor and resolved from storage controller cache. As a result, the request does not require DASD access.

Glossary 91

Read Request. Request for data by the processor that requires only that the data be read, not written.

Record Format (RECFM). Data Control Block (DCB) parameter that specifies the type and blocking characteristics of records in the dataset.

Record Organization (RECORG). Data class attribute that specifies the type of VSAM dataset. It may be key sequenced (KS), entry sequenced (ES), relative record (RR), or linear space (LS). If RECORG is blank, the dataset is non-VSAM; it is either physical sequential or PDS organization.

RECORG. See Record Organization.

Reserve. Mechanism used in a shared DASD environment to ensure that users in different systems do not update the same dataset at the same time.

Resource Contention. When a resource is requested by more than one task or process simultaneously.

Resource Monitoring Facility (RMF). IBM program product that collects important performance information, such as resource utilization and average response time data. This data is written to SMF for performance reports and is used by OMEGAMON XE to help identify resource problems.

Resource Monitoring Facility (RMF) Interval. Time interval in which the data that RMF has collected is summarized and written to SMF for later

use. RMF clears out the information it has collected and starts a new collection cycle at the start of every interval.

Response Time Collection Interval. Time interval in which OMEGAMON XE collects response time information for DASD volumes.

Retain Days. How many days to keep the most recent backup version of a deleted dataset, and how many days to keep versions other than the most recent for active datasets.

Retention Limit. Value specified in the data class definition that limits those retention period and expiration date values explicitly specified in JCL.For example, if the retention limit specified in the data class definition is 5 days, while the limit specified in the JCL is 10, the value of 5 will be used.

RMF. See Resource Monitoring Facility (RMF).

RMF Interval. See Resource Monitoring Facility (RMF) Interval.

Rolled-off Generation Dataset (GDS) Action. Management class attribute that indicates if a GDS that has been rolled off the Generation Data Group (GDG) due to age will expire or become eligible for migration.

Rotational Delay. Time during an I/O operation that a DASD device spends rotating to the required position on a track for data to be transferred.


S

Scaling Factor. A multiplication factor to be applied against a block length value for primary and secondary space allocations. See also AVGREC.

Scratch Tape. A magnetic tape that is available to be assigned to a specific individual or function, at which point it becomes a private tape.

Secondary Space Allocation. Amount of space that is allocated for each dataset extent beyond the primary allocation.

Seek. The motion required to position the actuator on a device with a movable head (3380 or 3390, or equivalents) at the requested cylinder and track.During the seek time, the device is freed from the channel, which can then handle other I/O requests.

Seek Time. Time during an I/O that the actuator travels to a requested cylinder and track on a device with a movable head (3380 or 3390). During this time the device is freed from the channel, which can then handle other I/O requests.

Sequential I/O. I/O operations where sequential access is specified in the Define Extent channel command word (CCW).Sequential I/O operations cause DASD cache control units to stage additional data beyond what is referenced by the

current I/O operation. The additional data will be available in cache on the next sequential I/O operation.

SETCACHE. An IBM IDCAMS command used to allow or prohibit access to the cache storage of 3880 and 3990 controllers.

Share Options. Defines how multiple users within single or multiple MVS images share access to a VSAM component or cluster.

Site Profile. Installation-defined set of values that specify the preferences, thresholds, defined applications, and user DASD groups for an OMEGAMON XE session. These settings will override the corresponding settings in the default profile. The product administrator can create one site profile for an installation.See also Default Profile.

Slot. A space in a tape library dataserver where a cartridge is stored.

SMF. See System-Managed Facilities (SMF).

SMF Interval. See System-Managed Facilities (SMF) Interval.

SMS Managed Volume. Volume that contains only SMS managed datasets and is assigned to an SMS storage group. DASD volumes in an SMS storage group must contain an indexed VTOC.

SMS Status of a Volume. Indicates whether the volume is or is not managed

Glossary 93

by SMS, or is in the process of being converted to SMS control.

Space Statistics Frequency. Number of response time intervals in which space and capacity information is collected by OMEGAMON XE for DASD volumes.

Started Task. Address space initiated via the MVS START command, which executes a cataloged procedure. Started tasks usually perform some system service.Some started tasks, such as CONSOLE or DUMPSRV, are started automatically by the system, while others can be started at IPL time if they are named to the COMMNDxx member of PARMLIB.Unlike TSO transactions or batch jobs, started tasks typically run throughout the day, often waiting for a specified time or event.

Status Indicators. Lights and the characters within them that provide a quick overview of your system's health. They quickly show you whether service levels at your installation are being met. Service levels are defined by your organization and monitored according to thresholds and parameters that you set in OMEGAMON XE profiles.On color terminals, OMEGAMON XE uses lights to identify the condition of each component that it is monitoring: red for critical, yellow for warning, and green for normal. On non-color

terminals, status characters indicate the condition of the component.

Storage Class. An SMS construct containing attributes that determine performance and availability objectives for datasets.

Storage Controller. Portion of a DASD control unit that executes I/O commands sent from a channel to devices attached to the control unit.

Storage Director. Part of the control unit that decodes channel commands.

Storage Director ID (SD ID). 1-byte identifier of a storage director, regardless of its selection address.

Storage Group. SMS construct used to group DASD devices in order to separate the logical requirements of accessing data from the physical requirements of storing the data. DASD volumes in an SMS storage group must contain an indexed VTOC. See also Storage Group Type.

Storage Group Status. Defines how SMS accesses volumes within a storage group on a system. The possible statuses are:

Enable (the default)

System can allocate and access all datasets in the storage group.

Disall (Disable All)

System cannot allocate or access datasets in the storage group.


Storage Group Type. Indicates the type of physical storage used by an SMS storage group. The five types of storage groups, which are defined separately in this glossary, are:� Virtual Input/Output (VIO)� Dummy� Pool� Object� Object backup

Storage Management Subsystem. The IBM DFSMS facility used to centralize and automate the process of storage management. Storage that is managed in this manner said to be system-managed.

Storage Path. Hardware within a 3990 or equivalent control unit that transfers data between DASD and a channel.

Storage Subsystem. One or more storage controllers and their attached storage devices.

Storage Subsystem ID (SSID). 2-byte unique value used to identify a 3990 storage control unit.

Storage Volume Mount Status. Volume mount attribute indicating that volume can be allocated with an esoteric or generic volume name.

System-Managed Facilities (SMF). IBM program product that provides the means for gathering and recording information that can be used to evaluate system usage.

System-Managed Facilities (SMF) Interval. Time interval in which the data collected by SMF is summarized and written to SMF datasets. This interval is available globally to SMF and RMF.

System-Managed Storage. Methodology for managing storage that relies on separation of the logical requirements of accessing data from the physical requirements of storing the data. In system-managed storage, data placement is determined by the system, and data management is automated.

Disnew (Disable New)

System cannot allocate new datasets in the storage group.

Quiall (Quiesce All)

System cannot schedule jobs to allocate or access data in the storage group. (JES3 only)

Quinew (Quiesce New)

System cannot schedule jobs to allocate new data in the storage group. (JES3 only)

Notcon (Not Connected)

Storage group is defined but not connected.You cannot dynamically change this status. You must re-configure and activate the new configuration to change the Notcon status.

Glossary 95

T

Tape Group. An OMEGAMON XE convention for reporting on tape drives by library or device type.

Tape Group Type. Identifies to OMEGAMON XE, the type of tapes that compose a tape group. Valid group types are:� ATLDS for tapes in an automated tape

library dataserver.� MTLDS for tapes in a manual tape

library dataserver.� No Lib for tapes that are not associated

with a library.

Tape Library. A set of tape volumes and the tape drives where those volumes may be mounted.

Tape Storage Group. A logical group of datasets or volumes residing on tape, which is defined to the SMS subsystem.

Threshold. Values stored in the active profile that OMEGAMON XE compares with the data it collects from your system. If threshold values are exceeded, OMEGAMON XE status indicators change to yellow or red, depending on the severity of the exceptional condition.

Track. Part of a DASD disk that can be accessed by the read/write head during one rotation. A set of tracks on a DASD volume that are equidistant from the axis form a cylinder.

Trend. Type of OMEGAMON XE display that presents historical data from

the PDS for a single object over a period of time.

UUnmovable Dataset. Dataset which normally should not be moved from its location on a volume. Typically, an unmovable dataset uses absolute addressing where each record is addressed by its actual physical location on the volume.

Unreferenced Interval Count (UIC) Range. The range of time in seconds that the oldest frame of pageable storage has gone without being referenced. The unreferenced interval count (UIC) is inversely related to contention for real storage--the lower the UIC, the more quickly frames are being referenced.

User-defined DASD Groups. OMEGAMON II facility that enables you to define groups of DASD volumes by volser and device address which are then monitored by OMEGAMON XE as a single entity.

User Profile. User-defined set of values that specify the preferences, thresholds, defined applications and user groups for an OMEGAMON XE session. These settings will override the corresponding settings in the default and site profiles.A typical installation has multiple user profiles, identified by the name and owner of the profile.


See also Default Profile, Profile Ownership, and Site Profile.

V

Virtual Input/Output (VIO). A way of simulating DASD I/O devices by using virtual storage.

VIO Max. Maximum size in kilobytes of datasets to be allocated to VIO storage groups.

VIO Storage Group. An SMS type of storage group used to allocate datasets to paging storage, simulating the activity of DASD volumes. VIO storage groups do not contain any actual DASD volumes.

VIO Unit Type. Generic DASD device type that a VIO storage group simulates.

Volser. A 6-character name assigned to a DASD or tape volume. Also known as volume serial number or volume ID.When you specify volser, it can be specific or generic. Use the wildcard character (*) for generic. For example, volser AB* specifies all volsers starting with AB.

Volume Group. On OMEGAMON XE volume summary displays, the volumes in use by an application, or defined to a:� channel path ID� logical control unit� cache control unit� SMS storage group� user DASD group

Volume ID. Six-character name assigned to a DASD or tape volume. Also known as volume serial number or volser.

Volume Table of Contents (VTOC). Special dataset on each DASD volume that contains records giving the names and locations of all datasets (including itself) on the volume. The VTOC also contains records that describe free space available on the volume.

Volume Table of Contents (VTOC) Index Record. Record within an indexed VTOC that either describes a dataset or the free space available on the volume.

VSAM Cluster. VSAM datasets (KSDS, RRDS, ESDS, LSDS) that include both data and index components.Index components are used for indexed datasets (KSDS).

W

Wildcard. Used to specify a pattern. In OMEGAMON XE, the wildcard character is an asterisk (*). For example, volser AB* specifies all volsers starting with the characters AB (such as ABA001, ABGG03, and ABZZZ3).

Write Hit. When a write request for data is made by the processor and resolved from storage controller cache. As a result, the request does not require DASD access.

Glossary 97

#

3880 Storage Controller. Refers to the 3880 family of IBM storage controllers. The characteristics of 3880 models vary, but they all have these features in common:� attaches 3380 DASD� contains two caching storage directors

(models 13 and 23)� caches data from DASD on a track basis

for read operation (models 13 and 23)

3990 Storage Controller. Refers to the 3990 family of IBM storage controllers. The characteristics of 3990 models vary, but they offer features not found in 3880 controllers:� faster internal processing� ESCON connectivity (models 2 and 3)� more storage paths (models 2 and 3)� contains non-volatile storage which

makes DASD fast write and dual copy operations possible (model 3)

Index 99

Index

AAdobe portable document format 8advanced monitoring facilities 17application summary report 55associating reports with attributes 28attribute 25attribute group 25attribute item 25attributes

composition of 25organization of 25structure of 25understanding 25using 25

Bbenefits

enhances system performance 21increases knowledge 21of OMEGAMON XE for OS/390 20simplifies application and system

management 21building situations 25

Ccacge cu status report 59cache cu performance report 57Candle Command Center

definition 14–15Candle Management Server 15Candle Management Workstation

benefits 15CandleNet Portal

formats for information 27CandleNet Portal server 15channel path report 61commands, Take Action 31

components of CCC 15composition of an attribute 25

Ddefining an attribute 25defining situations 32

Eevaluating

tuning decision 28event

investigating 29event indicator 29Event workspace 29Event workspace, opening 29

Ffavorites, adding a workspace to 30filtering 29

Hhistorical data collection 18HSM status report 63

Iidentifying

system bottlenecks 28installing OMEGAMON XE for OS/390 21introducing

OMEGAMON XE for Storage 13investigating an event 29

Llogical control unit report 65

M


Mmanaged system 25, 28monitoring

facilities 17performance 25, 28

monitoring agents 15

OOMEGAMON for Storage workspaces 54OMEGAMON XE for Storage

benefits 20user interface 17

Pplanning and installation 21printing problems 8properties

defining for a workspace 29

Rrelationship between attributes and

reports 28remote agents 25reports

purpose of 18

Sserver, CNP 15situations

definition 32SMS base configuration table 67SMS storage groups performance 68SMS storage groups space report 70sorting 30state change 28structure of an attribute 25

TTake Action 31

Take Action commandsexecuting a saved command 31

tape group report 71threshold values, setting 28

Uuser DASD groups performance report 73user DASD groups space report 74user interface 17using attributes 25using OMEGAMON XE for OS/390 17using reports 27

Vviewing

attribute information 28virtual tape subsystems report 75

Wworkspace

adding to favorites 30defining properties 29Event 29

workspace, Eventopening 29

workspacesapplication summary 55cache cu performance 57cache cu status 59channel path 61HSM status 63logical control unit 65SMS base configuration 67SMS storage groups performance 68SMS storage groups space 70tape group 71user DASD groups perormance 73user DASD groups space 74virtual tape subsystems 75

omegamon xe for storage user’s guidഀ攀Ⰰ...

Documents