ibm tivoli business systems manager: getting...

IBM Tivoli Business Systems Manager

Getting StartedVersion 2.1

GC32-0801-00

��

NoteBefore using this information and the product it supports, read the information in Appendix B, “Notices” on page 37.

First Edition (September 2002)

©This edition applies to version 2, release 1 of Tivoli Business Systems Manager (product number 5698–BSM) andto all subsequent releases and modifications until otherwise indicated in new editions.

Contents

Preface . . . . . . . . . . . . . . . vWho Should Read This Document . . . . . . . vWhat This Document Contains . . . . . . . . vPublications . . . . . . . . . . . . . . v

IBM Tivoli Business Systems Manager Library . . vPrerequisite and Related Publications . . . . . viAccessing Publications Online . . . . . . . viOrdering Publications . . . . . . . . . . viProviding Feedback about Publications . . . . vii

Contacting Customer Support . . . . . . . . viiAccessibility Information . . . . . . . . . . viiConventions Used in This Document. . . . . . vii

Typeface Conventions . . . . . . . . . . viiCommand Syntax . . . . . . . . . . . viiiTerminology . . . . . . . . . . . . . viii

Operating-specific Information . . . . . . . . ix

Chapter 1. Overview . . . . . . . . . 1What Is Tivoli Business Systems Manager? . . . . 1What Is a Business System? . . . . . . . . . 2Discovery Processing . . . . . . . . . . . 2Event Processing . . . . . . . . . . . . . 3Monitoring Options . . . . . . . . . . . . 3Reporting System. . . . . . . . . . . . . 5Instrumentation . . . . . . . . . . . . . 5Problem and Change Support . . . . . . . . 5

Chapter 2. Tivoli Business SystemsManager Components. . . . . . . . . 7Components for Handling OS/390 Data . . . . . 7Components for Handling Distributed Data . . . . 9Base Services and Components . . . . . . . . 10

Servers . . . . . . . . . . . . . . . 10Consoles . . . . . . . . . . . . . . 11Health Monitor . . . . . . . . . . . . 11

Chapter 3. Data Sources . . . . . . . 13Distributed Resources . . . . . . . . . . . 13MVS. . . . . . . . . . . . . . . . . 14

MVS Console . . . . . . . . . . . . . 14Resource Management Facility . . . . . . . 14Tivoli NetView for OS/390 . . . . . . . . 14MAINVIEW for OS/390 . . . . . . . . . 15OMEGAMON for MVS . . . . . . . . . 15ASG-TMON for MVS . . . . . . . . . . 15

Storage Management Resources . . . . . . . 15System-Managed Storage . . . . . . . . . 15Data Facility Systems Managed StorageHierarchical Storage Manager . . . . . . . 16Extended Remote Copy . . . . . . . . . 16

CICS Subsystems . . . . . . . . . . . . 17CICSPlex System Manager for OS/390 . . . . 17MAINVIEW for CICS . . . . . . . . . . 17OMEGAMON for CICS . . . . . . . . . 18

ASG-TMON for CICS . . . . . . . . . . 18DB2 Subsystems . . . . . . . . . . . . . 18

Monitoring of Subsystems Running DB2Universal Database . . . . . . . . . . . 18MAINVIEW for DB2 . . . . . . . . . . 19OMEGAMON for DB2 . . . . . . . . . 19ASG-TMON for DB2 . . . . . . . . . . 19

IMS Subsystems . . . . . . . . . . . . . 19IMS Monitoring . . . . . . . . . . . . 19MAINVIEW for IMS . . . . . . . . . . 20OMEGAMON for IMS. . . . . . . . . . 20

Job Schedulers . . . . . . . . . . . . . 20Tivoli Operation Planning and Control . . . . 21Tivoli Workload Scheduler . . . . . . . . 21CA-7 . . . . . . . . . . . . . . . 21CONTROL-M for OS/390 . . . . . . . . 21ASG-Zeke . . . . . . . . . . . . . . 22

Automation Products . . . . . . . . . . . 22System Automation for OS/390. . . . . . . 22CA-OPS/MVS . . . . . . . . . . . . 22AF/OPERATOR . . . . . . . . . . . . 22MAINVIEW AutoOPERATOR for OS/390 . . . 23

IBM WebSphere Application Server for z/OS andOS/390 . . . . . . . . . . . . . . . . 23

Chapter 4. Implementation Overview . . 25Data Collection . . . . . . . . . . . . . 25Site Preparation . . . . . . . . . . . . . 25Discovery . . . . . . . . . . . . . . . 25Enterprise Customization . . . . . . . . . . 26Installation . . . . . . . . . . . . . . 26Production Deployment . . . . . . . . . . 26

Appendix A. Discovery and ResourceMonitoring . . . . . . . . . . . . . 27Discovery . . . . . . . . . . . . . . . 27

Bulk Discovery . . . . . . . . . . . . 27Auto Discovery . . . . . . . . . . . . 27Rediscovery . . . . . . . . . . . . . 27Discovery by Event . . . . . . . . . . . 27Discovery Filtering . . . . . . . . . . . 28Automatic Business System Support . . . . . 28Supported Discovery Functionality by Product . 28

Resource Monitoring . . . . . . . . . . . 32Base Resources . . . . . . . . . . . . 32Low-level Resources . . . . . . . . . . 32Supported Resource Monitoring Functionality byProduct. . . . . . . . . . . . . . . 32

Appendix B. Notices . . . . . . . . . 37Trademarks . . . . . . . . . . . . . . 38

Index . . . . . . . . . . . . . . . 39

iii

iv IBM Tivoli Business Systems Manager: Getting Started

Preface

This document provides an overview of IBM® Tivoli® Business Systems Manager.

Who Should Read This DocumentThis document is written for system programmers, network planners, operationsmanagers, system designers, system administrators, network operators, and otherswho need an introduction to Tivoli Business Systems Manager.

What This Document ContainsIBM Tivoli Business Systems Manager: Getting Started contains the following sections:v Chapter 1, “Overview” on page 1 provides an overview of Tivoli Business

Systems Manager.v Chapter 2, “Tivoli Business Systems Manager Components” on page 7 provides

an overview of the components of Tivoli Business Systems Manager.v Chapter 3, “Data Sources” on page 13 describes the various software products

that integrate with Tivoli Business Systems Manager to monitor resources.v Chapter 4, “Implementation Overview” on page 25 provides an overview of

implementing Tivoli Business Systems Manager in an enterprise.v Appendix A, “Discovery and Resource Monitoring” on page 27 describes the

discovery and resource monitoring functionalities by products.

PublicationsThis section lists publications in the Tivoli Business Systems Manager library andany other related documents. It also describes how to access Tivoli publicationsonline, how to order Tivoli publications, and how to make comments on Tivolipublications.

IBM Tivoli Business Systems Manager LibraryThe following documents are available in the IBM Tivoli Business SystemsManager library:v Getting Started, GC32-0801-00, provides an introduction to Tivoli Business

Systems Manager.v Installation and Configuration Guide, GC32-0800-00, describes how to install Tivoli

Business Systems Manager.v Administrator’s Guide, GC32-0799-00, describes administrative tasks for Tivoli

Business Systems Manager.v User’s Guide, GC32-0798-00, describes how to use Tivoli Business Systems

Manager to monitor the resources in your enterprise.v Messages, GC32-0797-00, describes the messages for Tivoli Business Systems

Manager.v Release Notes, GI11-0886-00, describes what’s new for this release and lists the

software and hardware requirements.v Diagnosis Guide, SC23-4840-00, describes troubleshooting problems that might

occur with Tivoli Business Systems Manager.

v

Prerequisite and Related PublicationsThe following documents provide useful information about related topics:v Tivoli NetView® for z/OS™ Command Reference, SC31-8857v Tivoli NetView for z/OS User’s Guide, GC31-8849v Tivoli Distributed Monitoring User’s Guide, GC31-8382.v Tivoli NetView for OS/390® Automation Guide, SC31-8225-02v CICSPlex® SM Concepts and Planning, GC33-0786v CICSPlex SM Administration, SC34-5401v CICSPlex SM Managing Resource Usage, SC33-1808v CICSPlex SM Web User Interface Guide, SC34-5403v AOC/MVS V1R4 OPC Automation Programmer’s Reference, SC23-3820v IMS/ESA® Open Transaction Manager Access Guide and Reference Version 6,

SC26-8743-06v IMS/ESA Version 7 Open Transaction Manager Access Guide and Reference,

SC26-9434-01v DB2® for OS/390 Instrumentation User’s Guide, GC32-0312-01

You can find additional product information on this Internet site:http://www-3.ibm.com/software/support/

The Tivoli Glossary includes definitions for many of the technical terms related toTivoli software. The Tivoli Glossary is available, in English only, at the followingWeb site:

http://www.tivoli.com/support/documents/glossary/termsm03.htm

Accessing Publications OnlinePublications in the product libraries are included in PDF or HTML formats, orboth, on the product CD. To access the publications using a Web browser, open theinfocenter.html file, which is located in the publications directory on the productCD.

When IBM publishes an updated version of one or more online or hardcopypublications, they are posted to the Tivoli Information Center. You can accessupdated publications in the Tivoli Information Center from the following CustomerSupport Web site:

http://www-3.ibm.com/software/sysmgmt/products/support/

These publications are available in PDF format. Translated documents are alsoavailable for some products.

