Planning and Configuration Guide

Transcription

1 IBM Tivoli OMEGAMON XE on z/os Version 5 Release 1 Planning and Configuration Guide GC

2

3 IBM Tivoli OMEGAMON XE on z/os Version 5 Release 1 Planning and Configuration Guide GC

4 Note Before using this information and the product it supports, read the information in Notices on page 143. March 2012 This edition applies to version 5, release 1, modification 0 of IBM Tivoli OMEGAMON XE on z/os (product number 5698-T01) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2008, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures vii Tables ix Part 1. Preparation and planning... 1 Chapter 1. Introducing IBM Tivoli OMEGAMON XE on z/os Tivoli Management Services OMEGAMON XE common components Interoperability and integration New in this release Tivoli Management Services PARMGEN configuration method Self describing agents Enhanced 3270 user interface High availability hub on z/os Automatic registration of products with the local monitoring server PARMGEN Phase 2 changes OMEGAMON XE on z/os New workspaces for the OMEGAMON Enhanced 3270 User Interface Take Action commands Health check information New attribute groups New classic minor commands UNIX System Services 64-bit I/O count attribute New out-of-the-box defaults Performance improvements Chapter 2. Planning for configuration 11 Configuration prerequisites Software and hardware requirements Required software Supported operating systems Supported hardware Prerequisites for data collection and display.. 12 Using RMF data collection Planning configuration of OMEGAMON II for MVS 15 Migrating tables and data sets from another installation library OMEGAMON Subsystem Sharing the OMEGAMON Subsystem System requirements Starting the OMEGAMON Subsystem automatically Determining whether or not to install the OMEGAMON Subsystem Determining the dispatching authority to use 17 Modes of operation Historical data collection and reporting EPILOG historical data collector EPILOG data store (EDS) EPILOG historical reporter Planning configuration of OMEGAMON XE on z/os Defining Sysplexes Designating the Sysplex proxy Defining an enqplex Planning historical data collection Configuring the historical data stores for OMEGAMON XE on z/os Configuring historical data stores for OMEGAMON II for MVS Determining DASD requirements for storing historical data Before you begin configuration Chapter 3. Upgrading to the new release Configuring a high availability hub and converting a static hub to a remote Enabling new features Performing a staged upgrade Part 2. Configuration Chapter 4. Configuring OMEGAMON XE on z/os using the PARMGEN method. 29 Configuring OMEGAMON II for MVS (PARMGEN) 30 Configuring logon security (PARMGEN) Configuring EPILOG history (PARMGEN) Migrating profiles and screen spaces (PARMGEN) Specifying OMEGAMON II applids and started task names (PARMGEN) Specifying OMEGAMON profiles (PARMGEN) 35 Configuring OMEGAMON XE using the PARMGEN method Configuring security for Take Action commands 36 Configuring the OMEGAMON XE on z/os agent to use RMF data (PARMGEN) Turning off ziip offload (PARMGEN) Sending messages for proxy switch to the console (PARMGEN) Specifying MIM names (PARMGEN) Chapter 5. Configuring OMEGAMON XE on z/os using the Configuration Tool. 39 Configuring the OMEGAMON II for MVS component Summary of the configuration steps Accessing the Runtime Environments (RTEs) panel Specify configuration values Allocate historical data stores Copyright IBM Corp. 2008, 2012 iii

6 Create runtime members Register with local Tivoli Enterprise Monitoring Server Install the OMEGAMON Subsystem Complete the configuration Copy procedures to PROCLIB Copy VTAM definitions to VTAMLST Vary VTAM major node active APF-authorize libraries Modify virtual terminal pool definitions, if applicable Modify Classic interface command security (optional) Migrate profile members from previous versions (optional) Configuring the OMEGAMON XE on z/os monitoring agent Summary of configuration steps Begin the configuration Define a single LPAR environment Define Enterprise-wide ENQ manager Define your Sysplex environment Specify configuration parameters for security.. 62 Assign this runtime environment to a Sysplex.. 63 Register with the local Tivoli Enterprise Monitoring Server Install the agent into the local Tivoli Enterprise Monitoring Server Configure persistent datastore Modify and review data store specifications 65 Create or edit PDS maintenance job card.. 67 Create runtime members Edit and submit data store allocation job.. 67 Complete persistent data store configuration 67 Load the runtime libraries Complete the configuration Chapter 6. Completing the configuration Update the IEFSSNxx member of SYS1.PARMLIB.. 72 Update the LINKLIST Add support for the SYSTCPD DDNAME in the started tasks Copy started task procedures to your procedure library Copy the VTAM definitions to your system VTAMLST Vary the VTAM major node active APF-authorize the runtime load libraries Enable historical data store maintenance Provide access to the persistent data store files 76 Authorize the KPDDSCO module Verify persistent data store configuration Copy CSFPRM00 into SYS1.PARMLIB Add the KM5EXIT3 to the ICSF Configuration.. 77 Method 1: Add RKANMOD to the ICSF STEPLIB 77 Method 2: Copy RKANMOD(KM5EXIT3) to a new data set Modify the ICSF subsystem JCL Authorize address spaces for UNIX System Services 77 Enable RMF data collection iv IBM Tivoli OMEGAMON XE on z/os: Planning and Configuration Guide Define RACF IDs for OMEGAMON XE on z/os address spaces Enable the RACF secured signon function (PassTicket) Turn on RMF collection of coupling facility and lock data Configure historical data collection Enable Warehouse agents on a z/os hub monitoring server Create situations to filter DASD device collection.. 81 Set the PROJECTCPU control in the SYS1.PARMLIB IEAOPTxx member Install application and language support Verify the configuration Enable security for Tivoli Enterprise Portal Authorize users to issue Take Action commands.. 83 z/os commands UNIX commands Prefixed Take Action commands Recreate or replace z/os Management Console situations Authorize users to access OMEGAMON XE on z/os managed systems on the enhanced 3270 user interface Part 3. Appendixes Appendix A. Disk space requirements for OMEGAMON XE on z/os historical data tables Understanding how the data store works Estimated space requirements A reminder about historical data and performance impacts Appendix B. Securing OMEGAMON and OMEGAMON II Securing OMEGAMON for MVS (Realtime collector) 97 Modifying the security table Implementing external security for OMEGAMON 98 Securing OMEGAMON with RACF Set up RACF rules Customize, assemble, and link the KOMRACFX exit routine Modify the security table for RACF Securing OMEGAMON with CA-ACF Set up CA-ACF2 rules Customize, assemble, and link the KOMACF2X exit routine Modify security table for CA-ACF Securing OMEGAMON with CA-TOP SECRET Set up CA-TOP SECRET rules Customize, assemble, and link the KOMRACFX exit routine Modify security table for CA-TOP SECRET OMEGAMON security control statements General format rules for control statements 105