Note: If you print PDF documents on other than letter-sized paper, select the Fit topage check box in the Adobe Acrobat Print dialog (which is available whenyou click File --> Print) to ensure that the full dimensions of a letter-sizedpage are printed on the paper that you are using.

Ordering PublicationsYou can order many Tivoli publications online at the following Web site:

http://www.ibm.com/shop/publications/order

Preface

vi IBM Tivoli Business Systems Manager: Getting Started

http://www-3.ibm.com/software/support/

http://www.tivoli.com/support/documents/glossary/termsm03.htm


http://www.ibm.com/shop/publications/order

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968v In other countries, for a list of telephone numbers, see the following Web site:

http://www.tivoli.com/inside/store/lit_order.html

Providing Feedback about PublicationsIf you have comments or suggestions about Tivoli products and documentation,send an e-mail to [email protected] or complete the customer feedback survey atthe following Web site:


Contacting Customer SupportIf you have a problem with any Tivoli product, you can contact IBM CustomerSupport for Tivoli products. See the Customer Support Handbook at the followingWeb site:


The handbook provides information about how to contact Customer Support,depending on the severity of your problem, and the following information:v Registration and eligibilityv Telephone numbers and e-mail addresses, depending on the country you are inv What information you should gather before contacting Customer Support

Accessibility InformationAccessibility features help a user who has a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface. You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface.

Refer to IBM Tivoli Business Systems Manager: User’s Guide for additionalinformation about accessibility.

Conventions Used in This DocumentThis document uses several conventions for special terms and actions, operatingsystem-dependent commands and paths, and command syntax.

Typeface ConventionsThe following typeface conventions are used in this document:

Bold Lowercase and mixed-case commands, command options, flags,and parameters that appear within text appear like this, in boldtype.

Graphical user interface elements (except for titles of windows anddialogs) and names of keys also appear like this, in bold type.

Preface

Preface vii

http://www.tivoli.com/inside/store/lit_order.html



Italic Variables, values you must provide, new terms, and words andphrases that are emphasized appear like this, in italic type.

Monospace Commands, command options, and flags that appear on a separateline, code examples, output, and message text appear like this, inmonospace type.

Names of files and directories, text strings you must type, whenthey appear within text, names of Java™ methods and classes, andHTML and XML tags also appear like this, in monospace type.

Command SyntaxThe following special characters are used in specifying commands:

[] Identifies optional arguments. Arguments not enclosed in bracketsare required.

... Indicates that you can repeat the previous argument or specifymultiple values for the previous argument.

| Indicates mutually exclusive information. You can use theargument to the left or to the right of the separator. You cannot useboth arguments in a single use of the command.

{} Limits a set of mutually exclusive arguments when one of thearguments is required. Arguments enclosed in brackets areoptional.

TerminologyFor brevity and readability, the following terms are used in this document:

MVS™

OS/390 or z/OS operating systems.

Tivoli Enterprise™ softwareTivoli software that manages large business networks.

Tivoli environmentThe Tivoli applications, based upon the Tivoli Management Framework,that are installed at a specific customer location and that address networkcomputing management issues across many platforms. In a Tivolienvironment, a system administrator can distribute software, manage userconfigurations, change access privileges, automate operations, monitorresources, and schedule jobs. You may have used TME 10™ environment inthe past.

Tivoli NetView for OS/390Refers to Tivoli NetView for OS/390 versions 1.3 and 1.4 and also TivoliNetView for z/OS version 5.1.

V and RSpecifies the version and release.

VTAM® and TCP/IPVTAM and TCP/IP are included in the IBM Communications Serverelement of the OS/390 and z/OS operating systems. Refer to:

http://www.ibm.com/software/network/commserver/about/

Preface

viii IBM Tivoli Business Systems Manager: Getting Started

http://www.ibm.com/software/network/commserver/about/

Unless otherwise indicated, references to programs indicate the latest version andrelease of the programs. If only a version is indicated, the reference is to allreleases within that version.

When a reference is made about using a personal computer or workstation, anyprogrammable workstation can be used.

Operating-specific InformationFor more information about the hardware and software requirements for TivoliBusiness Systems Manager components, refer to IBM Tivoli Business SystemsManager: Installation and Configuration Guide.

Preface

Preface ix

x IBM Tivoli Business Systems Manager: Getting Started

Chapter 1. Overview

This chapter provides an overview of Tivoli Business Systems Manager andincludes:v “What Is Tivoli Business Systems Manager?”v “What Is a Business System?” on page 2v “Discovery Processing” on page 2v “Event Processing” on page 3v “Monitoring Options” on page 3v “Reporting System” on page 5v “Instrumentation” on page 5v “Problem and Change Support” on page 5

What Is Tivoli Business Systems Manager?Tivoli Business Systems Manager is an enterprise management product thatmonitors data processing resources that are critical to a business application. Itenables end-to-end monitoring of systems, subsystems, applications, and otherresources in your enterprise, from OS/390 and z/OS systems to distributedsystems. Tivoli Business Systems Manager provides your operations with a view ofthe system components as they relate to your overall business. Use Tivoli BusinessSystems Manager to:v Construct views for monitoring that reflect the current applications and business

systems within the enterprise, which can contain a complex mixture of systemresources across the entire enterprise

v Consolidate information scattered throughout the enterprisev Interact with customer applications, scheduling systems, and automation

systems to provide a single view of the overall status and health of systemresources

v Enable real-time monitoringv Support existing Tivoli Global Enterprise Manager instrumentation, Tivoli

Distributed Monitoring, and IBM Tivoli Enterprise Console®

v Manage business system components on a variety of platformsv Enable effective operation of your entire enterprise

After resources are defined to or discovered by Tivoli Business Systems Manager,they are registered with Tivoli Business Systems Manager and the information isstored in an SQL database. You can access the database using a GUI-based console.Tivoli Business Systems Manager monitors for state changes that occur in thevarious resources within your enterprise. An event management facility helps youdetermine and troubleshoot system problems that can affect the availability ofapplications and systems. By applying rules to events and data collected fromvarious sources, even when business systems span several platforms, TivoliBusiness Systems Manager enables you to graphically monitor and control theinterconnected business components and operating system resources.

1

What Is a Business System?A business system is a group of diverse but interdependent applications and othersystem resources that interact to accomplish specific business functions. A businesssystem can contain applications or other resources that run on a variety ofplatforms, including host, distributed, and network environments.

For example, a banking business system designed to support transactions over theWeb typically includes a Web server running outside the company’s intranet andconnected directly to the Internet and a firewall that provides secure connectivityto a machine running a custom business component, such as loan processing. Theloan processing business component usually runs on a distributed platform andinterfaces to business components running on a host computer. The host handlesall the bank transactions. This business system presents challenges to a systemmanager because it crosses the typically isolated environments of host anddistributed systems.

Another example of a business system is an e-mail system. E-mail business systemsinclude all the instances of e-mail business components that are being used in yournetwork. You might have a mix of Lotus Notes® servers and clients, POP mail orMicrosoft® Exchange servers and clients, and other e-mail business components.An e-mail business system includes definitions that tell whether each entity in thebusiness system is a server, a client, or both. It also includes definitions of themonitors that collect status information for each business component in thebusiness system, as well as definitions of the relationships between businesscomponents in the business system.

Tivoli Business Systems Manager allows you to use an automated approach forcreating business systems. Using commands provided in Tivoli Business SystemsManager results in faster implementation and completeness of the business views.When the configuration is completed, the automatically created business systemview continues to monitor the system for the creation of new resources andautomatically adds them to the view. Refer to IBM Tivoli Business Systems Manager:Administrator’s Guide for more information on automatically creating a businesssystem.

Discovery ProcessingTivoli Business Systems Manager monitors resources for state changes andperformance characteristics that indicate availability. However, before you canmonitor resources in your enterprise, the resources must be discovered andregistered in the Tivoli Business Systems Manager database. The resource discoveryand registration process varies depending on the data source. The process forresources monitored by OS/390 involves running batch jobs that detect theconfiguration of your resources and update the database. Resources discoveredthrough the Tivoli Enterprise Console require that the classes first be defined in theTivoli Business Systems Manager database. The resources are then createddynamically as events are received from the Tivoli Enterprise Console. Resourcesdiscovered through the common listener interface are dynamically populatedthrough bulk and delta discovery transactions.

Tivoli Business Systems Manager has three discovery processes for OS/390:v Prediscovery: Batch jobs are run initially when, or before, Tivoli Business

Systems Manager is installed and configured.

2 IBM Tivoli Business Systems Manager: Getting Started

v Rediscovery: Batch jobs can be customized and can be run on a scheduled basisto gather updated information about resources on your enterprise.

v Autodiscovery: Programs automatically detect updates, resulting in updates tothe database.

The identification or discovery process uses various data sources to initiallypopulate resources in the Tivoli Business Systems Manager database. The OS/390process involves a series of batch functions that create a sequential file, which isthen forwarded to the Tivoli Business Systems Manager servers. The data is thenprocessed and stored in the Tivoli Business Systems Manager database. Thediscovered resources are imported into Tivoli Business Systems Manager in aprocess called resource registration.

Tivoli Business Systems Manager has two methods for discovering distributedresources. Rules can be added to the Tivoli Enterprise Console that forward eventsto Tivoli Business Systems Manager database. The first event from a resourcetriggers the creation of the resource in the Tivoli Business Systems Managerdatabase. The common listener transport provides bulk and delta transactions.Bulk transactions are a snap shot of the instrumented environment. Bulktransactions identifies which resources exist, resources that have changed since thelast bulk transaction, the associations between resources, and resources that nolonger exist since the last bulk transaction. The Tivoli Business Systems Managerdatabase is populated with the information in the bulk transaction. The deltatransaction keeps the Tivoli Business Systems Manager database up to date as newresources are discovered.