7 AUTHLIB COMMAND LIST MINOR MODULE PASSWORD RESET SMFNUM UPDATE Security update program listing Accessing authorized commands Changing your security level to issue authorized commands Security exit processing logic The System Management Facilities audit Securing OMEGAMON II for MVS Enabling Network Access Manager Security Enabling RACF security Enabling CA-ACF2 security Enabling CA-TOP SECRET security Appendix C. Customizing EPILOG historical data collector controls Controlling collection options Adding a collector filter COLLECT statement Conditions when you have more than one COLLECT statement Workload keywords for COLLECT Resource keywords for COLLECT Date and time keywords for COLLECT Providing automatic data store maintenance Conditions that suppress automatic maintenance 128 Required authorizations Monitoring the status of the data stores Adding a data store Dropping a data store Switching to another data store without stopping the collector Manually starting the maintenance procedure Recovering data from SMF Sample job to load SMF data LOAD statement syntax Documentation library OMEGAMON XE on z/os library OMEGAMON XE and Tivoli Management Services on z/os common library OMEGAMON II for MVS V520 library IBM Tivoli Monitoring library Other sources of documentation Support information Notices Trademarks Glossary Index Appendix D. Managing EPILOG data stores Examples of chronological switching Contents v

8 vi IBM Tivoli OMEGAMON XE on z/os: Planning and Configuration Guide

9 Figures 1. Agent-server-client architecture Deployment of OMEGAMON XE on z/os in a multiplex environment OMEGAMON II for MVS started tasks, VTAM, and applid parameters Configuration Tool Main Menu Configure Products panel Product Selection Menu Runtime Environments (RTEs) panel Product Component Selection Menu Configure OMEGAMON II for MVS panel Specify Configuration Values panel Specify VTAM applids Values Specify Historical Datastore Allocation panel Specify Security and Other Parameters panel Install OMEGAMON Subsystem panel Specify Configuration Parameters panel Configure OMEGAMON XE on z/os panel Define a Single LPAR Environment panel Add a New Sysplex panel Define Enterprise wide ENQ manager Define Your Sysplex Environment panel The Add a New Sysplex panel Specify Configuration Parameters panel Assign this RTE rtename to a Sysplex Allocate Persistent Datastore menu Persistent Datastore Specifications panel 66 Copyright IBM Corp. 2008, 2012 vii

10 viii IBM Tivoli OMEGAMON XE on z/os: Planning and Configuration Guide

11 Tables 1. z/os common components Data prerequisites Characteristics and requirements for OMEGAMON II modes of operation What data store is configured at each step Preconfiguration tasks Tasks to complete before configuring OMEGAMON XE on z/os Prerequisite configuration Started tasks in RKANSAMU library Historical data table names and corresponding attribute groups System-level data profiles for small, medium, and large environments Sysplex-level data profiles for small, medium, and large environments Number of cylinders required for 24 hours for system-level (LPAR) data Number of cylinders required for 24 hours for sysplex-level (PLEX) data Choices of security facilities for implementing OMEGAMON security Security exit routines for external command-level security OMEGAMON II security options Keywords used with the OPTIONS statement Workload keywords for COLLECT statement Resource keywords for COLLECT statement Date and time keywords for COLLECT statement Automatic maintenance processing Column headers in Collector Status Display EDS STATUS column values Copyright IBM Corp. 2008, 2012 ix

12 x IBM Tivoli OMEGAMON XE on z/os: Planning and Configuration Guide