Event ProcessingTivoli Business Systems Manager consolidates events from a wide range of IBMand independent system vendor products. Event processing involves capturingspecific events and routing them to the Tivoli Business Systems Manager server.The events result in updates to the Tivoli Business Systems Manager database,which are then displayed on the Tivoli Business Systems Manager console. Eventscan also result in the discovery of resources.

Tivoli Business Systems Manager has two event types:v Messagesv Exceptions

Monitoring OptionsTivoli Business Systems Manager enables you to manage resources in a way thatbest reflects your current organization. Your Tivoli Business Systems Managerimplementation can reflect a decentralized or a centralized control structure. Theresources can either be defined to Tivoli Business Systems Manager or bediscovered using various methods (for example, components, modules, programs)to detect the configuration of the resources. Once the resources are defined ordiscovered, they are registered in the Tivoli Business Systems Manager database;that is, information about the resources is stored in the database and is availablefor monitoring and viewing.

The Tivoli Business Systems Manager console and the Tivoli Business SystemsManager Web console display the resources in your enterprise in various views.When notifications that trigger alerts are received from the various collectionagents within the enterprise, the alerts are displayed as graphic overlays on theresources, indicating the different status of your resources.

Chapter 1. Overview 3

A resource view displays all the resources registered in the Tivoli Business SystemsManager database. Business system views can be created from the console orautomatically from incoming discovery and event data. A business system view isa logical view that includes any subset of the registered resources that are ofinterest for monitoring. Each resource is represented as an icon within the view.You can create, save, and later access business system views. Opening severalwindows, each containing a different business system view, enables you to monitordifferent resources and their various relationships from a single workstation.Business system views can be based on an actual business system as well as on:v An application or set of applicationsv A departmentv A vertical area of responsibilityv A geographical region

Examples of business system views are:v Property & Casualty (business system)v Health Claims, Policy Easy-Access, Order Entry, Help Desk (applications)v Human Resources (department)v DASD Management (vertical area of responsibility)v Far East Operations (geographical region)

Business system views enable you to logically organize the resources that you wantto monitor. For example, to monitor a company’s health claim processing system,you might construct a business system view as follows:1. Identify the various applications, resources, and subsystems that make up the

health claim processing system.2. Verify that the items are registered resources within Tivoli Business Systems

Manager.3. Create a new business system view called “Health Claims”.4. Populate the newly-created business system view with the identified resources.

Resources in the resource and business system views can be displayed using thesemethods:v Tree view, which shows the hierarchy of the resources. Branches in the tree can

be expanded or collapsed to show or hide resources.v Hyperview, which graphically shows a large number of resources at one time.v Table view, which shows resources in a table format. Information for any column

can be sorted and filtered.v Business impact views, which are displayed as hyperviews, show resources that

are shared across several business systems.v Topology views, which show the relationships between the resources by

displaying the links between the resources as well as the resources.

Property sheets for each of the resources enable viewing and updating of:v Attributes, such as the resource name and current statusv Alert information, such as currently posted events and notesv Thresholds for propagation and filteringv Scheduling information


The Web console enables quick access for checking critical resources and providesvarious ways for viewing resources and events.

Reporting SystemTivoli Business Systems Manager provides a reporting system for generatingreports from real time and historical availability data that Tivoli Business SystemsManager collects from the resources in your enterprise. The reporting systemprovides report forms for viewing the data you need to analyze problems and toanticipate and avoid future problems. You can also use the generated reports fortrend analysis and capacity planning.

InstrumentationInstrumentation provides information about specific applications, system software,or business components to Tivoli Business Systems Manager. You can addinstrumentation to components of a business system or to standalone applications.Tivoli Business Systems Manager supports the following mechanisms forintegrating third-party software:v Tivoli Business Systems Manager source/390 object pumpv Tivoli Business Systems Manager common listener architecturev Tivoli Business Systems Manager Intelligent Monitoring infrastructurev Tivoli Enterprise Console and the standard adapters that provided with Tivoli

Enterprise Consolev Tivoli Ready and Tivoli Manager productsv Tivoli Application Management Specification

Problem and Change SupportTivoli Business Systems Manager provides Problem Ticket, Change Request andAutomatic Ticketing program user exits that can be used for integration to acustomer’s Problem Management or Change Management product. Completedocumentation, configuration and sample integrations may be found on thesupport Web site http://www-1.ibm.com/support.

Note: If you are upgrading from V1.5 to V2.1, it is critical that you review theinformation on new features in the Program User Exits Guide and CodeSamples documentation located on the Web sitehttp://www.ibm.com/software/sysmgmt/products/support/. Under SelfHelp select Solutions then select Program User Exits Guide and CodeSamples. Some changes have been made that might require you to modifyyour request processor that is invoked from within Tivoli Business SystemsManager and integrated to your Problem or Change product. Additionally,there are new features available in V2.1 that you might want to incorporateas well.

IT departments commonly use a problem information system to document andtrack issues that pertain to the resources they manage. Typically the databaserecord used to manage these issues is called a problem ticket. The standardworkflow of a problem would be to create a problem ticket and assign it to ahuman resource for resolution. The ticket is closed when the problem is resolved.Tivoli Business Systems Manager now provides an automated process to createproblem tickets when key events occur by defining event-filtering rules. For more

Chapter 1. Overview 5

http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliBusinessSystemsManager.html

http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliBusinessSystemsManager.html

information about the automated problem ticket process, refer to IBM TivoliBusiness Systems Manager: Administrator’s Guide.


Chapter 2. Tivoli Business Systems Manager Components

This chapter describes the Tivoli Business Systems Manager components. Itincludes descriptions of:v “Components for Handling OS/390 Data”v “Components for Handling Distributed Data” on page 9v “Base Services and Components” on page 10

Components for Handling OS/390 DataThe Tivoli Business Systems Manager source/390 is a set of programs orcomponents that enable monitoring and management of MVS and OS/390-basedsystems. Source/390 resides on the OS/390 system and consists of the following:v The source/390 object pump, which collects data and traps events for monitored

resources. It captures data from a variety of sources including the MVS systemconsole, performance monitors, subsystems, CICS® regions, and otherapplications and resources. Upon detecting an event, the source/390 objectpump formats a message according to a defined specification and forwards theformatted message to the source/390 object server.

v The source/390 object server, which manages the communication between theOS/390–based components and the Tivoli Business Systems ManagerWindows-based servers. It passes the data gathered by the source/390 objectpump to the servers and logs any activity.

v The source/390 dataspace, which facilitates communication between thesource/390 object pump and the source/390 object server. It provides anintermediate queue area used for passing data between the source/390 objectpump and the source/390 object server.

v Tivoli Business Systems Manager uses an External Data Interface (EDI) tointegrate automation products (System Automation for OS/390, OPS/MVS, AFOperator, and Auto Operator). State changes, messages, and exceptions (forobjects) that reside on the same MVS operating systems are passed through theEDI to Tivoli Business Systems Manager.In addition to passing state changes, messages, and exceptions, EDI enables youto pass data from other supported data sources (for example, DB2, CICSPlex,IMS™). You can also send automation starting and automation ending messagesto indicate, respectively, automation is in progress and automation hascompleted for resources managed by Tivoli Business Systems Manager.Refer to IBM Tivoli Business Systems Manager: Installation and Configuration Guidefor additional information about using the EDI.

Event and performance data collected by the source/390 object pump is placed inthe source/390 dataspace. The source/390 object server then picks up the data andpasses it to the Windows-based servers for subsequent processing and storing inthe Tivoli Business Systems Manager database. Figure 1 on page 8 shows how datais passed through the source/390 components to the Windows-based servers andinto the Tivoli Business Systems Manager database.

7

Note: In Figure 1, DB2 indicates DB2 and DB2 Performance Monitor, MAINVIEWindicates MAINVIEW for CICS, DB2, IMS and OS/390, and TMON indicatesASG-TMON for CICS, DB2 and MVS.

MVS ConsoleMessages and

Commands

IBM TivoliBusiness SystemsManager Servers

IBM TivoliBusiness SystemsManager Database

Source/390Object Pump

IBM Tivoli Business Systems ManagerSource/390

OS/390

Windows NT or Windows 2000

WebSpherefor OS/390

Source/390 Dataspace

CICSTransient Data

Tivoli OperationsPlanning and Control

Tivoli WorkloadScheduler

ResourceManagement

Facility

System Automationfor OS/390 V1R3

CICSPlexSystem Manager

for OS/390

MAINVIEWAutoOPERATOR

for OS/390

SMS

XRC

CA-7

CONTROL-M

CA-OPS/MVS

AF/OPERATOR

DB2

ASG-Zeke

OMEGAMON

DFSMShsm

ExternalData

Interface

AutomationExternal

DataInterface

Program-to-ProgramInterface

Source/390 Object Server

CICSPlex

IMS

MAINVIEW

TMON

Tivoli NetView forOS/390 and z/OS

System Automationfor OS/390 V2R1

Figure 1. The source/390 program


Components for Handling Distributed DataDistributed components, which are installed in a Tivoli management region, areshown in Figure 2:

Event enablement, which is installed on the Tivoli Enterprise Console event server,integrates with Tivoli Management Framework, Tivoli Enterprise Console, andTivoli Distributed Monitoring to enable availability and performance managementof distributed resources. Any resource whose status can be communicated using aTivoli Enterprise Console event can be integrated with Tivoli Business SystemsManager. Event enablement also defines event classes and rules for handlingevents related to Tivoli Business Systems Manager.

Sources of data for distributed resources are:

IBM TivoliBusiness Systems

Manager Source/390

IBM TivoliBusiness SystemsManager Servers

TivoliManagementFramework


ManagerTask Server


Manager EventEnablement

Tivoli: DistributedMonitoring Advanced

Edition

TivoliEnterpriseConsole

IBM TivoliBusiness SystemsManager Database

OS/390

Windows NT or Windows 2000

Tivoli Management Region

APMInstrumentation

TivoliDistributed

Monitoring Profiles

TivoliEnterprise Console

Events

Tivoli Managerfor Products

Tivoli NetView

AppManagerSuite

Unicenter TNG

TivoliWorkloadScheduler

PATROL

Figure 2. Tivoli Business Systems Manager Distributed components

Chapter 2. Tivoli Business Systems Manager Components 9

v The Application Policy Management (APM) event architecture, which is theevent flow architecture of Tivoli Global Enterprise Manager and uses theApplication Management Interface (AMI) instrumentation source from across theenterprise

v The Tivoli Distributed Monitoring event architecturev Events created using the Tivoli Business Systems Manager Tivoli Enterprise

Console rule engine program interfacev Applications instrumented using the common listener architecture

The task server interacts with the Tivoli Management Framework and the TivoliNetView for OS/390 environments. Command requests from an operator arerouted to the task server, which routes the requests to the appropriateenvironment. Responses are returned to the task server where they are correlatedwith the request and routed back to the requesting operator.

Base Services and ComponentsThe Tivoli Business Systems Manager Windows-based components include:v “Servers”v “Consoles” on page 11v “Health Monitor” on page 11

For information on hardware and software requirements for Tivoli BusinessSystems Manager, refer to IBM Tivoli Business Systems Manager: Installation andConfiguration Guide.

ServersThe Tivoli Business Systems Manager servers process the availability data that iscollected from various sources. Availability data is placed in the Tivoli BusinessSystems Manager database, where intelligent agents provide alerts on monitoredresources and broadcast the alerts to the Tivoli Business Systems Manager console.The servers also handle user requests from the console.

Some of the services provided within the Tivoli Business Systems Managermanagement server are:

Database serverProvides for database for the Tivoli Business Systems Manager data andcollects data from the Tivoli Enterprise Console event source in thedistributed environment.

History serverMaintains a history of events collected by Tivoli Business Systems Managerand replicates the Tivoli Business Systems Manager database.

Application serverHandles requests for the console-based Tivoli Business Systems Managerclients.

Propagation serverProcesses events and calculates propagation actions.

Event handler serverReceives data from and sends commands to OS/390.


SNA serverEnables Windows-based applications to communicate with OS/390-basedapplications.

Web console application serverHandles requests for the Web-based Tivoli Business Systems Managerclients. This is a new server component for Tivoli Business SystemsManager 2.1 and is only required if you are using Web clients.

ConsolesThe Tivoli Business Systems Manager console and the Tivoli Business SystemsManager Web console provide various views for monitoring the resources in yourenterprise. For example, consoles are typically used for performing administrativeand operator tasks. Web consoles are typically used for view sessions of resources.See “Monitoring Options” on page 3 for more information.

Health MonitorThe Tivoli Business Systems Manager health monitor monitors the health andavailability of Tivoli Business Systems Manager and the various servers on whichthe application is installed.

Chapter 2. Tivoli Business Systems Manager Components 11

Chapter 3. Data Sources

Tivoli Business Systems Manager integrates with and collects data from numeroussoftware products to provide monitoring of:v “Distributed Resources”v “MVS” on page 14v “Storage Management Resources” on page 15v “CICS Subsystems” on page 17v “DB2 Subsystems” on page 18v “IMS Subsystems” on page 19v “Job Schedulers” on page 20v “Automation Products” on page 22v “IBM WebSphere Application Server for z/OS and OS/390” on page 23

Distributed ResourcesTivoli Business Systems Manager distributed components successfully integrate themanagement of distributed data sources into the business system and life cycleapproach to availability management.

Tivoli Business Systems Manager integrates with the following distributed datasource products:v Intelligent Monitoring for BMC PATROLv Intelligent Monitoring for NetIQ AppManagerv Intelligent Monitoring for Unicenter TNGv IBM Tivoli Monitoring Classic and Advanced Editionsv IBM Tivoli Monitoring for Applications - mySAP.comv IBM Tivoli Monitoring for Applications - Siebelv IBM Tivoli Monitoring for Business Integration - WebSphere® MQv IBM Tivoli Monitoring for Business Integration - WebSphere MQIv IBM Tivoli Monitoring for Databases - Oraclev IBM Tivoli Monitoring for Databases - DB2v IBM Tivoli Monitoring for Databases - Informix®

v IBM Tivoli Monitoring for Infrastructure - Apachev IBM Tivoli Monitoring for Infrastructure - WebSphere Application Serverv IBM Tivoli Monitoring for Infrastructure - iPlanetv IBM Tivoli Monitoring for Infrastructure — IISv IBM Tivoli Monitoring for Messaging and Collaboration - Domino™

v IBM Tivoli Manager products, for example MQSeries®

v IBM Tivoli NetView

13

MVSMonitoring of MVS is provided by collecting data from the MVS console(described in “MVS Console”) and from one or more of the following:v “Resource Management Facility”v “Tivoli NetView for OS/390”v “MAINVIEW for OS/390” on page 15v “OMEGAMON for MVS” on page 15v “ASG-TMON for MVS” on page 15

MVS ConsoleTivoli Business Systems Manager collects start, stop, or abend information from theMVS console for registered resources, which can be started tasks, batch jobs, CICSregions, DB2, and IMS.

Resource Management FacilityIBM Resource Management Facility (RMF™) provides a wide breadth of data aboutthe status of almost any resource within the MVS environment. RMF issues systemperformance reports that you can use to:v Determine if your system is running smoothlyv Detect system bottlenecks caused by contention for resourcesv Evaluate the service your installation provides to different groups of usersv Identify workload delays and the reasons for the delaysv Monitor system failures, system stalls, and failures of selected applications

RMF monitors collected data about system workload and resource utilization. Thisdata addresses all hardware and software components of your system, includingprocessor, I/O device, and storage activities and utilization; resource usage; andactivity and performance of groups of address spaces. Data is gathered for aspecific cycle time, and consolidated data records are written at specified intervals.

RMF has three monitors. Monitor I provides long-term data collection for systemworkload and resource utilization. The Monitor I session is continuous, andmeasures various areas of system activity over a long period of time. Monitor II isan online snapshot session that generates a requested report from a single datasample. Monitor III provides short-term data collection and online reports forcontinuous monitoring of system workflow and delays.

Tivoli Business Systems Manager uses RMF data and automated thresholds tomonitor OS/390 resources and services. Through the source/390 program, TivoliBusiness Systems Manager integrates with RMF monitors to generate exceptionswhen RMF collects metrics that exceed customer-supplied thresholds. Source/390processes a subset of the RMF Monitor III metrics such as activity, utilization,workflow, and delay counters. RMF exceptions are captured and posted to theTivoli Business Systems Manager database and appear as alerts related to theoperating system.

Tivoli NetView for OS/390The Systems Network Architecture (SNA) provides a centralized networkmanagement system for subarea and Advanced Peer-to-Peer Networking®

(APPN®) networks. The Tivoli NetView for OS/390 SNA topology manager gathers


subarea and APPN status and topology information and uses the Tivoli NetViewfor OS/390 Resource Object Data Manager (RODM) as a data cache to locate andmanage SNA topology data.

The integration of Tivoli Business Systems Manager with RODM involvescapturing events and messages for the SNA/APPN resources and updating theTivoli Business Systems Manager database with availability information.

MAINVIEW for OS/390BMC Software MAINVIEW for OS/390 monitors the performance of OS/390.MAINVIEW for OS/390 provides samplers that monitor OS/390 performanceindicators. Each sampler monitors a single indicator, such as the processor usage ofa job. When you invoke a sampler, you can define a threshold value for itsindicator. If the indicator exceeds the threshold value, then the sampler issues awarning message.

Integrating MAINVIEW for OS/390 with Tivoli Business Systems Managerinvolves capturing these sampler warning messages, translating the warningmessages into events understood by Tivoli Business Systems Manager, and passingthem to Tivoli Business Systems Manager.

OMEGAMON for MVSCandle OMEGAMON for MVS is an MVS interactive performance monitoringsystem. Exception conditions are reported in Tivoli Business Systems Manager.

Integrating OMEGAMON for MVS involves Tivoli Business Systems Managersource/390 collecting and monitoring exceptions, thresholds, tape waits, and otherdata available from OMEGAMON for MVS.

ASG-TMON for MVSASG-TMON for MVS monitors MVS performance in real time, provides access tohistorical data online for analysis, and offers facilities for summarizing andarchiving MVS performance data for historical reporting. ASG-TMON for MVSalso includes flexible exception processing and productivity-enhancing system andprogrammer utilities.

Integrating ASG-TMON for MVS with Tivoli Business Systems Manager involvescapturing ASG-TMON for MVS exception messages, translating the exceptionmessages into events understood by Tivoli Business Systems Manager, and passingthe events to Tivoli Business Systems Manager.