13 Part 1. Preparation and planning This guide provides information specific to configuration of IBM Tivoli OMEGAMON XE on z/os. The OMEGAMON XE Products: Preinstallation Requirements and Instructions technote and the OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide contain planning information that is common to the deployment and configuration of all OMEGAMON XE monitoring agents and Tivoli Management Services components on z/os. You should be familiar with the information in those documents before you read the information in this book. (See Other sources of documentation on page 140 for information on locating technotes.) The chapters in this section contain introductory and planning information: v Chapter 1, Introducing IBM Tivoli OMEGAMON XE on z/os, on page 3 provides an overview of the monitoring product and the infrastructure on which it runs. It also introduces new features of the product that may affect deployment and configuration. v Chapter 2, Planning for configuration, on page 11 discusses prerequisites for product installation and the monitoring of certain types of data and provides information to help you plan the configuration of OMEGAMON XE on z/os monitoring agents. v Chapter 3, Upgrading to the new release, on page 23 discusses the product-specific requirements and sequence of steps for upgrading to this release. A Tivoli Enterprise Monitoring Server must be configured in each runtime environment in which OMEGAMON XE on z/os is configured. Before you continue to Part 2, Configuration, on page 27, use IBM Tivoli Monitoring: Configuring the Tivoli Enterprise Monitoring Server on z/os to configure a monitoring server in each runtime environment. Copyright IBM Corp. 2008,

14 2 IBM Tivoli OMEGAMON XE on z/os: Planning and Configuration Guide

15 Chapter 1. Introducing IBM Tivoli OMEGAMON XE on z/os IBM Tivoli OMEGAMON XE on z/os is a member of the latest generation of the OMEGAMON family of mainframe monitoring products. OMEGAMON XE on z/os enables you to monitor and manage the performance and availability of individual z/os systems, as well as the workload performance and resource utilization of the Parallel Sysplex in which they participate. OMEGAMON XE on z/os monitoring agents installed on monitored z/os LPARs (logical partitions) provide comprehensive usage information for Sysplex-level resources such as coupling facilities, global enqueues, global resource serialization (GRS) ring systems, shared DASD groups, and cross-system coupling facilities (XCFs), as well as performance information for the service classes, report classes, and resource groups that use those resources. OMEGAMON XE on z/os monitoring agents also provide extensive system-level performance and usage information for individual z/os images. In addition, they monitor the status and configuration of IBM cryptographic coprocessors installed in zseries servers, provide data on UNIX System Services hosted on your z/os systems, and allow system-level and sysplex-wide reporting of actual and potential special processor resource usage. The data collected by the monitoring agents and alerts triggered by monitored conditions can be displayed in a graphical, Java-based interface, shared with other OMEGAMON XE and IBM Tivoli Monitoring products. In addition, OMEGAMON XE on z/os offers continued access to the OMEGAMON for MVS and OMEGAMON II for MVS 3270 interfaces, as well as a new, enhanced 3270 interface with specially-designed workspaces that can provide plex-wide and even cross-product data. Used in conjunction with other OMEGAMON XE monitoring products, the data, analyses, and alerts presented by OMEGAMON XE on z/os help you develop a holistic view of your entire computing enterprise from a single console. Tivoli Management Services OMEGAMON XE on z/os takes advantage of the Tivoli Management Services infrastructure. Tivoli Management Services provide security, data transfer and storage, notification mechanisms, user interface presentation, and communication services for a number of products, including IBM Tivoli Monitoring and OMEGAMON XE monitoring agents, in an agent-server-client implementation (Figure 1 on page 4). Copyright IBM Corp. 2008,

16 Figure 1. Agent-server-client architecture Some components of Tivoli Management Services, such as Tivoli Enterprise Portal and the Warehouse Proxy and Summarization and Pruning agents, run only on distributed systems (Windows, AIX, and Linux). The Tivoli Enterprise Monitoring Server and the Tivoli Data Warehouse can run on either distributed or mainframe systems. The Tivoli Management Services:Engine runs only on mainframe systems. The components of Tivoli Management Services are described in detail in the OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide. The required versions of all Tivoli Management Services components are included in the OMEGAMON XE on z/os package. For detailed information about installing, configuring, and using Tivoli Management Services, see the documents in the IBM Tivoli Monitoring Library. OMEGAMON XE common components OMEGAMON XE monitoring agents on z/os share several components (referred to as common components: see Table 1). These common components, along with the monitoring agent software are included on the OMEGAMON XE on z/os V5.1.0 product tape. Table 1. z/os common components End-to-End Response Time collector V6.2.0 Provides response time data for several OMEGAMON XE products. 4 IBM Tivoli OMEGAMON XE on z/os: Planning and Configuration Guide