Storage Management ResourcesMonitoring of storage management resources is provided through integration with:v “System-Managed Storage”v “Data Facility Systems Managed Storage Hierarchical Storage Manager” on

page 16v “Extended Remote Copy” on page 16

System-Managed StorageStorage environments have become increasingly complex as data centers haveexpanded to support numerous systems and platforms. Although storage

Chapter 3. Data Sources 15

management tasks vary with the platforms and storage system types supported,operating a storage system generally requires storage administrators to manage thefollowing:v Hardware components of various models and capabilities, which must match the

requirements of the data transferred and storedv Software utilities for moving, copying, retrieving, and archiving datav Procedures for controlling the use of storage resources

Using a system-managed storage approach changes storage management from amanual process implemented by both end users and storage administrators to anautomated process controlled by storage administrators. Although system-managedstorage improves storage control and utilization and enables service levelmanagement, it does not provide the real-time data needed to effectively managelarge and complex storage environments.

Tivoli Business Systems Manager integrates with DFSMS (Data Facility SystemsManaged Storage) as an event source to discover and monitor storage group andvolume events along with hardware storage subsystems and MVS device events.Tivoli Business Systems Manager reports system-managed storage exceptions thatare based on a pre-defined workflow and provides real-time viewing of data setinformation that is contained in volume table of contents (VTOC) entries andcatalogs. This integration provides an end-to-end view of how storage is affectingapplications and other system components including the operating system, OLTP(on-line transaction processing), and batch processing.

Data Facility Systems Managed Storage Hierarchical StorageManager

DFSMShsm™ (Data Facility Systems Managed Storage Hierarchical StorageManager) is a storage management and productivity tool for managing low activityand inactive data. It improves DASD use by automatically managing both spaceand data availability in a storage hierarchy. DFSMShsm handles data set archiving,backup, and recovery, and manages available space on DASD volumes. Spacemanagement involves moving low-activity data sets from user-accessible volumesto DFSMShsm volumes and reducing the space occupied by data on bothuser-accessible and DFSMShsm volumes.

The integration of DFSMShsm with Tivoli Business Systems Manager involvesreporting DFSMShsm exceptions that are based on a predefined workflow ofmessages that define DFSMShsm events. This integration provides an end-to-endview of how DFSMShsm processes affect applications and other systemcomponents, including the operating system, OLTP (on-line transaction processing),and batch processing.

Extended Remote CopyExtended remote copy (XRC) is a storage-based disaster recovery and workloadmigration solution that can copy data in real time to a remote location. XRC is anextended function on all newer IBM storage controllers and operates in conjunctionwith appropriate levels of DFSMS/MVS®. It enables complete recovery of the datatransactions that occurred between the most recent backup and the time when anapplication system failed.

Tivoli Business Systems Manager integrates with XRC as a source of events formonitoring and controlling XRC resources. Tivoli Business Systems Manager


reports XRC events based on a predefined workflow of OS/390 messages andqueries the system data mover address space for information on established XRCsession and volume pairs.

CICS SubsystemsMonitoring of CICS subsystems is provided through integration with:v “CICSPlex System Manager for OS/390”v “MAINVIEW for CICS”v “OMEGAMON for CICS” on page 18v “ASG-TMON for CICS” on page 18

CICSPlex System Manager for OS/390A CICSPlex (a CICS complex) is an environment in which two or more CICSregions are linked through CICS intercommunication facilities.

IBM CICSPlex System Manager for OS/390 is a subsystem monitor that automatesthe operations of CICS systems. It reduces the complexity and simplifies themanagement of complex collections of CICS systems by presenting them as anintegrated whole. It manages CICS systems under various operating systems andprovides resource management, workload management, and resource monitoring.It enables you to manage by exception processing by automatically warning you ofdeviations from intended performance and workload management.

Tivoli Business Systems Manager supports CICSPlex System Manager for OS/390by using it as a source for CICS monitoring and discovery. A CICSPlex system andits resources can be discovered from the Tivoli Business Systems Manager clientconsole. Once the system has been discovered, it can be constantly monitored forchanges in topology and for events. CICSPlex System Manager passes events toTivoli Business Systems Manager through Tivoli NetView for OS/390. These eventsare captured and posted in the Tivoli Business Systems Manager database andappear as events related to specific resources on the Tivoli Business SystemsManager console.

The following list of resources are discovery and monitored by Tivoli BusinessSystems Manager:v CICS regionsv CMAS regionsv Transactionsv Filesv CICS-CICS connectionsv CICS system groupsv DB2 connectionsv CORBA serversv CICS-deployed jar files

In addition to the discovery and monitoring capability provided by Tivoli BusinessSystems Manager, a user may launch in context from any resource to the CICSPlexSystem Manager WUI (web user interface). This enables to the users access andcontrol information from CICSPlex System Manager.

MAINVIEW for CICSBMC Software MAINVIEW for CICS provides monitors that regularly collect dataabout conditions in a CICS region. Each monitor collects data for a different


performance statistic, such as average response time. When you start a monitor,you can define a warning threshold value for the statistic. If the statistic exceedsthe threshold, the monitor issues a warning message. Later, if the statistic dropsbelow the threshold, the service issues a matching resolution message.

Integration with Tivoli Business Systems Manager involves capturing thesewarning and resolution messages, translating them into events formatted for TivoliBusiness Systems Manager, and passing them to Tivoli Business Systems Manager.

Note: CICS regional discovery data is not provided by MAINVIEW for CICS.

OMEGAMON for CICSCandle OMEGAMON for CICS is a CICS performance monitoring system. TivoliBusiness Systems Manager source/390 collects data from OMEGAMON for CICS.Exceptions are collected by Tivoli Business Systems Manager. In addition, data iscollected to provide CICS file availability for a registered CICS region.

Note: CICS regional discovery data is not provided by OMEGAMON for CICS.

ASG-TMON for CICSASG- TMON for CICS is a CICS performance monitoring system. Alert messagesissued by ASG-TMON for CICS are translated into exception events for therelevant CICS resources in Tivoli Business Systems Manager.

Integrating ASG-TMON for CICS with Tivoli Business Systems Manager involvescapturing ASG-TMON for CICS SmartTarget alert messages, translating the alertmessages into events formatted for Tivoli Business Systems Manager, and passingthe events to Tivoli Business Systems Manager.

Note: CICS regional discovery data is not provided by ASG-TMON for CICS.

DB2 SubsystemsMonitoring of DB2 subsystems is provided through integration with:v “Monitoring of Subsystems Running DB2 Universal Database”v “MAINVIEW for DB2” on page 19v “OMEGAMON for DB2” on page 19v “ASG-TMON for DB2” on page 19

Monitoring of Subsystems Running DB2 Universal DatabaseThe DB2 Universal Database™ for z/OS and OS/390 provides comprehensivedatabase functionality including high performance, scalability, network and dataintegration, reliability, and availability. The DB2 Performance Monitor (DB2 PM) isa tool for analyzing and tuning the performance of DB2 subsystems andDB2-based applications. DB2 PM can be used to determine overall performance ofa DB2 subsystem or to identify potential performance problems on an individualthread basis.

Tivoli Business Systems Manager integrates with DB2 Universal Database for z/OSand OS/390 and DB2 PM by capturing warning and resolution messages,translating them into events formatted for Tivoli Business Systems Manager, andpassing them to Tivoli Business Systems Manager. Exceptions within DB2 PM can


be further managed by establishing threshold settings. This integration provides anend-to-end view of how DB2 is affecting applications and other systemcomponents.

MAINVIEW for DB2BMC Software MAINVIEW for DB2 provides monitors that regularly collect dataabout DB2 for OS/390 performance indicators. Each monitor collects data for asingle performance indicator, such as percentage of buffer pool usage. When youstart a monitor, you can define a warning threshold value for the indicator. If theindicator exceeds the threshold, the monitor issues a warning message. Later, if theindicator drops below the threshold, the service issues a matching resolutionmessage.


OMEGAMON for DB2Candle OMEGAMON for DB2 is a performance and availability monitor formonitoring the performance of DB2 Universal Database for z/OS and OS/390.OMEGAMON for DB2 provides an at-a-glance view of DB2 performance. The clearstatus orientation alerts you to potential problems immediately, so you can takeaction to protect DB2 system and application availability.

ASG-TMON for DB2ASG- TMON for DB2 is a performance monitoring system for DB2 UniversalDatabase for z/OS and OS/390. Integrating ASG-TMON for DB2 with TivoliBusiness Systems Manager involves capturing ASG-TMON for DB2 defaultexceptions, translating these exceptions into events formatted for Tivoli BusinessSystems Manager, and passing the events to Tivoli Business Systems Manager.

Note: Only the default exceptions supplied with ASG-TMON for DB2 arecaptured; site-specific exceptions that you have defined are not captured.

IMS SubsystemsMonitoring of IMS subsystems is provided through either IMS monitoring suppliedby Tivoli Business Systems Manager (see “IMS Monitoring”) or through integrationwith:v “MAINVIEW for IMS” on page 20v “OMEGAMON for IMS” on page 20

IMS MonitoringIMS is a transactional and hierarchical database management system that provideshigh availability, performance, capacity, and integrity for critical on-line operationalapplications and data.

Tivoli Business Systems Manager IMS enables the enterprise to monitor IMSsystems. The resources within IMS are discovered dynamically by Tivoli BusinessSystems Manager. IMS discovery requests can also be initiated for IMS subsystemsfrom the Tivoli Business Systems Manager client console. Once an IMS system hasbeen discovered, it is constantly monitored for changes in topology and for events.