17 Table 1. z/os common components (continued) OMNIMON base V7.0.0 A set of common code used by OMEGAMON Classic (realtime collectors) components and the OMEGAMON enhanced 3270 user interface to control initialization, security, and I/O for all sessions. OMNIMON Base has two components: v OMEGAMON Subsystem (formerly Candle Subsystem) A z/os subsystem, running in its own address space, that enables OMEGAMON IIs running in other address spaces to monitor dynamic device activity. A single OMEGAMON Subsystem can support multiple copies of OMEGAMON II and multiple OMEGAMON II products on a single z/os image. The OMEGAMON Subsystem also collects coupling facility data for OMEGAMON XE on z/os. Not all OMEGAMON XE monitoring products require the OMEGAMON Subsystem. v OMEGAMON enhanced 3270 user interface An enhanced 3270-based user interface that collects and displays data from the Tivoli Enterprise Monitoring Server and the supporting OMEGAMON XE on z/os monitoring agents. One instance of the interface must be installed in each Sysplex for use by all supporting agents. Shared probes Data probes shared by several OMEGAMON XE products. Note: If you install OMEGAMON XE on z/os into an existing environment, in which the components are already at the required level (for example, if you have already installed another OMEGAMON XE agent), you may need to delete the FMIDs for these components from the SMP/E install jobs to avoid errors because they are already installed. See the IBM Tivoli OMEGAMON XE on z/os: Program Directory for more information. Interoperability and integration OMEGAMON XE on z/os is designed to integrate with all products that use Tivoli Management Services. These products exploit the ability of the Tivoli Enterprise Portal to integrate and correlate performance and availability information from a variety of sources. For example, with OMEGAMON DE, the Tivoli Enterprise Portal allows you to create custom workspaces composed of data from a range of Tivoli monitoring solutions (IBM Tivoli Monitoring, IBM Tivoli Composite Application Manager, and IBM Tivoli NetView for z/os, as well as OMEGAMON XE monitoring agents). You can also create context-sensitive links between product workspaces to obtain additional information about systems, subsystems, resources or network components that are being monitored by other monitoring agents, or links that access related screens in TN3270-based applications. OMEGAMON XE products are being integrated with an increasing number of other Tivoli and IBM products. Situation events reported by OMEGAMON XE on z/os can be forwarded to Tivoli Event Console or Tivoli Netcool/OMNIbus for event correlation and management. You can view historical reports using Tivoli Common Reporting. From the Tivoli Enterprise Portal you can launch "in context" into other Web-based or web-enabled Tivoli applications without having to re-enter user credentials, and you can launch in context into Tivoli Enterprise Portal workspaces from applications such as IBM Tivoli Business Services Management. Note: OMEGAMON XE on z/os V5.1.0 is not compatible with IBM OMEGAMON z/os Management Console. New in this release The following topics describe features of the shared infrastructure and the monitoring agent itself that affect deployment and configuration. If you are already using Tivoli Management Services components at V6.2.3 or higher, you may already be familiar with some of the changes described here. Chapter 1. Introducing IBM Tivoli OMEGAMON XE on z/os 5

18 For detailed descriptions of all the new features in OMEGAMON XE on z/os V5.1.0, see IBM Tivoli OMEGAMON XE on z/os: User's Guide. Tivoli Management Services OMEGAMON XE on z/os supports Tivoli Management Services V6.2.3 Fix Pack 1. The following topics introduce new features that may affect deployment and configuration. If you are already using Tivoli Management Services components at V6.2.3 or higher, you may already be familiar with some of the features described here. For detailed descriptions of all the new features in Tivoli Management Services V6.2.3 Fix Pack 1, see IBM Tivoli Monitoring: Tivoli Enterprise Portal User's Guide. PARMGEN configuration method The PARMGEN configuration method uses a runtime environment based approach to configuration. With PARMGEN, you edit a comprehensive list of parameters to configure all the installed products and components in a runtime environment. You then submit a series of jobs to create a complete runtime environment with the parameter values you specified. A workflow "wrapper" steps you through the configuration process. The PARMGEN configuration method is the preferred configuration method and is intended to replace the Configuration Tool (ICAT). For more information, see "Configuring products with the PARMLIB method" in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide, the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Parameter Reference, IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: PARMGEN Reference, the IBM Tivoli OMEGAMON XE on z/os: Parameter Reference, and the PARMGEN Technote at support/docview.wss?uid=swg Self describing agents Monitoring agents have been enhanced with a self description capability that automatically distributes each agent's operating configuration directly to the local monitoring server, which then distributes those agent configuration files first to the hub monitoring server (if necessary) and then to the various IBM Tivoli Monitoring components that require it. Prior to Tivoli Management version 6.2.3, before an agent could connect to a Tivoli Enterprise Monitoring Server, you were required to update the monitoring server (as well as other Tivoli Management Services components such as the Tivoli Enterprise Portal Server and the Tivoli Data Warehouse) with information necessary for it to recognize and process data sent by that agent. As of V6.2.3, this "seeding" step (as it was once known) becomes unnecessary. By default, the self describing capability is disabled on z/os hub monitoring servers. Enabling the self describing capability of monitoring agents ensures that the proper level of application data is installed on monitoring servers and the Tivoli Enterprise Portal. If the self description feature is activated, runtime verification checks for updated application data. If inconsistent conditions are detected, application data is propagated from the agent to the various monitoring servers, which are automatically updated without requiring recycling of the hub monitoring server. If you intend to enable the self describing features and a z/os hub monitoring server, you should configure a high availability hub. For more information, see IBM Tivoli Monitoring: Configuring the Tivoli Enterprise Monitoring Server on z/os, IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide, and Planning configuration of OMEGAMON XE on z/os on page IBM Tivoli OMEGAMON XE on z/os: Planning and Configuration Guide

19 Enhanced 3270 user interface The OMEGAMON enhanced 3270 user interface is a z/os-based interface that supports plex-wide and cross-product views, as well as summary and detail views of single entities. The interface integrates the OMEGAMON monitoring products under a "single pane of glass". The enhanced 3270 user interface is the latest generation of 3270-based user interfaces for the OMEGAMON monitoring products. Used in conjunction with OMEGAMON XE monitoring agents and the Tivoli Enterprise Monitoring Server, the Enhanced 3270 User Interface enables you to monitor the performance of the z/os systems, applications, and devices in your environment and helps you identify and troubleshoot problems with those monitored resources. The enhanced interface offers the following features: v plex-wide as well as single system views of data v autodiscovery of and autoconnection to data sources v customizable workspaces v fastpath navigation v support for screen sizes up to 62 x 160 v dynamic behavior and operation v Take Action commands v SAF-based security for logon, data access, and Take Action commands High availability hub on z/os You can now configure a high-availability hub monitoring server in any Sysplex environment with dynamic virtual IP addressing (DVIPA) and shared DASD. A high-availability hub is configured in its own runtime environment, without any monitoring agents connecting to it and can be configured on the same LPAR with a remote monitoring server. This configuration allows the hub monitoring server to be relocated to any suitable LPAR in the Sysplex with no changes, and with minimal disruption to the components connecting to the hub. For instructions on configuring a high-availability hub on z/os, see IBM Tivoli Management Services on z/os: Configuring the Tivoli Enterprise Monitoring Server on z/os. Automatic registration of products with the local monitoring server Runtime environment load processing now automatically copies the KppATR and KppCAT members from the &thilev.tkandatv target data set installed by SMP/E to the runtime environment RKANDATV library. If you apply maintenance that updates only the KppATR and KppCAT members, you do not have to reregister with the monitoring server. Instead, you can just reload the runtime environment to refresh the members. Registration with the local Tivoli Enterprise Monitoring Server is still required the first time you configure a monitoring agent or whenever you apply maintenance that updates parameters. PARMGEN Phase 2 changes If you have been using the PARMGEN (formerly PARMLIB) configuration method previously, you should be aware of the following new additions. v Generation of the 350COMPATMODE GRS enqueue parameter in the monitoring server KDSENV KDS_RUN KFAXCF.FAXCSRV &proxy_position,plex command has been obsoleted to support the nonenqueue means of Sysplex proxy arbitration. v A MODE() parameter is now supported in the OMEGAMON XE on z/os KEPOPTN member of xkanparu. v A SAMP=99 parameter in OMEGAMON XE on z/os is now supported in the Common Storage Analyzer started task (by default, CANSM2CS). v Support for customizable LOG= and DEBUG= parameters has been added to the OMEGAMON XE on z/os KM2IPARM member of xkanparu. Chapter 1. Introducing IBM Tivoli OMEGAMON XE on z/os 7

20 OMEGAMON XE on z/os V5.1.0 introduces a number of new features, in addition to support for Tivoli Management Services V6.2.3 Fix Pack 1. New workspaces for the OMEGAMON Enhanced 3270 User Interface OMEGAMON XE on z/os V5.1.0 introduces a set of workspaces designed for the OMEGAMON enhanced 3270 user interface. The new workspaces support scenarios that provide monitoring, planning, and troubleshooting of z/os systems and resources, including the following workspaces: v High CPU usage from a Sysplex perspective: This set of workspaces enables you to identify high usage, use bottleneck analysis to profile offending address spaces, use the inspect function to evaluate which instructions in which module are consuming the cycles, and cancel looping jobs. v Top consumers Displays top 10 consumers for a specific Sysplex in 8 categories: CPU, real storage, virtual storage, CSA storage, ECSA storage, I/O, enqueue conflicts, and Performance Index v High CPU usage from a CPC perspective v LPAR overview v LPAR CPU v Global enqueue delay, at the Sysplex level. v Enqueue delay, LPAR level v Various storage scenarios Take Action commands In V5.1.0, OMEGAMON XE on z/os introduces a set of Take Action commands. These commands, issued with the prefix M5:, can be run from either the Tivoli Enterprise Portal or the OMEGAMON enhanced 3270 user interface. By default, any unprefixed command issued on behalf of OMEGAMON XE on z/os in the Tivoli Enterprise Portal is issued as a z/os system command. Commands prefixed with a UNIX-specific prefix are issued as UNIX commands. Starting with V5.1.0, OMEGAMON XE on z/os provides the following set of agent commands, which use the prefix M5:. CANCEL CANCELDUMP CANCELRESTART CANCELDUMPRESTART KILL RESETSC QUIESCE RESUME CHANGETIMELIMIT SWAPIN MARKSWAPPABLE MARKNONSWAPPABLE Security for these agent Take Action commands is implemented through direct SAF (System Authorization Facility) calls and is based on resource profiles. Both user ID and command are validated. 8 IBM Tivoli OMEGAMON XE on z/os: Planning and Configuration Guide