The following list of resources are discovered and monitored by Tivoli BusinessSystems Manager:v IMS Control Regions (DBCTL, DCCTL, and TM/DB)v IMS Primary and Secondary MTOv IMS Logs and WADSv IMS Message Processing Regionsv IMS Fast Path Regionsv IMS Batch Message Processing Regionsv IMS Batch Message Processing Programsv IMS Message Processing Programsv IMS Transactionsv IMS Databases, Fast Path DEDBs and AREAs, HALDB Partitionsv DB2 connectionsv MQ connectionsv IMS Connect Regionsv IMS Fast Database Recovery (FDR) Regionsv Common Queue Server (CQS) Regionsv Internal Resource Lock Manager (IRLM) Regions

Integrating IMS with Tivoli Business Systems Manager involves using TivoliNetView for OS/390 to capture a set of IMS system console messages, IMScommands, and exceptions. These are translated into events understood by IBMTivoli Business Systems and passed to Tivoli Business Systems Manager. Theseevents are posted in the Tivoli Business Systems Manager database and appear asevents related to specific resources on the Tivoli Business Systems Managerconsole. IMS exceptions are further managed by processes that run at predefinedintervals to check the status of IMS resources. This integration provides anend-to-end view of how IMS is affecting applications and other systemcomponents.

MAINVIEW for IMSBMC Software MAINVIEW for IMS provides monitors that regularly collect dataabout IMS performance indicators. Each monitor collects data for a single indicator,such as the length of the IMS transaction input queue. When you start a monitor,you can define a warning threshold value for the indicator. If the indicator exceedsthe threshold, the monitor issues a warning message. Later, if the indicator dropsbelow the threshold, the service issues a matching resolution message.


Note: Tivoli Business Systems Manager for IMS is a prerequisite for this function.

OMEGAMON for IMSCandle OMEGAMON for IMS is an interactive performance monitoring system.Exception conditions are reported in Tivoli Business Systems Manager.

Job SchedulersTivoli Business Systems Manager provides monitoring of job schedulers in theenterprise through integration with:v “Tivoli Operation Planning and Control” on page 21v “Tivoli Workload Scheduler” on page 21


v “CA-7”v “CONTROL-M for OS/390”v “ASG-Zeke” on page 22

Tivoli Operation Planning and ControlTivoli Operations Planning and Control (Tivoli OPC) provides a comprehensive setof services for managing and automating the workload for the OS/390 platformfrom a single point of control. Through the creation of plans, applications,calendars, and special resources, production work loads can be scheduled to runautomatically, taking into consideration dependencies, calendar issues such asweekends or holidays, and special processing requirements.

The integration of Tivoli OPC with Tivoli Business Systems Manager enables youto manage strategic applications from a business systems perspective. TivoliBusiness Systems Manager receives events directly from Tivoli OPC regarding jobstatus changes as well as alert conditions. Tivoli OPC also sends events that signaljob additions.

Tivoli Workload SchedulerTivoli Workload Scheduler is a suite of programs that can:v Help you plan and organize phases of workload productionv Manage the production environment and automate most operator activitiesv Prepare jobs for execution, resolve interdependencies, and launch and track jobsv Minimize idle time and improve throughputv Help increase system control, ease of use, and production capacityv Help reduce the need for workload management skills at remote locationsv Help with unattended operations

The integration of Tivoli Workload Scheduler with Tivoli Business SystemsManager enables the monitoring of key batch jobs, including start and stop timetracking, and deadline prediction.

CA-7Computer Associates CA-7 is an OS/390-based scheduling and workloadmanagement system. Applications and jobs are defined, scheduled, and submittedby CA-7 and are tracked by SMF and JES exits and internal CA-7 code. Messagesassociated with the tracking that indicate milestones (start, stop, or normalcompletion) and problems (late start, excessive run time, or abnormal ends) arealso written to a master station that is most commonly defined as a browsedataset.

The integration of CA-7 with Tivoli Business Systems Manager provides bothdiscovery data and event data. Job discovery information is provided by a forecastreport, generated at a client-defined interval, that is transported to Tivoli BusinessSystems Manager for processing. Event data is captured by the Tivoli BusinessSystems Manager external data interface using a CA-7 defined exit.

CONTROL-M for OS/390BMC Software CONTROL-M for OS/390 is an automated production control andscheduling system. It manages and automates the setup, scheduling, and executionof jobs within an enterprise. It performs almost all of the job handling tasks ofcomputer operators and provides continual data and status information about the


jobs being processed. It also provides a user interface for controlling theproduction management process when necessary.

CONTROL-M will integrate with Tivoli Business Systems Manager by providingboth discovery and event data. Discovery data and events are provided to thesource/390 object pump through CONTROL-M exits.

ASG-ZekeAllen Systems Group ASG-Zeke is an automated scheduling and dispatchingsystem that monitors time and performs real-time scheduling for MVS systems. Itautomates the production control process by scheduling and dispatching events.Events are defined as a batch job, a message to the console, a system command, anASG-Zeke command, a VM command, or a work center function.

The integration of Tivoli Business Systems Manager with ASG-Zeke involves bothdiscovery and event data. Discovery data is provided through a customized planlisting report. Events and messages are provided to the source/390 object pump bytrapping ASG-Zeke messages.

Automation ProductsTivoli Business Systems Manager currently integrates with the followingautomation products:v “System Automation for OS/390”v “CA-OPS/MVS”v “AF/OPERATOR”v “MAINVIEW AutoOPERATOR for OS/390” on page 23

System Automation for OS/390System Automation for OS/390, a Tivoli NetView for OS/390-based application,provides monitoring of all enterprise assets, as well as timely information aboutthe operational status of those assets.

Tivoli Business Systems Manager integrates with System Automation for OS/390 toenable you to intercept the message and exception information generated bySystem Automation for OS/390.

CA-OPS/MVSComputer Associates CA-OPS/MVS is an automated systems operations productthat facilitates monitoring of the enterprise and provides information about thestatus or condition of enterprise components. Tivoli Business Systems Managerexploits the use of messages and exceptions generated through CA-OPS/MVS,graphically representing their impact on the respective registered resource.

AF/OPERATORCandle AF/OPERATOR is an enterprise systems management product thatprovides current information as to the status of monitored components of theenterprise. The status and information, in the form of messages and exceptions, areprocessed by Tivoli Business Systems Manager and their impact is recorded on thecomponent resource within the Tivoli Business Systems Manager representation ofthe enterprise.


MAINVIEW AutoOPERATOR for OS/390BMC Software MAINVIEW AutoOPERATOR for OS/390 monitors status andconditions of enterprise components. Tivoli Business Systems Manager exploits theuse of messages and exceptions generated by AutoOPERATOR, and graphicallypresents their impact on the enterprise.

IBM WebSphere Application Server for z/OS and OS/390The WebSphere software is a suite of secure and reliable software products thatenables you to bring your mission-critical applications directly to the Web.

The integration of IBM WebSphere Application Server for z/OS and OS/390 withTivoli Business Systems Manager enables the discovery of WebSphere for OS/390resources. Tivoli Business Systems Manager provides a resource view of IBMWebSphere Application Server for z/OS and OS/390 and covers resources that arerepresented as MVS address spaces.


Chapter 4. Implementation Overview

This chapter provides an overview of implementing Tivoli Business SystemsManager in an enterprise. For detailed information about implementation, refer toIBM Tivoli Business Systems Manager: Installation and Configuration Guide. Thefollowing illustration provides an overview of the workflow.

Discovery EnterpriseCustomization

SitePreparation

Installation ProductionDeployment

Data Collection

Data CollectionData elements are collected from a variety of sources. These sources include systemproducts (for example, DB2, SMF, OPC), specific information (for example, namingconventions), and defining enterprise-specific configuration components. The tasksto collect the data elements are performed at your location. Your Tivoli servicesrepresentative will assist with the determination of the data to be collected.

Site PreparationInstallation of hardware and software elements is required to support theimplementation and production operations. If you require assistance in preparingyour site for implementation, contact your Tivoli services representative.

DiscoveryThe implementation process represents your system and workload-relatedenterprise assets within Tivoli Business Systems Manager.

Discover OS/390 resources:1. Load data from SMF.2. Load data from OS/390 subsystems.3. Set up and verify threshold profiles for performance monitors.4. Load data from batch management applications.

Discover distributed resources:1. Define new classes for AMS-based components and for Tivoli Distributed

Monitoring profile integration.2. Define the business system filtering for AMS-based components.3. Set up instrumentations and Tivoli Distributed Monitoring profiles.4. Set up Tivoli Enterprise Console rules.5. Set up event enablement and the task server.6. Set up the heartbeat as the primary discovery mechanism.

The collected and prepared data elements are used by your Tivoli servicesrepresentative to perform the tasks required within this activity.

25

Enterprise CustomizationThe defaults provided with Tivoli Business Systems Manager may not meet theoperational needs at your location. This activity will utilize the attribute valuesgathered during data collection to customize functionality required by youroperations. Your Tivoli services representative will assist in defining this activity, aswell as with performing the actual customization.

Other considerations are as follows:1. Setting up the business system views in the Tivoli Business Systems Manager

console.2. Setting up the propagation priorities for the resources in the Tivoli Business

Systems Manager database.3. Setting up operator security.4. Creating any commands that are needed for specific resources.5. Establishing operating procedures.

InstallationYour Tivoli services representative will work with you to install and test allcomponents of the Tivoli Business Systems Manager solution.

Production DeploymentWhen Tivoli Business Systems Manager has been fully installed, full enterprisedeployment in a production environment must be planned for and achieved.Production deployment consists of rollout planning, acceptance testing, andhistorical tuning, and addresses the critical issues of disaster recovery anddeployment support for the Tivoli Business Systems Manager implementation.


Appendix A. Discovery and Resource Monitoring

This section describes the Discovery and Resource Monitoring functionalities byproducts.

DiscoveryBefore Tivoli Business Systems Manager can monitor enterprise-wide resources, theresource discovery process must be run. This process can be a manual process ofsubmitting discovery batch jobs from the mainframe or an automatic processdirectly from the graphical user interface (GUI). Resources also can be discoveredby events (exceptions, messages, etc.) issued by the products being monitored (forexample, CICSPlex, DB2, IMS, SMS, RODM) and by bulk discovery and deltadiscovery by products monitored through the common listener (Tivoli NetView,TNG, PATROL, Application Manager, TWS).

Bulk DiscoveryThis process consists of submitting discovery batch jobs on the OS/390 or z/OSmainframe. The discovery jobs run utilities to discover resources that are requiredto be monitored by Tivoli Business Systems Manager. The information required todiscover these resources is sent to the Tivoli Business Systems Manager SQLdatabase. Here, Load/Discover SQL Enterprise Manager jobs are run to discover orshow resources in the Tivoli Business Systems Manager GUI.

Distributed resources instrumented through the common listener provide bulkdiscovery, which discovers all the resource instances related to the instrumentedproduct. This information is sent to the SQL server where the resource database isupdated. The IBM Tivoli Monitoring For products provide scripts that scan theenvironment that they are managing and generate events to create resources in theSQL database.

Auto DiscoveryWith this process, resources are discovered or rediscovered automatically. The autodiscovery process can be accomplished directly from the Tivoli Business SystemsManager GUI. Currently, auto discovery is only supported for CICSPlex resources.Distributed resources instrumented through the common listener provide deltadiscovery. Delta discovery sends changes to the resource instances related to theinstrumented product to the SQL server. Changes can include resource attributechanges, resource deletion, and new resource creation. The IBM Tivoli MonitoringFor products provide scripts that monitor the environment for new resources andgenerate events to reflect these changes.

RediscoveryThe rediscovery process is similar to running the bulk discovery process exceptthat any changes to the resources are shown on the Tivoli Business SystemsManager GUI. For distributed data sources, auto discovery and rediscovery areessentially the same.

Discovery by EventThis process discovers resources based on events (states, messages, and exceptions)that are sent to Tivoli Business Systems Manager. If a resource is not discovered

27

during bulk discovery and an event is trapped for this resource, the resource isdiscovered and the trapped event is posted to the discovered resource.

Discovery FilteringThis process filters (including or excluding) resources that should or should not bemonitored by Tivoli Business Systems Manager.

Automatic Business System SupportThis process creates automatic Business Systems for Tivoli Business SystemsManager resources.

Supported Discovery Functionality by ProductThe following table shows the supported OS/390 monitors for the discoveryprocess.

Table 1. OS/390 Supported Monitors

IBM TivoliSource/390ObjectPumpConsole

CandleOMEGAMON IIfor MVS

ASG-TMON forMVS

BMC MAINVIEWMVS

IBMTivoliSMS

IBMTivoliHSM

IBMTivoliXRC

BulkDiscovery

No No No No Yes No Yes

AutoDiscovery

No No Yes Yes No No No

Rediscovery No No No No Yes No Yes

Discoveryby Event

No No Yes Yes No No No

DiscoveryFiltering

No No Event Event No No No

The following table shows the supported Subsystem monitors for CICS for thediscovery process.

Table 2. Subsystem Monitors (CICS)

IBM TivoliCPSM/Native

CandleOMEGAMON II forCICS

ASG-TMON forCICS

BMC MAINVIEWCICS

Bulk Discovery Yes No No No

Auto Discovery Files Yes Yes Yes Yes

Auto DiscoveryTransactions

Yes No No No

Auto Discovery Other Yes No No No

Rediscovery Yes No No No

Discovery by Event Yes Yes Yes Yes

Discovery Filtering Event Event Event Event

The following table shows the supported Subsystem monitors for DB2 and IMS forthe discovery process.


Table 3. Subsystem monitors (DB2 and IMS)

IBM TivoliDB2 PM /Native

CandleOMEGAMON IIfor DB2

ASG-TMONfor DB2

BMCMAINVIEWDB2

IBMTivoliNativeIMS

CandleOMEGAMONII for IMS

BMCMAINVIEWIMS

BulkDiscovery

Yes No No No Yes No No

AutoDiscovery


Rediscovery Yes No No No Yes No No

Discoveryby Event

Yes No Yes Yes Yes No Yes

DiscoveryFiltering

Event andRediscovery

No Event Event EventandRe-discovery

No Event

The following table shows the supported Subsystem monitors for WebSphere forthe discovery process.

Table 4. Subsystem Monitors (WebSphere)

Websphere OS/390

Bulk Discovery HTTP Server

Auto Discovery Yes, WebSphere

Rediscovery No

Discovery by Event Yes

Discovery Filtering No

Automatic Business System Support No

The following table shows the supported Job Schedulers for the discovery process.

Table 5. Job Schedulers

ComputerAssociates CA7

IBM OPC IBM TWS 8.1 BMC Control-M ASG-Zeke

Bulk Discovery Yes Yes Yes Yes Yes

Auto Discovery No No No Yes No

Rediscovery Yes Yes Yes Yes Yes

Discovery byEvent

Yes Yes Yes Yes Yes

DiscoveryFiltering

Yes Yes Yes Yes Yes

The following table shows the supported automation products for the discoveryprocess.

Appendix A. Discovery and Resource Monitoring 29

Table 6. Automation Products

IBM NetviewOS/390 w/RODM

IBM SA OS/390 ComputerAssociatesOPS/MVS

CandleAF/Operator

BMC AutoOperator

Bulk Discovery SNA/GMFHS Yes No No No

Auto Discovery No No No No No

Rediscovery SNA/GMFHS SA V2.1 No No No

Discovery byEvent

No No Yes Yes Yes

DiscoveryFiltering

No No No No No

The following table shows the supported monitors for distributed sources for thediscovery process.

Table 7. Distributed Sources Supported Monitors

Tivoli EnterpriseConsoleResources

IBM TivoliNetView

ComputerAssociates TNG

BMC PATROL NetIQAppManager

Bulk Discovery No Yes Yes Yes No

Auto Discovery Yes No Yes Yes Yes

Rediscovery Yes Yes Yes Yes No

Discovery byEvent

Yes No No No No

DiscoveryFiltering

Yes No Yes Yes No

AutomaticBusiness SystemSupport

Yes Yes Yes Yes Yes

The following table shows the supported monitors for Tivoli Monitoring forapplications.

Table 8. Tivoli Monitoring for Applications

IBM Tivoli Monitoring forApplications - mySAP.com

IBM Tivoli Monitoring forApplications - Siebel

Bulk Discovery Yes Yes

Rediscovery Yes Yes

Discovery by Event Yes Yes

Discovery Filtering No No

Automatic Business SystemSupport

Yes Yes

The following table shows the supported monitors for Tivoli Monitoring forbusiness integration.


Table 9. Tivoli Monitoring for Business Integration

IBM Tivoli Monitoring forBusiness Integration -WebSphere MQ

IBM Tivoli Monitoring forBusiness Integration -WebSphere MQI


Rediscovery Yes Yes


Discovery Filtering Yes No


Yes Yes

The following table shows the supported monitors for Tivoli Monitoring fordatabases.

Table 10. Tivoli Monitoring for Databases

IBM TivoliMonitoring forDatabases - Oracle

IBM TivoliMonitoring forDatabases - DB2

IBM TivoliMonitoring forDatabases - Informix

Bulk Discovery Yes Yes Yes

Rediscovery Yes Yes Yes

Discovery by Event Yes Yes Yes

Discovery Filtering No No No

Automatic BusinessSystem Support

Yes Yes Yes

The following table shows the supported monitors for Tivoli Monitoring for Webinfrastructure.

Table 11. Tivoli Monitoring for Web Infrastructure

IBM TivoliMonitoring for WebInfrastructure -Apache

IBM TivoliMonitoring for WebInfrastructure -WebSphereApplication Server

IBM TivoliMonitoring for WebInfrastructure -iPlanet

Bulk Discovery Yes Yes Yes

Rediscovery Yes Yes Yes

Discovery by Event Yes Yes Yes

Discovery Filtering No No No

Automatic BusinessSystem Support

Yes Yes Yes

The following table shows the supported monitors for Tivoli Monitoring formessaging and collaboration.

Table 12. Tivoli Monitoring for Messaging and Collaboration

IBM Tivoli Monitoring forWeb Infrastructure - IIS

IBM Tivoli Monitoring forMessaging andCollaboration - Domino


Rediscovery Yes Yes



Table 12. Tivoli Monitoring for Messaging and Collaboration (continued)



Discovery Filtering No No


Yes Yes

Resource MonitoringThis section describes the resources monitored by Tivoli Business Systems Managerintegration.

Base ResourcesBase resources include the monitoring of resources that are directly underEnterprise, Complex, Machine, LPAR, or OS. These may include CICSPlex, RODM,SMS and other resources.