21 You can use the SAF security class defined for the runtime environment to control access to the OMEGAMON XE on z/os commands, or use a separate security class. These new commands cannot be issued unless security is configured. Health check information OMEGAMON XE on z/os now provides health check information for z/os systems through both the Tivoli Enterprise Portal and enhanced 3270 user interfaces. Collection and display of health check information require that the IBM Health Checker for z/os software be installed, configured, and running. If New attribute groups Two new attribute groups, KM5 Host Configuration and KM5 Sysplex Configuration, provide monitoring status and configuration information for Sysplexes and central processing complexes (CPCs). The KM5 Top Consumers attribute group provides information on top consumers of various resources, including CPU, storage, I/O, enqueue conflicts, and Performance Index, for all LPARs in a central processing complex (CPC) or Sysplex. The KM5 LPAR Overview attribute group provides summary information about a selected LPAR. Intended primarily for workspaces in the OMEGAMON enhanced 3270 user interface, these attributes can also be used to create monitoring situations and automation policies in the Tivoli Enterprise Portal interface. New classic minor commands Two new OMEGAMON for MVS minor commands have been added: PEEK LPAG and SYS RMLF. The LPAG minor of PEEK displays large page usage for an address space. The metrics displayed are the number of allocated large memory objects and the number of 1 MB pages backed in real storage. The RMLF minor of SYS displays statistics for large frames and large pages. For more information about these commands, see the IBM Tivoli OMEGAMON XE on z/os: OMEGAMON for MVS Commands and Keywords Reference. UNIX System Services 64-bit I/O count attribute Similar to the 32-bit Number of I/Os Count attribute, the Number of I/Os Extended Precision attribute displays the total number of I/O operations performed by the kernel address space since it was started, extended to 64-bit precision. The 32-bit I/O count wraps when it reaches 2,147,483,648 and reverts to 0; the 64 bit I/O count does not wrap until it reaches 9,223,372,036,854,775,807. New out-of-the-box defaults Several defaults have been changed to improve out-of-the-box performance. v The default for the processing mode for the EPILOG data store has been changed from RESTART to BOTH. v The auto refresh interval for OMEGAMON for MVS has been changed from 5 seconds to 30 seconds. v The minimum value for the number of kilobytes of extended storage allocated for TMS:Engine has been increased to Performance improvements Several changes were made in V5.1.0 to improve performance. In addition to the change in the OMEGAMON for MVS VTAM mode refresh, the following changes were made to improve performance: Chapter 1. Introducing IBM Tivoli OMEGAMON XE on z/os 9

22 v The Common Storage Area Analyzer (CSA Analyzer) task has been modified to bypass detail collection when total common storage has not changed by more than 1% since the last collection, to save CPU resources. v The OS390 Unreferenced Interval Count situations have been modified to use the Page Dataset Activity attribute group instead of the Real Storage attribute group, as the paging group requires much less resource consumption to process. 10 IBM Tivoli OMEGAMON XE on z/os: Planning and Configuration Guide

23 Chapter 2. Planning for configuration The information in this section is intended to help you plan the configuration of OMEGAMON XE on z/os. This information assumes that you have met the relevant installation requirements discussed in the OMEGAMON XE Products: Preinstallation Requirements and Instructions technote and read the planning information in the OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide. The following topics are covered in this section: v Configuration prerequisites v Planning configuration of OMEGAMON II for MVS on page 15 v Planning configuration of OMEGAMON XE on z/os on page 18 v Planning historical data collection on page 20 v Before you begin configuration on page 22 If you are installing the OMEGAMON XE on z/os product for the first time, read the entire chapter. If you are upgrading from a prior version, you can proceed to Chapter 3, Upgrading to the new release, on page 23 after you have reviewed the configuration requirements for this release. Configuration prerequisites The topics in this section cover the hardware and software requirements for OMEGAMON XE on z/os, as well as the prerequisites for the collection and display of certain types of data. v Software and hardware requirements summarizes the prerequisite software and the supported operating systems and hardware. v Prerequisites for data collection and display on page 12 summarizes the conditions that must be in effect for certain types of data to be available. v Using RMF data collection on page 14 provides an overview of the configuration tasks required to enable use of data collected by z/os Resource Measurement Facility. Software and hardware requirements A complete list of the software and hardware prerequisites is provided in the IBM Tivoli OMEGAMON XE on z/os: Program Directory. The following sections provide an overview of these prerequisites: v Required software v Supported operating systems on page 12 v Supported hardware on page 12 Required software OMEGAMON XE on z/os requires Tivoli Management Services on z/os V6.2.3 or above. You can downloadtivoli Management Services on z/osv6.2.3 Fix Pack 1 from www14.software.ibm.com/webapp/iwm/web/prelogin.do?source=swg-tiv-acasf if you have purchased a product that requires it, using your IBM customer number and ibm.com ID. You can also obtain Tivoli Management Services on z/os v from CBPDO and ServerPac ( ssi/showdoc.jsp?docurl=/common/ssi/rep_ca/9/897/enus /index.html). Copyright IBM Corp. 2008,