Low-level ResourcesThese are resources that are children of base resources. These may be DB2 bufferpools, CICS to CICS connection, CICS to DB2 connection, IMS databases or otherresources.

Supported Resource Monitoring Functionality by ProductThe following table shows the supported OS/390 monitors for the resourcemonitoring process.

Table 13. OS/390 Supported Monitors

IBM TivoliRMF

CandleOMEGAMON IIfor MVS

ASG-TMON forMVS

BMCMAINVIEWMVS

IBMTivoliSMS

IBMTivoliHSM

IBMTivoliXRC

BaseResources

Yes Yes Yes Yes Yes Yes Yes

Low-levelResources

No No Yes Yes Yes Yes Yes

The following table shows the supported Subsystem monitors for CICS for theresource monitoring process.

Table 14. Subsystem Monitors (CICS)



ASG-TMON forCICS

BMC MAINVIEWCICS

Regions Yes Yes Yes Yes

Transactions Yes Yes Yes Yes

Files Yes Yes Yes Yes

LUs No No No No

CICS Connections Yes No No No

CICS-DB2Connections

Yes No No No


Table 14. Subsystem Monitors (CICS) (continued)



ASG-TMON forCICS

BMC MAINVIEWCICS

CICS Corba Servers Yes No No No

CICS DJARS Yes No No No

Resource Monitoring View

CICS Topology Yes No No No

CICS Link Topology Yes No No No

Launch CPSMConsole

Yes, WUI No No No

The following table shows the supported Subsystem monitors for DB2 and IMS forthe resource monitoring process.

Table 15. Subsystem monitors (DB2 and IMS)

IBMTivoliDB2 PM /Native

CandleOMEGAMON IIfor DB2

ASG-TMONfor DB2

BMCMAINVIEWDB2

IBMTivoliNativeIMS

CandleOMEGAMONII for IMS

BMCMAINVIEWIMS

BaseResources

Yes Yes Yes Yes Yes Yes Yes

Low-levelResources


The following table shows the supported Subsystem monitors for WebSphere forthe resource monitoring process.

Table 16. Subsystem Monitors (WebSphere)

Websphere OS/390

Base Resources Yes

Low-level Resources Yes

The following table shows the supported Job Schedulers for the resourcemonitoring process.

Table 17. Job Schedulers

ComputerAssociates CA7

IBM OPC IBM TWS 8.1 BMC Control-M ASG-Zeke

Base Resources Yes Yes Yes Yes Yes

Low-levelResources

Yes Yes Yes Yes Yes

The following table shows the supported automation products for the resourcemonitoring process.


Table 18. Automation Products

IBM NetviewOS/390 w/RODM

IBM SA OS/390 ComputerAssociatesOPS/MVS

CandleAF/Operator

BMC AutoOperator

Base Resources Yes Yes Yes Yes Yes

Low-levelResources

Yes (only SNA) Yes Yes Yes Yes

The following table shows the supported monitors for distributed sources for theresource monitoring process.

Table 19. Distributed Sources Supported Monitors

Tivoli EnterpriseConsoleResources

IBM TivoliNetView

ComputerAssociates TNG

BMC PATROL NetIQAppManager

Base Resources Yes* Yes Yes Yes Yes

Low-levelResources

Yes* Yes Yes Yes No

* The types of resources generated by events from the Tivoli Enterprise Console is dependent on the type of eventsmonitored and by the instrumentation generating the events.

The following table shows the supported monitors for Tivoli Monitoring forapplications.

Table 20. Tivoli Monitoring for Applications

IBM Tivoli Monitoring forApplications - mySAP.com

IBM Tivoli Monitoring forApplications - Siebel

Base Resources Yes Yes

Low-level Resources No No

The following table shows the supported monitors for Tivoli Monitoring forbusiness integration.

Table 21. Tivoli Monitoring for Business Integration

IBM Tivoli Monitoring forBusiness Integration -WebSphere MQ

IBM Tivoli Monitoring forBusiness Integration -WebSphere MQI



The following table shows the supported monitors for Tivoli Monitoring fordatabases.

Table 22. Tivoli Monitoring for Databases

IBM TivoliMonitoring forDatabases - Oracle

IBM TivoliMonitoring forDatabases - DB2

IBM TivoliMonitoring forDatabases - Informix

Base Resources Yes Yes Yes

Low-level Resources No No No

The following table shows the supported monitors for Tivoli Monitoring for Webinfrastructure.


Table 23. Tivoli Monitoring for Web Infrastructure

IBM TivoliMonitoring for WebInfrastructure -Apache

IBM TivoliMonitoring for WebInfrastructure -WebSphereApplication Server

IBM TivoliMonitoring for WebInfrastructure -iPlanet

Base Resources Yes Yes Yes

Low-level Resources No No No

The following table shows the supported monitors for Tivoli Monitoring formessaging and collaboration.

Table 24. Tivoli Monitoring for Messaging and Collaboration






Appendix B. Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents.You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

37

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

TrademarksAdvanced Peer-to-Peer Networking, APPN, CICS, CICSPlex, DB2, DB2 UniversalDatabase, DFSMS/MVS, DFSMShsm, IBM, IMS, IMS/ESA, Informix, MQSeries,MVS, NetView, OS/390, RMF, Tivoli, Tivoli Enterprise, Tivoli Enterprise Console,TME 10, VTAM, WebSphere and z/OS are trademarks of International BusinessMachines Corporation in the United States, other countries, or both.

Lotus, Domino, and WordPro are trademarks of International Business MachinesCorporation and Lotus Development Corporation in the United States, othercountries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in theUnited States, other countries, or both.

Other company, product, and service names may be trademarks or service marksof others.


Index

Aaccessibility information viiAdministrator, Tivoli Business Systems

Manager 4AF/OPERATOR 22ASG-Zeke 22auto discovery process 27automated creation of a business

system 2automatic business system support

process 28automating problem tickets 5automation products

AF/OPERATOR 22CA-OPS/MVS 22MAINVIEW AutoOPERATOR for

OS/390 23monitoring 22system automation for OS/390 22

Bbase services and components

consoles 11health monitor 11overview 10servers 10

bulk discovery 27business system

overview 2views 3

CCA-7 21CA-OPS/MVS 22CICS subsystems

ASG-TMON for CICS 18CICSPlex system manager for

OS/390 17MAINVIEW for CICS 17monitoring 17OMEGAMON for CICS 18

components for handling distributeddata 9

components, Source/390 7console monitoring 14contacting customer support viiCONTROL-M for OS/390 21customer support vii

Ddata collection, implementation 25data sources

automation products 22CICS subsystems 17DB2 subsystems 18distributed resources 13

data sources (continued)IMS subsystems 19job schedulers 20MVS 14overview 13storage management resources 15WebSphere Application Server for

z/OS and OS/390 23dataspace, Source/390 7DB2 subsystems

ASG-TMON for DB2 19MAINVIEW for DB2 19monitoring 18monitoring of subsystems running

DB2 universal database 18OMEGAMON for DB2 19

disability information viidiscovery by event process 27discovery filtering process 28discovery process

auto discovery 27automatic business system

support 28bulk discovery process 27discovery by event 27discovery filtering 28overview 2rediscovery 27running 27supported functionality by

product 28distributed resources

overview 13documents

feedback vonline vordering v

Ee-mail contact viievent enablement 9event processing 3

Ffeedback about publications vii

IIBM WebSphere Application Server for

z/OS and OS/390monitoring 23

implementing Tivoli Business SystemsManager

data collection 25discovery 25enterprise customization 26installation 26overview 25

implementing Tivoli Business SystemsManager (continued)

production deployment 26site preparation 25

IMS subsystemsIMS monitoring 19MAINVIEW for IMS 20monitoring 19OMEGAMON for IMS 20

information, accessibility viiinformation, disability vii

Jjob schedulers

ASG-Zeke 22CA-7 21CONTROL-M for OS/390 21monitoring 20Tivoli Operating Planning and

Control 21Tivoli workload scheduler 21

Kkeyboard, shortcut keys vii

MMAINVIEW AutoOPERATOR for

OS/390 23manuals

feedback vonline vordering v

master console 1MVS

ASG-TMON for MVS 15MAINVIEW for OS/390 15monitoring 14MVS console 14OMEGAMON for MVS 15Resource Management Facility 14Tivoli NetView for OS/390 14

Oobject pump, Source/390 7object server, Source/390 7OMEGAMON for CICS 18OMEGAMON for DB2 19OMEGAMON for IMS 20online publications viordering publications vi

Pperformance monitors 1prerequisite publications vi

39

problem and change support 5problem tickets

automating 5publications

accessing online viordering viprerequisite viproviding feedback about viirelated vi

Rrediscovery process 27related publications viresource monitoring

base resources 32low-level resources 32supported functionality by

product 32resources 3

Sshortcut keys, keyboard viiSource/390 components 7

Source/390 dataspace 7Source/390 object pump 7Source/390 object server 7

storage management resourcesdata facility systems managed storage

hierarchical storage manager 16extended remote copy 16monitoring 15system-managed storage 15

supported discovery functionality byproduct 28

System Automation for OS/390 22

TTivoli Business Systems Manager

instrumentation 5monitoring options 3problem and change support 5reporting system 5workstation 1

Tivoli Operating Planning andControl 21

Tivoli Workload Scheduler 21

Vviews

business system 3


��

Printed in U.S.A.

GC32-0801-00

ibm tivoli business systems manager: getting...

Documents