24 If you intend to enable the self-describing agent feature, Tivoli Management Services V6.2.3 Fix Pack 1 is required at the hub Tivoli Enterprise Monitoring Server and the Tivoli Enterprise Portal Server. If you are installing any of the application support files from this image into an environment running IBM Tivoli Monitoring (ITM) version 6.2.3, then ITM V6.2.3 Fix Pack 1 (6.2.3-TIV-ITM-FP0001) or higher is required. The hardware and software prerequisites for the distributed components of Tivoli Management Services can be found in IBM Tivoli Monitoring: Installation and Setup Guide. The software and hardware requirements for a monitoring server on z/os are discussed in IBM Tivoli Management Services on z/os: Configuring the Tivoli Enterprise Monitoring Server on z/os. To make sure that you have the latest version of all components, check for any fix packs that might be available (go to the IBM Software Support site at Supported operating systems LPARs on which OMEGAMON XE on z/os monitoring agents are installed must be running z/os version 1 release 11 or higher. For information about APARs (authorized program analysis reports) required, see the IBM Tivoli OMEGAMON XE on z/os: Program Directory. For late-breaking information, see the Preventive Service Planning (PSP) bucket for this monitoring agent. Supported hardware OMEGAMON XE on z/os monitoring agents can be deployed on any hardware environment that supports z/os 1.11 or higher. Ensure that you have adequate disk space to accommodate the products you are installing. Before installing your OMEGAMON XE products, review the disk space requirements and considerations for an SMP/E installed environment, as documented in the IBM Tivoli OMEGAMON XE on z/os: Program Directory, to make sure that sufficient storage is available. Tip: During normal SMP/E processing, VSAM control interval and control area splits can occur. This causes fragmentation, which can degrade SMP/E performance and space utilization. To reorganize the CSI, use your site's approved utility and method for managing VSAM files. Prerequisites for data collection and display For an OMEGAMON XE on z/os monitoring agent to collect certain types of data, the Tivoli Enterprise Monitoring Server address space in which it is configured must be assigned a user ID and given the appropriate authorization. In addition, some attributes or attribute groups collect and display data only if specific conditions are met. To monitor UNIX System Services, the Tivoli Enterprise Monitoring Server must be identified to your security authorization facility as a UNIX System Services user as described in Authorize address spaces for UNIX System Services on page 77). To monitor coupling facility, cross-system coupling facility, or lock data collected by RMF, the Tivoli Enterprise Monitoring Server must have a RACF ID and the ID must be authorized to generate PassTickets, as described in Enable RMF data collection on page 78. Table 2 describes the additional prerequisites for collection and display of certain types of data. Table 2. Data prerequisites Data is available for 4 Hour MSUs attribute in the System CPU Utilization attributes group Only if A defined capacity is used as a basis for pricing and the z/os system is not running as a guest on z/vm. 12 IBM Tivoli OMEGAMON XE on z/os: Planning and Configuration Guide

25 Table 2. Data prerequisites (continued) Channel Path attributes The Resource Measurement Facility (RMF) has been started. Common Storage attributes The Common Storage Area Analyzer (CSA Analyzer) is started. Note: The CSA Analyzer is shipped and installed with OMEGAMON XE on z/os. It is configured as part of the configuration of the OMEGAMON II for MVS component and is started as a separate started task. Coupling facility and cross-system v The following RMF components are activated: coupling facility (XCF) data collected RMF Control Task (RMF) one instance on each system by the Resource Measurement Facility (RMF) Distributed Data Server (DDS) RMF Monitor III Gatherer (RMFGAT) one instance on each system RMF Distributed Data Server (GPMSERVE) one instance per sysplex v You have enabled RMF data collection as described in Using RMF data collection on page 14. Cryptographic attributes At least one IBM cryptographic coprocessor is installed and configured and the KM5EXIT3 exit is installed in the Integrated Cryptographic Service Facility (ICSF). Note: The KM5EXIT3 exit is shipped and installed with OMEGAMON XE on z/os. See Add the KM5EXIT3 to the ICSF Configuration on page 77 for more information. DASD MVS workspace and DASD RMF has been started. MVS Devices attributes GRS Ring Systems attributes The global resource serialization (GRS) complex is in ring mode. (If the complex is in star mode, only the name, status, and ring acceleration of each system are available.) Health Check attributes IBM Health Checker for z/os software be installed, configured, and running. HiperDispatch Management and HiperDispatch Logical Processors HiperDispatch Management mode is On. attributes Integrated Facility for Applications (IFA) on CP resource times at the address space and service class period level LPAR cluster attributes Model Permanent Capacity ID and Rating and Model Temporary ID and Rating Promoted Percent Sysplex DASD attributes (Sysplex DASD Device, Sysplex DASD Group, Sysplex DASD) Either v z/series Application Assist Processors are configured on the systems, or v Java applications are started using a switch (-Xifa:force) The z/os system is not running as a guest on z/vm. System hardware is z10 or above. The z/os Workload Manager blocked workload capability is enabled. A DASD filter situation is enabled. Suspend lock and spin lock data v The following RMF components activated: v v RMF Control Task (RMF) one instance on each system RMF Monitor III Gatherer (RMFGAT) one instance on each system RMF Distributed Data Server (GPMSERVE) one instance per sysplex You have enabled RMF data collection (see Using RMF data collection on page 14). Lock data collection is enabled on RMF. Chapter 2. Planning for configuration 13

26 Table 2. Data prerequisites (continued) User Response Time attributes zfs attributes z/os UNIX System Services attributes The End to End (ETE) Response Time collector is started. Note: The ETE response time collector is shipped and installed with the OMEGAMON XE on z/os product. It is configured as part of the configuration of the OMEGAMON II for MVS component and is started as a separate started task. zfs is specified as the file system on the monitored system (FILESYSTEM TYPE(ZFS) is specified in SYS1.PARMLIB(BPXPRMxx)). Note: For z/os 1.10, OMEGAMON XE on z/os uses an address space name of ZFS, unless the parameter KM3KZFSASNM=xxxxxxxx (where xxxxxxxx is the started task (STC) name of the zfs address space) has been added to the &rhilev.&rte.rkanparu(kdsenv). If you are running z/os V1.10, you can use the nonstandard parameters editing facility in the Configuration Tool to make this override so that it will not get overwritten. If the runtime environment was configured with PARMLIB, an override for KDSENV would ensure that this override persists. If you are running V1.11 or above, the ZFS name is obtained from the system, and you do not need to code this parameter. The address space where the OMEGAMON XE on z/os product is running has SUPER USER authority. This level of authority is equivalent to root (UID=0). Using RMF data collection OMEGAMON XE on z/os can be configured to obtain coupling facility (CF), cross-system coupling facility (XCF), and system lock data from the Resource Measurement Facility (RMF) Distributed Data Server (DDS) instead of collecting its own data. Using RMF data can eliminate duplicate data collection and provide you with consistent metrics. It can also result in some overhead savings. RMF data is collected at a shorter monitoring interval than the corresponding OMEGAMON XE on z/os data. Use of RMF can be enabled as part of Sysplex configuration. There are four options: NO The default. Disables RMF data collection. CF and XCF data is collected from the OMEGAMON Subsystem. ALL CF, XCF, and lock data is collected from RMF. CF/XCF CF and XCF data is collected from RMF. LOCK Spin and suspend lock data is collected from RMF. The availability of data depends upon the level of the operating system (see Supported operating systems on page 12). Use of RMF data collection requires that the following RMF components be activated: v RMF Control Task (RMF) one instance on each monitored system. v RMF Monitor III Gatherer (RMFGAT) one instance on each monitored system. v RMF Distributed Data Server (GPMSERVE) one instance per sysplex. The z/os system that is running the DDS (the GPMSERVE address space) must be V1.8 or above. (The DDS migrates to the system running the highest level of Monitor III.) In addition, the following tasks must be completed: v RACF IDS must be defined for the address spaces that will be using RMF data. 14 IBM Tivoli OMEGAMON XE on z/os: Planning and Configuration Guide

27 Activation of the DDS API requires a RACF user ID and password. As its user ID, OMEGAMON XE on z/os uses the name shown in the SDSF Display Active screen as the OWNER of the address space. This is often the started task name but does not have to be. The user IDs of these address spaces must be defined to RACF. You will probably want to add those IDs to a group to simplify PassTicket authorization (see below). v RACF secured signon PassTicket function for the DDS must be enabled. Passwords specified during configuration would have to be held in a secure, encrypted format, and many sites have default time limits on how long passwords are viable. Instead, OMEGAMON XE on z/os uses the RACF secured signon function. The secured signon function provides an alternative to the RACF password called a PassTicket. PassTicket is a one-time-only password that is generated by a requesting product or function. OMEGAMON XE on z/os generates a PassTicket for a specific Tivoli Enterprise Monitoring Server (address space) ID when it accesses the DDS to obtain RMF data. To enable OMEGAMON XE on z/os to use PassTicket, a RACF administrator must enable the PTKTDATA class and authorize the address spaces. Detailed instructions for completing these tasks are provided in Enable RMF data collection on page 78. See the z/os Security Server RACF Security Administrator's Guide for a full discussion of PassTicket function and setup. Note: You can choose to bypass user ID and password authentication for the DDS API for all or selected users using initialization parameters. For further information, refer to discussion of the HTTP_NOAUTH in the RMF documentation. Planning configuration of OMEGAMON II for MVS Some of the data reported by OMEGAMON XE on z/os is provided by its OMEGAMON II for MVS component. OMEGAMON II for MVS, in turn, gets much of its data from OMEGAMON for MVS (OMEGAMON "classic"), on which it is built. Sometimes referred to as the realtime collector, OMEGAMON for MVS provides real time data to OMEGAMON II, as well as command-level security services. Configuring the OMEGAMON II for MVS (OMEGAMON II) component is the first step in configuring OMEGAMON XE on z/os. When you configure OMEGAMON II, you generate parameter library entries used in common with the Tivoli Enterprise Monitoring Server and set up the communication between OMEGAMON II and OMEGAMON. You also configure the address spaces for common components such as OMEGAMON Subsystem, the CSA Analyzer, and the End-to-End Response Time feature, which provide services for both OMEGAMON and OMEGAMON II. You can use the OMEGAMON II component as you use the standalone version, using its Common User Access (CUA) interface. You can also access OMEGAMON using its menu-driven interface. However, this guide covers only the configuration steps required to enable OMEGAMON II as a component of OMEGAMON XE on z/os and some additional optional configuration for security and historical data collection. For more information on configuring, customizing, and using OMEGAMON II, see the manuals listed in OMEGAMON II for MVS V520 library on page 138. This documentation has not been updated for this release. However, most of the configuration and customization information contained in these books is still valid. For more information on using the OMEGAMON for MVS component, see IBM Tivoli OMEGAMON XE on z/os: OMEGAMON for MVS User's Guide and the IBM Tivoli OMEGAMON XE on z/os: OMEGAMON for MVS Command Reference. OMEGAMON II for MVS provides separate historical data collection and reporting using EPILOG. You do not need to configure an historical data store for OMEGAMON II for MVS if you do not intend to use EPILOG to collect and report historical data. Chapter 2. Planning for configuration 15