IBM Service Management Suite for z/OS

IBM Service Management Suite for z/OS
Joachim Schmalzried Certified IT Specialist, IBM Software Services Tivoli V

Agenda Service Management Suite for z/OS
BA Cognos 10 Template 9/17/2018 Agenda Service Management Suite for z/OS Introduction IBM Service Management Suite for z/OS Automation Network Management Performance Monitoring Asset Discovery Value through integration What‘s new Summary Prensenter name here.ppt

Smarter Infrastructure
Rapid growth of next generation technologies supported seamlessly on zEnterprise System z scaling model and security to manage and optimize both Systems of Engagement Social, Mobile, Analytics Smarter Infrastructure Systems of Record Business Transactions Quality of Service Command & Control Facts and data “source of truth” z/OS Mobile and Social Dynamic Interactions and Collaboration Insight, trends, analytics Linux on System z Main Point: Much of this Cloud, Mobile and Social innovation is starting to be enabled by new what is called “systems of engagement” that leverage ubiquitous cloud computing models, pervasive tooling and mobile access to bridge traditional IT “Systems of Record” to drive interactions closer to the customers and leverage relationships that are enabled by this shift. The opportunity to capture markets through optimized customer interaction is driving rapid innovation and iteration in the cloud leveraged by these new systems. At the same time infusion of intelligence in physical assets such as automobile, building systems, electrical utilities and traffic control systems, require models that can more easily scale to collect data and deliver content. Systems of Record are characterized by being what we think of as System z today, transactional, database, Command and Control. Systems of Record will be key in providing the data, security and availability needed for the new 24/7 requirements that come from Systems of Engagement. Systems of engagement are the new technologies, and System z can support them just as well. Linux on System z is a great platform that provides the security, availability and reliability of zEnterprise and supports Linux workloads. Both components are needed to successfully implement new business requirements. 3 3

Mainframe customers require ability to quickly correlate and fix problems across applications
Islands of monitoring and automation lead to potentially more outages and higher costs Low automation degree Problems crossing monitors hard to diagnose due to lack of correlation or drill down Higher education, installation and maintenance costs Less flexible sysprog and operations specialists Customer challenges Performance number values – what is good versus bad How to find correct thresholds Problems detected in time versus flooded with exceptions Identify problems before they cause an outage Quickly finding root cause “I’d like my operators to be able to more quickly diagnose certain events and patterns to implement fixes.” “I’d like 30 minutes warning to know when my user experience is going to deteriorate” Islands of monitoring and automation lead to potentially more outages and higher costs as automation can not detect and resolve performance problems before they become outages. Monitoring is used to detect performance problems, however a large number of numbers must be interpreted by the operator to differentiate performance problems that affect service problems from a temporary high load. Thresholds can be used to create exceptions so that operators are not required to monitor screens constantly. However thresholds need to be set right. If a threshold is too low and generates too many exceptions operators will be flooded, annoyed and they will ignore those exceptions. When a real problem develops it will be ignored too. Thresholds also can vary over the day or week depending on load. Complex applications are monitored by different monitors, problems crossing monitors hard to diagnose due to lack of correlation or drill down. Multiple monitors that are not integrated with each other and with automation lead to higher education, installation and maintenance costs and less flexible sysprog and operations specialists. “After we fix the problem, then we set another threshold” “I’d like to adjust for repeating traffic situations” “We have too many thresholds to maintain” 4

Lack of automation can increase costs and risks
Many shops only automate IPL, messages, and shutdown Recovery automated only for single resources without dependencies Complex recovery or moves done by operators leads to higher effort and recovery time Operators not alerted about monitor or automation exceptions Performance problems not solved by automation Subject Matter Experts Service Level Agreements Manual Operations Recovery time Automated Operation Lack of automation or a low automation level requires that recovery or moves have to be done by operators which leads to higher effort and recovery time, often exceeding the time allowed in Service Level Agreements. If automation does not notify operators about an exceeded threshold, broken resources or critical messages, valuable time is lost and operator productivity is low as they have to monitor many consoles and enter many commands to detect and diagnose problems. When recovery actions must be taken by operators or Subject Matter Experts, more time is required as everything is manual. At the bottom recovery actions are listed. Their complexity increases from left to right. A low automation level only covers basic message automation and recycling resources. Dependant resources are unknown to automation so that recovery fails as resources are recovered in the wrong order or on the wrong systems where prerequisites are not met. More complex recovery actions, like unlocking resources, killing resources that consume too many resources, resetting resources that do not work or offloading logs and data have to be done by the operator which is a lot slower, executed too late or incorrectly. Subject Matter Experts then will do root cause analysis by analysing logs and history or by doing a fallback to working configurations or maintenance levels. Adding resources like more application servers, more disk, more CPU or more RAM is also a complex recovery action. Complexity Message automation Recycle resource Application recovery Application move Unlock Kill Reset Offload Analysis logs, history Correct configuration Reinstall Fallback Add resources

High automation level can decrease costs and risks
Complex recovery or moves done by automation – fast and reliably Operators alerted about monitor or automation exceptions Pro-active automation using monitoring can resolve performance problems before they cause outages Operators and SMEs can solve problems faster by using automation to manage applications Service Level Agreements Subject Matter Experts Recovery time Manual Operations Alarm Pro-active Automation using Monitoring With a high automation level operators are relieved and recovery time is significantly reduced as more complex recovery is done by automation, fast and reliably. Operators are alerted about monitor or automation exceptions so operators do not have to monitor many consoles and are not required to enter many commands to detect and diagnose problems. Pro-active automation using monitoring can resolve performance problems before they cause outages. Automation does notify operators about an exceeded threshold, broken resources or critical messages, valuable time is saved, operator productivity is high as they do not have to monitor many consoles and enter many commands to detect and diagnose problems. When recovery actions must be taken by operators or Subject Matter Experts, less time is required as automation can be used to restart or move applications, fast and reliably. Dependent resources are known to automation so that recovery succeeds as resources are recovered in the right order and on the right systems where prerequisites are met. More complex recovery actions, like unlocking resources, killing resources that consume too many resources, resetting resources that do not work or offloading logs and data can be done by automation which is a lot faster, executed in time and correctly. Adding resources like more application servers, more disk, more CPU or more RAM is also done by automation, fast and reliably. Complexity Message automation Recycle resource Application recovery Application move Unlock Kill Reset Offload Analysis logs, history Correct configuration Reinstall Fallback Add resources

IBM Service Management Suite for z/OS combines monitoring and automation for integrated capability
Tivoli Asset Discovery for z/OS System Automation for z/OS OMEGAMON Performance Management Suite for z/OS NetView OMEGAMON and System Automation work together to provide simplified operations and reduced risk Exploit Tivoli Asset Discovery to better understand application usage and save license charges and address audits Main Point: IBM Service Management Suite for z/OS V1.2 offers a single point of control for a broad range of systems management functions. You get the visibility, control, and automation of a large range of system elements spanning both the hardware and software resources of enterprises in a sysplex. The IBM Service Management Suite for z/OS provides automation, network, and systems management to address business agility on IBM System z. This approach to automating system and application start up, shut down, recovery, response to problems, and disaster recovery can help improve availability and costs on IBM z/OS. IBM Service Management Suite for z/OS leverages broad monitoring values to provide both real-time and historical performance and network management capabilities for your z/OS operating system, networks, storage subsystems, IBM DB2, IBM CICS, IBM IMS, IBM WebSphere MQ for z/OS, and IBM WebSphere Application Server for z/OS IBM Service Management Suite for z/OS V1.2.0 includes: o IBM Tivoli System Automation for z/OS V o IBM Tivoli NetView for z/OS V o IBM Tivoli Asset Discovery for z/OS V o IBM Tivoli Performance Management Suite for z/OS If you have an active license for any of the component products, you have the ability to upgrade to the IBM Service Management Suite for z/OS V1.2 8

Service Management Suite for z/OS V1.2
Provides comprehensive service management capabilities for IBM zEnterprise Simple Pricing metric (One Time Charge PID) to deploy infrastructure and middleware solutions as needed System Automation for z/OS NetView for z/OS Tivoli Asset Discovery for z/OS OMEGAMON Performance Management Suite for z/OS z/OS DB2 CICS IMS MQ Networks Storage WAS Single offering that contains capabilities to manage z/OS and all key subsystems High Availability & Automated Operations to improve Service Levels and reduce system downtime Ability to visualize and automate your mainframe environment as a single system Eliminates boundaries between system and application components Network & Performance Management to increase efficiency of resources and personnel Tools tightly integrated providing pro-active automation, which helps on problem resolution even before an alarm goes off 9 9

zEnterprise management
BA Cognos 10 Template 9/17/2018 zEnterprise management Service Management Suite for z/OS 3270 and graphical user interfaces Integration Pro-active automation Disaster recovery platform NetView for z/OS OMEGAMON Performance Management Suite Asset Discovery for z/OS Network Management Automation platform CANZlog Enterprise monitoring Exceptions Analysis Expert advice History License compliance Software license cost optimization Financial accountability Usage trends System Automation for z/OS High availability Automated operations z/VM Linux LPAR CEC zBX I/O zAware z/OS DB2 CICS IMS MQ Networks Storage WAS Prensenter name here.ppt

Service Management Suite for z/OS V1.2
HIGHLIGHTS Increased efficiency - Enhanced OMEGAMON functions with OM Performance Management Suite V5.3 updates (e.g UI Near Term Historical capability). Improved time to value - Improvement customer experience with a 80% decrease in time of System Automation base installation and configuration. Reduced risk of application downtime with pro-active automation enhancements (out of the box policy-based management of looping address spaces to help SMEs execute various recovery actions without the need for programming.) Increased visibility and improved application availability – Support of ITM pure events helps System Administrators to get situations reported immediately for selected automation resources to allow for corresponsive actions. Pro-active outage prevention through analytics - New Monitoring and Automation integration capabilities enable customers to pro-actively avoid outages through predictive insights analytics and zAware hardware automation support Improved SME productivity – Multiple users are able to customize and browse an automation policy while a configuration built process runs in parallel. 11 11

How are companies thinking about automation today
Customer Concerns: Regular activities that need fast respond Minimize dangerous human activities Reduce risk of outages based on human error React to unexpected events without having a disaster Ability to support different types of activities without change Increase number of events managed with same staff System Automation addresses these concerns. Provides fast response to planned events Minimizes human interactions for error situations Add new capability without having to add resources 13 13

System Automation for z/OS provides
High availability for z/OS applications including UNIX Policy-based plug and play automation using best practices Automated and easier mainframe operation through goal- driven automation and reduced complexity Parallel Sysplex single system image and automation Basis for disaster recovery with Geographically Dispersed Parallel Sysplex (GDPS) Pro-active automation through monitor and OMEGAMON integration Comprehensive integration External automation to initialize, configure, change capacity, recover, and shut down IBM zEnterprise® servers Play Automation provides high availability for z/OS applications including UNIX Policy-based automation is a sophisticated methodology that allows to easily incorporate business goals into an automation framework. IBM ships plug'n play automation that includes best practices automation for many z/OS applications. This can help to: Reduce time and effort in creating a new policy or updating one Improve automation quality and reduce human error Goal-driven automation greatly simplifies operations. System operators just request what they want. Automation takes care of any dependencies and goals that are affected. It can resolve conflicting goals and even can remember goals. Grouping of resources and definition of aggregate or business applications can greatly reduce the complexity of automation definition and operations. Automation is sysplex-wide. Operators can operate from a single point of control and the sysplex appears as a single system image. NetView and System Automation for z/OS are the basis for disaster recovery with Geographically Dispersed Parallel Sysplex (GDPS) Monitor resources enable integration with any monitor and include easy to exploit OMEGAMON access to update the health status of monitor resources which can trigger pro-active automation. Comprehensive integration with z/OS components, for example WLM and ARM, Tivoli products, for example Tivoli Workload Automation and NetCool OMNIbus as well as the rich set of NetView interfaces. External automation to initialize, configure, change capacity, recover, and shut down IBM zEnterprise® servers

System Automation for z/OS - Components
IBM Automation Control for z/OS System Automation for z/OS - Components System Operations Automate repetitive and complex tasks in z/OS systems Helps operators to perform their tasks in a more robust way Reduces z/OS specific skill requirements Automated operations through monitoring of applications, messages, and alerts: Increase availability and performance through pro-active automation Processor Operations Automate and control hardware operations Power on/off and reset Perform system IPL for z/OS, Linux, z/VM, blades Automate LPAR settings like weights and capping System Automation for z/OS has two key components that are designed to automate processor and system operation. These components are called Processor Operations and System Operations. Processor Operations helps operators manage more systems with greater efficiency. This means that one operator, even from a remote location, can configure, initialize, monitor, shut down, and recover a central processor complex (CPC), Logical Partitions (LPAR), and multiple systems in parallel and respond to a variety of detected conditions. An operator, using one standard interface, can do all that across multiple types of systems such as z/OS, VSE, z/VM, and Linux. In addition, automated routines for redundant tasks speed the work of skilled operators and assist less experienced operators in becoming more productive. The System Operations component, running as a NetView application, automates many system console operations and selected operator tasks such as startup, monitoring, recovery and shutdown of z/OS subsystems, components, applications, UNIX (USS), and sysplex resources. IBM Automation Control for z/OS provides comprehensive, out of the box automation for mission-critical software like CICS, DB2, and SAP. The System Operations component also enables you to automate operator console messages, initiate timer-based actions, and prevent shortages of critical z/OS resources. The automation product integrates with Tivoli OMEGAMON to help you to increase availability and performance through proactive automation. © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Component System Operations provides internal automation
IBM Automation Control for z/OS Component System Operations provides internal automation Policy-based automation Start, recover, and shutdown applications, system and sysplex using: Timers, events, triggers, service periods... Dependencies and groups Thresholds, active and external monitors JES, CICS, IMS, DB2, TWS, WebSphere, OMEGAMON, UNIX, SAP, GDPS… Message monitoring & response WTO, WTOR, joblog, UNIX, NetView, hardware Escalation to SA IOM, OMNIbus... Prevent outages of critical resources: WTO and AMRF buffers, spool, sysplex SYSLOG, LOGREC, SMF, dump data sets Easier operations at the application level 3270 or Tivoli Enterprise Portal Single point of control, single system image Goal-driven automation OMNIbus SA IOM SDF TEP Configuration Goals Requests Overrides Status Events Policy Automation Engine Commands Resources Monitor Applications The System Operations component, running as a NetView application, automates many system console operations and selected operator tasks such as startup, monitoring, recovery, and shutdown of z/OS subsystems, components, applications, UNIX (USS), and sysplex resources as well as entire systems and sysplexes (SA z/OS only). The System Operations component provides comprehensive, out-of-the-box automation for mission-critical software like JES, CICS, IMS, DB2, TWS, WebSphere, OMEGAMON, UNIX, SAP and GDPS (SA z/OS only), and many more. Applications can be started or stopped using timers, events, triggers, or service periods. Dependencies can be automatically established. Resources can be member of groups which can greatly reduce the complexity of automation definition and operations. Server groups control which and how many group members are started. Group members can represent, for instance, application servers. Thresholds can be defined to alert operators or stop recovery. Various active monitors including a fast control block scanner and a monitor for UNIX resources are available. Clients can specify their own monitor and interval. Monitor resources can determine the health status using external monitors or OMEGAMON. Messages like Write-to-operator (WTO) or WTOR or even messages from joblogs or UNIX can be automated without writing scripts. Automation can be different depending on codes in the message or depending on how often the message appeared. Escalation to various notification targets can be setup easily using pre-defined or user defined alert points on a resource level to Create incidents in IBM Tivoli Service Request Manager® Create events in IBM Tivoli Netcool® OMNIbus Alarm staff using , pager or SMS using IBM Tivoli System Automation for Integrated Operations Management The System Operations component provides automation procedures that enable recovery of the following z/OS components and data sets: SYSLOG data sets LOGREC data sets System Management Facility (SMF) data sets Write-to-operator (WTO) buffers JES spools z/OS dump data sets Action Message Retention Facility (AMRF) buffers Sysplex resources, for example, coupling facility (SA z/OS only) All you have to do is specify to System Operations in an ISPF dialog what resources you wish to automate and monitor, and what your policies are for automation and monitoring. The automation engine, which is identical on all systems, will then start, monitor, recover, and shutdown resources and complex applications according your configuration and goals. At any time, the operator can monitor and control from an enterprise-wide single point of control at the application level. You have the choice of using a 3270 based NetView console or the graphical user interface of the Tivoli Enterprise Portal. Both are easy to use, powerful and provide a common interface for all types of resources. When exceptions occur or goals have to be changed, an operator just issues requests and overrides. SA z/OS offers a sysplex single system image, system boundaries are removed. Goal-driven automation greatly simplifies operations. Operators just request what they want, and automation takes care of any dependencies and resolution of affected or even conflicting goals. UNIX Sysplex Job/STC Logs I/O System © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Summary of key automation technologies
IBM Automation Control for z/OS Summary of key automation technologies Play Policy-based automation can replace scripts Plug and play automation using best practices Powerful sysplex-wide automation and operation Goal-driven automation to keep applications in line with business goals Grouping of resources for reduced complexity and management at business application level Relationships between resources for accelerated startup and shutdown, and correct recovery Manage by resource state, not by message Integration with monitors and OMEGAMON Health status can trigger pro-active automation Manager / agent design Same automation concepts enterprise-wide MyWeb Web DB VIPA ForceDown HasParent Web DB VIPA Summary of key automation technologies Policy-based automation is a sophisticated methodology that allows to easily incorporate business goals into an automation framework. As the term implies, policy-based automation uses simple policy statements, with no program scripting or special education required. Policy-based automation includes resource information, groups of resources, and relationships in the decision-making process prior to taking action. Resource information defines resource class and name; how to start, stop, and monitor the resource; and what the preferred systems are (SA z/OS only) . Resources can be members of cluster-wide (SA z/OS only) groups and relationships. IBM ships plug'n play automation that includes best practices automation for many z/OS applications. This can help to: Reduce time and effort in creating a new policy or updating one Improve automation quality Goal-driven automation greatly simplifies operations. System operators just request what they want. Automation takes care of any dependencies and goals that are affected. It can resolve conflicting goals and even can remember goals. Relationships between resources for accelerated startup and shutdown, and correct recovery Resources can have complex dependencies of different kinds inside and outside of an application. This gives you the power to define these dependencies, so that applications get what they need, are started in the right order as quickly as possible and are shut down fast without interference. Grouping of resources and definition of aggregate or business applications can greatly reduce the complexity of automation definition and operations. Exploiting groups is beneficial in many ways: Automation definition and operations can be greatly simplified through the grouping of resources and even business-application definitions. Groups let you monitor important business applications and help verify that everything they require is available. Groups can make operations easier by showing the aggregated status of resources and by group actions such as startup or shutdown. Through groups, operators are freed from knowing the various pieces that make up an application, their dependencies, how to start or stop them and so on. Server groups control which and how many group members are started. Group members can represent, for instance, application servers. Manage by resource state, not by message Operators can manage at the resource and even application level using the resource state rather than by watching messages and determining what they mean. Automation knows about resources and keeps track of their status using more than 20 different states and therefor knows exactly what‘s going on and what the options are. Although automation uses messages to update the status and also can automate messages, it is the status change that triggers automation, for example dependent resources are started after the parent is up or a dependent resource is forced down when the resource it is dependent on terminates. Also messages are forgotten, but the status is preserved even across restarts and IPLs. Monitor resources enable integration with any monitor and include easy to exploit OMEGAMON access to update the health status of monitor resources which can trigger pro-active automation. The health status of monitor resources is propagated along monitor relationships to applications and is aggregated into the compound status which reflects the overall resource status. Elements of the automation engine are separated. Those that observe, react and take action remain within the IBM Tivoli NetView address space. Known as the automation agent, this portion must be present on every system to be automated. The coordinating, decision-making and controlling elements are grouped into a single address space known as the automation manager. It is loaded with a model of the automated resources defined across the Parallel Sysplex cluster or system. The automation manager communicates with the automation agent on each system through XCF (Cross-System Coupling Facility). It receives updates about the status of resources in its automation model and sends orders to the agent when various conditions within the model are encountered. The IBM Tivoli Automation Control automation manager communicates only with the automation agent in the same system wheras the IBM Tivoli System Automation for z/OS automation manager communicates with all automation agents in the Parallel Sysplex. You have the same automation concepts across your enterprise. Tivoli System Automation for Multiplatforms runs on Solaris, AIX, or Linux cluster. IBM Tivoli System Automation Application Manager provides cross cluster and cross platform automation and Automation Control and IBM Tivoli System Automation for z/OS run on z/OS. All are policy driven, have the same automation manager, goal-driven automation, groups, relationships between resources and so on. © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

IBM Automation Control for z/OS
What can you automate? Automate messages Prevent outages of critical resources Start, recover, and stop z/OS resources STCs, jobs… UNIX System Services (USS) resources Easier z/OS operations and monitoring Change system run mode like day or night shift Escalation of problems Pro-active automation using integration with monitors Integration with scheduling Problem determination DB2, CICS and IMS automation These are typical automation scenarios: basic ones like automating messages, starting, recovering, and stopping z/OS resources and advanced ones like System run modes and pro-active automation using integration with monitors Prevent outages of critical resources like JES spool, logrec, page datasets or syslog Easier z/OS operations and monitoring Escalation of problems to a status console or via alerting Integration with scheduling Problem determination DB2 automation CICS automation © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Operator user interface – Tivoli Enterprise Portal
IBM Automation Control for z/OS Operator user interface – Tivoli Enterprise Portal Tivoli Enterprise Portal is the integration point for monitoring OMEGAMON XE Tivoli Monitoring Tivoli composite application monitors Automation Control adds its operational views to the TEP presented side by side with availability data Capabilities Resource overview, health and status item workspaces Situation monitoring and visualization Graphical summaries combined with detailed tabular views Context-sensitive linking between workspaces Display critical messages and WTORs Display topology view Tivoli Enterprise Portal Support The Tivoli Enterprise Portal (TEP) support allows you to monitor the status of automation on z/OS systems and z/OS sysplexes (SA z/OS only) using a TEP client. The client is the user interface for the monitoring agents. The monitoring agent uses the Tivoli Monitoring Services infrastructure, which provides security, data transfer and storage, notification mechanisms, user interface presentation, and communication services for products in the IBM Tivoli Monitoring and OMEGAMON XE suites in an agent-server-client architecture. The monitoring agent is installed on the systems that you want to monitor and passes data to a hub Tivoli Enterprise Monitoring Server (monitoring server), which can be installed on z/OS, Windows, and some UNIX operating systems. The monitoring server communicates with the Tivoli Enterprise Portal Server (portal server), which then communicates with the portal client. The TEP is also the integration point for monitoring OMEGAMON XE, Tivoli Monitoring and the Tivoli composite application monitors. With the automation product the operational views are added to the TEP via several workspaces. On these workspaces you get an overview on the resources with all their different states. The graphical summaries are combined with the detailed tabular views. You can jump directly from one workspace to another using the context sensitive links. Additional you see information like the outstanding WTORs and the relationships with the topology view. The automation workspaces are display only but are extendable by take actions for start, stop, etc. All automation objects and attributes are available for OMEGAMON situations. When the specified condition consisting of specific attributes of specific objects becomes true, the situation is visualized on the TEP to alert operators. Expert advice and simple actions can be defined too. © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Tivoli Enterprise Portal workspace
IBM Automation Control for z/OS Tivoli Enterprise Portal workspace Request Summary: Graph of vote status for all resources. Compound Status Summary: Graph of resources by Compound Status. 3 80 2 The Resource Overview workspace provides an overview of resources, their state and requests to them. The predefined workspace contains the following views: The Request Summary bar chart shows the distribution of request types (start vs. stop, winning vs. losing) across all requests . A link is provided to navigate to the Resource Requests workspace for detailed information about the requests. The Compound Status Summary bar chart shows the distribution of compound states across all resources. The Resource List table lists all resources, the various automation states, and other descriptive information. Links are provided to navigate to the Resource Details workspace for further details about a particular resource or to navigate to the Resource Requests workspace for detailed information about the requests. Filter support Special filter support exists for the Resource Overview workspace because this list can be extremely large. Although all filtering is done on the Tivoli Enterprise Portal (TEP) side, some filters for this workspace are also implemented on the NetView side. This can help reduce the amount of data that must be transferred from the automation manager. The following filters are supported: Operand may be equal to or contained in the resource name. Operand may be equal to or contained in the resource type. Operand may be equal to or contained in the resource system. Status may be equal to the compound, observed, or health status and a multiple of such expressions are logically ORed. Status may be not equal to the compound, observed, or health status and a multiple of such expressions are logically ANDed. Combinations of different attributes are only allowed within a single filter row, that is, the attributes are logically ANDed. © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Tivoli Enterprise Portal Resource Topology
IBM Automation Control for z/OS Tivoli Enterprise Portal Resource Topology IBM Tivoli Enterprise Portal (TEP) topology view The new TEP topology view that combines the dependency graph with the resource status and other important run-time data about the resource managed and automated by IBM Tivoli System Automation for z/OS allows operators to notice odd system behavior. The view can also be used by the automation administrator to spot misconfiguration but also to verify the correct relationship definitions previously made in the customization dialog. Resource Topology workspace The Resource Topology workspace displays dependencies between the resource in focus and other resources. Four modes are available: Start Dependencies - displays all resources that need to be up so the resource in focus can be started Stop Dependencies - displays all resources that need to be down so the resource in focus can be stopped Group Dependencies - displays all groups where the resource in focus is a member of and, if this resource is a group, all of its members and sub-members All Dependencies - displays all resources that have direct dependencies with the resource in focus. The predefined workspace contains the following views: The Resource List lists all resources as in the Resource Overview workspace The Resource Topology shows a graphical view of resource dependencies. © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Component Processor Operations provides external automation
LPAR startup, recovery, and shutdown z/VM guest system support LPAR capacity & weight management Power management IBM zEnterprise management (zBX) Secured through SNMP V3 encryption and SAF protected access Central processor complex (CPC) z/OS Linux z/OS z/VSE z/VM z/VM PR/SM PR/SM HMC/SE SNMP API Processor operations Processor Operations is based on System Automation for z/OS. Processor Operations runs on the NetView platform and controls the logical partitions, system images, blades, and virtual processors, that is, IBM System z or IBM zEnterprise® with the optionally attached zEnterprise BladeCenter ExtensionBladeCenter® (zBX). Processor Operations can startup, recover, and shutdown LPARs including z/VM guests. LPAR capacity & weight management as well as power management is possible with NetView automation capabilities SA z/OS ProcOps uses the SNMP protocol to communicate to HMC/SEs. Problem: SNMPv2 (SA 3.4 and older) - security has been the biggest weakness of SNMP since the beginning. Authentication in SNMP Versions 1 and 2 amounts to nothing more than a password (community string) sent in clear text between a manager and agent. Solution: SNMPv3 makes no changes to the protocol aside from the addition of cryptographic security: Confidentiality - Encryption of packets to prevent snooping by an unauthorized source. Integrity - Message integrity to ensure that a packet has not been tampered with in transit including an optional packet replay protection mechanism. Authentication - to verify that the message is from a valid source. SA z/OS ProcOps

Component Processor Operations provides:
IBM Automation Control for z/OS Component Processor Operations provides: External Automation IML & IPL (NIP time) Respond to System or Operator Console messages Set time of day clocks Detect and resolve wait states CPC capacity changes, powermode control Server Time Protocol and LPAR management Hardware status changes and alerts Single point of control for System z Ease of Use Common commands for: CPCs, LPARs, zBX blades, systems, and z/VM guests z/OS, Linux, z/VM, z/VSE, z/TPF Easy to configure NetView and SNMP based, no PC required Central processor complex (CPC) z/VM z/VM PR/SM PR/SM HMC/SE SNMP API Processor operations Processor Operations is based on System Automation for z/OS. Processor Operations runs on the NetView platform and controls the logical partitions, system images, blades, and virtual processors on the local processor, that is, IBM System z or IBM zEnterprise® with the optionally attached zEnterprise BladeCenter ExtensionBladeCenter® (zBX). Tivoli System Automation for z/OS can manage remote processors. You can perform initial program load (IPL), set the time of day clock, respond to hardware messages, monitor hardware status, and detect and resolve wait states. Processor operations can help operators manage more systems with greater efficiency by providing external automation and a single point of control which is easy to configure and easy to use. One operator in one location can initialize, configure, monitor, shut down and recover multiple systems—both local and remote—and respond to various detected conditions. Using one standard interface, the operator can do all that across multiple types of systems. Automated routines for frequently used functions can speed the work of a skilled operator and help less-experienced operators become more productive. Automation Control and System Automation for z/OS are the only products that provide one platform for internal and external automation at z/OS runtime and at IML and NIP time when internal automation is not yet available. Highlights include LPAR Capacity Management, power mode control, and support for Linux as a z/VM guest. Management is done with direct service element (SE) connection via SNMP and the Hardware Management Console (HMC) API, no PC is required. With the ensemble processor operations commands you can discover, monitor and manage the advanced hardware features like blades, virtual servers and workloads. ProcOps © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

IBM Automation Control for z/OS
Hardware scenarios Easier hardware and operating system operations and monitoring IPL z/OS (and other System z operating systems) Shutdown z/OS Recover systems Address software cost challenges and lower performance when LPAR is capped LPAR configuration Manage temporary processor capacity and server time Energy control Trap hardware alerts © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

ProcOps Hardware Management Console Tasks
IBM Automation Control for z/OS ProcOps Hardware Management Console Tasks Support Elements and Hardware Management Consoles of System z and zEnterprise IBM mainframes provide the facilities for day-to-day HW operation, configuration, maintenance, problem determination, console user access, logging, and many other tasks. In addition, the SE/HMC Console Application supports a number of APIs. They allow HMC/SE task execution to be initiated by a computer program, rather than using the console GUIs, available for manual SE/HMC operation. The System Automation for z/OS component Processor Operations exploits the TCP/IP - SNMP based “System z Programming Interfaces” API. SA z/OS itself requires NetView z/OS, with its rich set of automation facilities. With the ISQCCMD Hardware Common Command Interface, ProcOps has simplified the HMC task operation and provides it as an API on the same platform used for z/OS System Operations. © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Do your own smart capping and load distribution
IBM Automation Control for z/OS Do your own smart capping and load distribution Group Capacity Limit Software cost challenges: Charges based on peak rolling 4 hour average or the LPAR Defined Capacity whichever is lower Capping might cap priority workload Solutions using SA z/OS: Move workload to under-utilized system using server/move groups based on Predicted free capacity and WLM data Using OMEGAMON metrics Use ProcOps API to adjust capacity across LPARs and WLM capacity groups automatically Policy-based looping jobs resolution LPAR 1 LPAR 1 LPAR 2 Capacity in MSU LPAR 2 slow LPAR 3 LPAR 3 System 3 System 2 System 1 Free, Displaceable Capacity Many clients face Software cost challenges that they try to resolve with sub-capacity pricing for Variable Workload License Charges (VWLC) software that is based upon monthly peak rolling 4 hour average (R4HA) usage measured in MSUs (Millions of Service Units) and LPAR size definitions (LPAR Defined Capacity). When the R4HA becomes higher or equal to the Defined Capacity then the LPAR is capped by the z/OS Workload Manager (WLM) which slows down the system and priority workload. Clients can use IBM Tivoli System Automation for z/OS capabilities to avoid extra VWLC charges during peak hours by Automatically moving low priority workloads to systems with free capacity Providing just-in-time cushioning of the R4HA Adjusting LPAR Weights on behalf of IBM Capacity Provisioning Manager for z/OS Adjusting capacity across LPARs and WLM capacity groups automatically Moving workload to under-utilized system based on the predicted free capacity and WLM data or based on OMEGAMON metrics A policy-based solution for active suppression of looping address spaces 5. Moving workload to under-utilized system based on the predicted free capacity and WLM data, called Resource aware Application Management Existing processing capacity is used more efficiently Load situation of z/OS systems considered when moving applications when more then 1 system is eligible with the same preference AM queries periodically WLM capacity of all systems SA z/OS tries to estimate how the number of free MSUs will change after each start operation z/OS Workload Manager (WLM) Goal-driven workload management Based on business priorities Grants resources (CPU, I/O, memory) across LPAR clusters SA z/OS incorporates WLM information into its automation framework Gains an understanding of existing available capacity Knows from WLM where to move applications based on priorities and available capacity to adapt to increased workloads Knows where to restart failed applications Background: Sub-capacity Pricing (see Software expense for a product is determined by utilization of LPARs where that product executes  Total utilization of LPAR, not utilization of individual product Utilization is calculated as 4 hour rolling average (4HRA)  Measured in MSUs (Millions of Service Units) Charges based on peak 4h rolling average or the LPAR Defined Capacity whichever is lower Billing month is 2nd calendar day of one month through 1st day of following month Capping Technologies Initial Capping (“hard cap”)  Sets capacity limit always enforced by WLM Defined Capacity/DC (“soft cap”)  Current utilization can exceed DC as long as 4HRA < DC  When 4HRA reaches DC, WLM caps LPAR at DC until 4HRA drops below DC  4HRA can exceed DC but SW is never billed above DC Group Capacity Limit (“group cap”)  Soft cap concepts applied to a group of LPARs on same CPC Absolute Capping Limit (zEC12 GA2)  Expressed in terms of 1/100ths of a processor © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Automatic CPC & LPAR capacity changes
IBM Automation Control for z/OS Automatic CPC & LPAR capacity changes ProcOps Management API to: Query current CPC configuration details Query and set LPAR-specific controls Query and set the default CPC RESET activation profile Manage RESET, IMAGE, and LOAD activation profiles Automate IPLs from SCSI devices (Linux, z/VM) Allows you to automate based on schedule, workload, application LPAR weight (defined, initial, minimal, maximal, current (R/O)) Defined capacity to lower your software costs Provisioning of new CPs to adapt to increased workload Reserve of CPC (or reserve query) Switch between WLM and PR/SM management IPL profiles for easier operations ISQCCMD target_system_ProcOps_name ICNTL target_hardware_name.lparname CMD(UPDATE) VAR(vnm) VAL(vvl) The killer function is that Processor Operations allows you to change LPAR weights based on schedule, workload, application... This can be used to change defined capacity to lower your software costs. Background: A System z LPAR can be assigned resources like CPU, memory, weight for WLPM LPAR CPU management, etc. The problem is that often applications are licensed by capacity, sometimes calculated as average. Clients often need temporary higher capacity, for example for quarter end processing or for a marketing campaign. If they exceed their allowed capacity they must either pay extra or reduce to a lower capacity to meet the average they are licensed for. © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Summary System Automation
IBM Automation Control for z/OS Summary System Automation Business applications require high availability Downtime can cause lost sales and customer shifts to competitors Automation provides high availability for z/OS applications including UNIX Policy-based plug and play automation using best practices can replace scripts Faster time-to-value Much reduced maintenance burden Less human error Goal-driven automation to keep applications in line with business goals Grouping of resources for reduced complexity and management at business application level Status aggregation Server and move groups help achieving availability targets Relationships between resources for accelerated startup and shutdown, and correct recovery Manage by resource state, not by message Integration with monitors and OMEGAMON to increase automation degree with pro-active automation Play Business applications require high availability as downtime can cause lost sales and customer shifts to competitors. Automation provides high availability for z/OS applications including UNIX Policy-based automation is a sophisticated methodology that allows to easily incorporate business goals into an automation framework. IBM ships plug'n play automation that includes best practices automation for many z/OS applications. This can help to: Reduce time and effort in creating a new policy or updating one Improve automation quality and reduce human error Goal-driven automation greatly simplifies operations. System operators just request what they want. Automation takes care of any dependencies and goals that are affected. It can resolve conflicting goals and even can remember goals. Grouping of resources and definition of aggregate or business applications can greatly reduce the complexity of automation definition and operations. Exploiting groups is beneficial in many ways: Automation definition and operations can be greatly simplified through the grouping of resources and even business-application definitions Groups let you monitor important business applications and help verify that everything they require is available Groups can make operations easier by showing the aggregated status of resources and by group actions such as startup or shutdown Through groups, operators are freed from knowing the various pieces that make up an application, their dependencies, how to start or stop them and so on. Server groups control which and how many group members are started. Group members can represent, for instance, application servers. Relationships between resources for accelerated startup and shutdown, and correct recovery. Resources can have complex dependencies of different kinds inside and outside of an application. The automation product gives you the power to define these dependencies, so that applications get what they need, are started in the right order as quickly as possible and are shut down fast without interference. Manage by state, not by message Automation knows about more than 20 different states and therefor knows exactly what‘s going on and what the options are. Although automation uses messages to update the status and also automate messages, it is the status change that triggers automation, for example dependent resources are started after the parent is up or a dependent resource is forced down when the resource it is dependent on terminates. Also messages are forgotten, but the status is preserved even across restarts and IPLs. Monitor resources enable integration with any monitor and include easy to exploit OMEGAMON access to update the health status of monitor resources which can trigger pro-active automation. The health status of monitor resources is propagated along monitor relationships to applications and is aggregated into the compound status which reflects the overall resource status. © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

BA Cognos 10 Template 9/17/2018 Agenda Service Management Suite for z/OS Introduction IBM Service Management Suite for z/OS Automation Network Management Performance Monitoring Asset Discovery Value through integration What‘s new Summary 29 Prensenter name here.ppt

NetView for z/OS network management and automation
NetView ® for z/OS provides functions to help maintain the highest degree of availability for IBM System z networks. It provides: an extensive set of tools for managing complex, multi-vendor, multi-platform networks and systems from a single point of control advanced automation facilities for network events support for both IP and SNA network componentry a set of user interfaces to meet the needs of any user and management functions that work with other products to provide a complete picture of your networks and systems NetView provides automation, and network and systems management to address today’s requirement for business agility on System z Provides key capabilities and advanced functions related to networking and automation, enhanced enterprise integration, customer time-to-value and ease of use, as well as management functions that work in cooperation with other products. Supports heterogeneous networks that include both SNA and TCP/IP and supports changing network and system requirements that exist on System z. NetView provides the ability through a single console to manage your entire network. 30

Automation and network management
Enterprise Network Management from a Single Point of Control At-a-glance status determination via network topology displays Manage TCP/IP and SNA key performance indicators via single consolidated interface Proactively identify and respond to network intrusions Filter out network noise and focus on key issues impacting your network Maximize Availability of Business-Critical Services Minimize service and system outages Identify recurring incidents, and implement automated actions to prevent future occurrences Assist operators with detecting and resolving incidents at the point of failure Improve Operational Efficiency and Performance of IT Assets and Staff Reduce recovery time and need for operator intervention Automate for repeatability and reduced potential for user error Develop standardized practices for complex business processes, ensuring consistent handling of incidents (quality) Tailor NetView capabilities to meet your needs via flexible APIs and services

NetView for z/OS, the automation platform
NetView for z/OS has extensive automation facilities: Automation table (IF … THEN ….) Message revision table to revise messages Automation tasks for isolation and load distribution Timers Unlimited sources and targets of automation Rexx scripts with automation function packages Powerful pipes instead of scripts You can automate from: Messages (VTAM, z/OS, JES, NetView, user, etc.) - solicited and unsolicited Alerts (SNA and non SNA) Full screen applications, SNMP traps, TEC events NetView for z/OS is a powerful the automation platform both for network and system automation. The automation table enables you to respond automatically to messages and management services units (MSUs). You can issue a response in the form of a command, command list, or command processor. You can also set attributes and processing options. For example, you can suppress, log, or route messages and block, record, or highlight MSUs. The message revision table (MRT) enables you to intercept MVS messages before they are displayed, logged, automated, or routed through your sysplex. You can make decisions about the message based on its message ID, job name, and many other properties. You can issue timer commands to schedule activities many days in advance or to schedule an activity that takes place once a day or once a month. Use a timer command to schedule another command: After the lapse of a specified time At a specified time Repeatedly at specified intervals Automation tasks or autotasks can receive messages, process commands and command procedures, and establish NetView program to NetView program sessions. Autotasks can run full screen commands using the NetView program full screen automation function. NetView has almost unlimited sources and targets of automation. Events can be processed from the network and the system as well as from jobs and applications as well as USS logs and remote agents. Likewise it can use many APIs to issue commands, send or log events and s, create SNMP traps, and interfaces with other systems management products. NetView supports Rexx scripts extended by NetView functions to issue commands, trap messages, do I/O and more. Rexx scripts are usually interpreted but can be compiled or loaded into main storage to improve performance. NetView pipelines help you solve a complex problem by dividing the problem into a set of smaller, simpler steps. Each step orstagehandles one part of the overall problem. PIPE stages can: Read data from system sources, such as files on DASD or variables in command procedures. Filter and refine the data. Export (output) the data from the pipeline. You can connect stages in logical sequence until they collectively cover all steps required to solve your problem. You can automate solicited and unsolicited messages from z/OS and subsystems, SNA and non SNA Alerts as well as full screen applications, SNMP traps, and TEC events. 32

NetView v6.2 continues IBM’s focus on enhancing network and system availability and ease-of-use
Enhanced IP Management Improved access to IP functions: New IP Management Menu Simplified navigation through packet trace data Support for multiple, concurrent packet traces per stack Save packet traces in CTRACE format Faster Problem Repair Expanded integration and central-site access to consolidated logs from multiple z/OS systems Integration of System z analytics (zAware) Automated problem detection Determine the health of your environment through Log Analysis Surface anomalies with high confidence New in NetView V6.2.1 The conditional %INCLUDE statement allows the conditional inclusion of members The MODIFY.TOWER statement enables or disables the specified towers and subtowers, without affecting the definitions of those towers and subtowers. Advanced Encryption Standard (AES) can be used for encryption of SNMP v3 requests sent and received using the SNMP command The Discovery Manager now supports OSA-Express 5S NEW with v6.2.1 (GA’ed on September 5th, 2014) Easier customization through conditional %INCLUDE and MODIFY.TOWER Advanced Encryption Standard (AES) can be used for de/encryption of SNMPv3 requests The Discovery Manager now supports OSA-Express 5S 33 33 33

Enhanced IP management
BA Cognos 10 Template 9/17/2018 Enhanced IP management Improved Access to IP functions: New IP Management Menu Support for multiple, concurrent packet traces per stack Save packet traces in CTRACE format Client Value Analysis of packet trace data reduces the diagnostic time as well as mean time to repair for network problems Customize presentation of potential issues, focusing network operators on key indicators The new menu minimizes the need for operators to memorize command syntax or refer to command help. The menu also helps keep operators familiar with the IP management functions in NetView without having to remember many different commands. Multiple packet trace support per stack: Tivoli NetView for z/OS V6.2.1 extends capabilities for collecting, controlling, and viewing packet traces by allowing for multiple concurrent traces in the same z/OS Communications Server image (stack). This means that multiple traces, each using different trace criteria, can execute simultaneously on a given stack, and can be controlled and viewed from NetView. Multiple problems can be diagnosed at the same time without causing conflicts Multiple traces can be set with specific filters when diagnosing a single problem Each trace instance runs on a separate autotask Up to 32 separate traces Requires z/OS v2.1 Prensenter name here.ppt

CANZLOG: Consolidated Audit, NetView and z/OS Log
Netlog Syslog Consolidated log NetView console Customer Value Single interface to a consolidated message file reducing diagnostics time Single consolidated console to manage key performance and availability indicators Access both real time and archived logs via single interface, even remotely Filter on time, jobname, codes... CANZLOG Remote Canzlog NetView CANZLOG consolidates these logs and provides convenient browsing through a single, easy-to-use UI, with highly flexible search and filtering criteria. What’s new in V6.2? CANZLOG now has the capability to display log for a specific interval of time. A user can use a 'FOR' option and specify a 'TO' or 'FROM' field to display only an interested interval subset of log. Value If an operator needs to browse an hour of the log, CANZLOG filtering can be used to display this log using a FROM and a FOR (or) a TO and a FOR. Operators can save a filter with just a FOR value. Whenever this filter is called, a default TO is assumed, the TO value being the time of execution of the command. Joblogs CANZLOG = Consolidated Audit, NetView and z/OS LOG

CANZLOG v6.2: relative time specification
Messages from TCP/IP for first 2 hours after midnight today This specification will match any job whose names begins with tcpip. What’s new? CANZLOG now has the capability to display log for a specific interval of time. A user can use a 'FOR' option and specify a 'TO' or 'FROM' field to display only an interested interval subset of log. Value If an operator needs to browse an hour of the log, CANZLOG filtering can be used to display this log using a FROM and a FOR (or) a TO and a FOR. Operators can save a filter with just a FOR value. Whenever this filter is called, a default TO is assumed, the TO value being the time of execution of the command. The trailing D, H and M represent DAYS, HOURS and MINUTES respectively. If none are specified, the given input digits are considered as minutes. If trailing end-character in an argument is missed, the character next in the sequence is assumed. These arguments should be entered sequentially without spaces in between them. For example, 3D12 is interpreted as 3 days and 12 hours 1 is interpreted as 1 minute 1h2 is interpreted as 1 hour and 2 minutes FOR values are converted to minutes internally. Maximum allowed FOR value would be 730 days.

CANZLOG v6.2: browse and filter remote log
Browse records from the Canzlog at CNM01 that are from the jobnames beginning with “tcpip”. Target: a remote NetView instance. Can be: a NetView domain name, or Group name Sysplex name an alias defined using the RMTSYN and RMTALIAS statements in stylesheet. 37 37

CANZLOG v6.2 Source Date Time Mtype Origin 38
SOURCE = jobname or operatorID MTYPE = message type (from HDRMTYPE) ORIGIN = For MVS messages, the origin system name. For NetView messages, the origin domain name. DATE, TIME and SOURCE (and *NONE*) were available in NetView New in NetView V6.2 are MTYPE, ORIGIN, and DEFAULT. HDRTYPET (*): Indicates a command issued to NetView from a NetView terminal. This message type indicates that the buffer is a command rather than a message. HDRTYPEN (-): Indicates a regular single-buffer message from NetView. HDRTYPEE (E): Indicates a message from the operating system. Source Date Time Mtype Origin 38 38 38 38

BA Cognos 10 Template 9/17/2018 Challenges IT Budget Investment shifting to cloud; expecting to stabilize and significantly reduce costs Cost of administering contracts, adjusting sub-cap licensing Need to standardize on one tool set, rationalize vendors, solutions Skills Need to extend reach of sysprogs/admins with an integrated set of tools Technology Existing monitors may not be current with the platform/subsystem Need to integrate z/OS and distributed/cloud monitoring and management 40 Prensenter name here.ppt

Maximizing time and personnel
BA Cognos 10 Template 9/17/2018 Maximizing time and personnel VISIBILITY CONTROL AUTOMATION Increase ability to meet SLAs by managing environment with intelligent alerting Increase staff productivity through managing by exception Maximize efficiency of staff with Common Tools and Processes Create collaboration through tool integration and information Efficiency in doing the day to day management - Link actions to situations Automate problem responses Capture expert knowledge Common data and KPIs 41 Prensenter name here.ppt

IBM Tivoli OMEGAMON Performance Management Suite for z/OS v5.3.0
BA Cognos 10 Template What is OM Performance Management Suite for z/OS? 9/17/2018 IBM Tivoli OMEGAMON Performance Management Suite for z/OS v5.3.0 DB2 Storage (DASD and Tape) Networks (TCPIP / VTAM) CICS / CICS TG IMS DB/DC Messaging (MQ) WAS on Z z/OS Operating System Tivoli OMEGAMON Performance Management Suite for z/OS provides an integrated solution with extensive capabilities to manage on-line and middleware sub-systems like CICS, DB2, IMS WAS on z/OS and the z/OS Operating System, Networks and Storage which supports these capabilities 42 Prensenter name here.ppt

Why OM Performance Management Suite for z/OS?
BA Cognos 10 Template 9/17/2018 Why OM Performance Management Suite for z/OS? Single PID offering that contains the System and Resource level monitoring capabilities needed to Manage z/OS and all key subsystems One stop shop for all your mainframe monitoring needs Simple Pricing metric (z/OS VU’s) enabling customers to deploy infrastructure and middleware solutions as needed. Buy for the size of your environment and you have everything you need - Provides a price incentive with a single vendor to consolidate all of our z/OS Management needs. Our solution costs less than what you’re spending with your multi-vendor solution today Provides a foundation offering for further Analytics and C&SI solutions in the future Foundation for today and tomorrow 43 Prensenter name here.ppt

Complete zEnterprise Monitoring Solution
Monitoring and Management with: OMEGAMON Performance Management Suite for z/OS OMEGAMON XE for DB2 PE V5.2 OMEGAMON XE for Messaging for V7.3 OMEGAMON XE for CICS V5.3 OMEGAMON XE for IMS V5.1 OMEGAMON XE for z/OS V5.3 OMEGAMON XE for Mainframe Networks V5.1.1 OMEGAMON XE for Storage V5.3 OMEGAMON DE for z/OS V5.3 ITCAM AD V7.1 (only ITCAM for WR component) Manage System and Subsystems from single view Exploit Enhanced 3270 User Interface Resource monitoring for DB2, IMS, WAS, MQ, Networks and Storage 44 44

OMEGAMON Performance Management Suite v5.3
OMEGAMON Performance Management Suite includes capability to gain improved visibility and management for z/OS and subsystems CICS, DB2, IMS, Messaging, WAS, Storage, Mainframe Networks Efficiency and cost saving through integration, version 5.3 comes with integrated monitoring with both Enhanced 3270 User Interface and Tivoli Enterprise Portal Increased problem determination capability with Enhanced 3270 User Interface Near-Term-History function Simplification - ordering, pricing and all the components that would ever be needed are included which covers current and future needs as your z/OS environment grows and expands Reduced time-to-resolution of problems with new embedded data function Lower Cost of Ownership with simplified Install/Config with Parmgen enhancements for first time users up to 60% less time and effort Main Point: OMEGAMON V5.3 provides new levels of visibility into the entire IT environment across z/OS and subsystems (CICS, IMS, DB2). We have updated a number of our OMEGAMON products: OMEGAMON XE for z/OS V5.3, OMEGAMON XE for Storage V5.3, OMEGAMON XE for Messaging for z/OS V7.3 Efficiency and cost saving through integration, Personnel efficiency improvements with an integrated management tool set and reduction in cost of computing resources through more efficient management and less down time. Increased problem determination capability for users of the Enhanced 3270 User Interface. Near-Term-History functions now provided in E3270UI provide the user to quickly analyze and pin point root cause of issues and cross check with verification/cross checking of historical information. Simplification - ordering, pricing and all the components that would ever be needed are included which covers current and future needs as your z/OS environment grows and can expand monitoring of sub-capped levels up to the z/OS base licensed for without renegotiating licensed levels. Reduced time-to-resolution of problems with new embedded data function, provides cross product associated information in a single work space to get the whole picture needed to analyze problems. Lower Cost of Ownership with simplified Install/Config with Parmgen enhancements for first time users up to 60% less time and effort With the improvements being able to see and react to more information on a single 3270 screen, there are significant savings in time to find problems. There are over 380 new 3270 problem solving screens shipped with OM 5.x. Moving the CICS monitoring off the mainframe MIPs and onto the zIIP processor has saved significant resource. We are planning to continue that over time, including moving the Tivoli OMEGAMON Monitor (TOM) to zIIP. Benefits: Save up to 75% of time needed to find problems. Finding and fixing a Looping Job: Old way of having to find the problem by going from LPAR to LPAR to check for job. Each LPAR search used a different monitor, and then operations had to figure out where to go to cancel. Now we can do it all, find and fix, from one screen. Up to 73% savings in reporting on if CICS transactions are meeting SLAs. Savings by exploiting zIIP to off-load OMEGAMON monitoring overhead. Reduce fix times from 90 minutes to 2 minutes. Hung user scenario across large CICS Plex with multiple CICS regions across multiple machines which could take up to 90 minutes to manually search. Could not find the user across large Enterprise easily or quickly. Now with ‘find user’ command under E3270UI with one command OMEGAMON will go find the hung user and we can cancel from the same screen. Customers using OMEGAMON for CICS have really liked this new capability. 48% total less CPU usage running OMEGAMON 5.1 using the E3270UI improvement over OMEGAMON 4.2 CUA monitoring. This was achieved by reducing the number of address spaces and monitors used by OMEGAMON. 45

Analysts already agree that OMEGAMON V5 provides value to clients
Ptak / Noel On OMEGAMON moving to simplified architecture and a common view across multiple domains, Rich Ptak of PNA commented, "This is an important and much needed enhancement. We’ve heard consistently – there is a need for this kind of integration. Consistent interface – a couple of years ago, some people liked to be in a silo and just toss things over to someone else. But, they can’t live that way anymore.” PNA also gave IBM high marks for doing so without losing functionality. On OMEGAMON Enhanced 3270 User Interface, Joe Clabby with Clabby Analytics commented: What you've done to your 3270 interface is kind of a "wow"! I'm not a 3270 fan and I love what you've done with it" Clabby Analytics ftp://public.dhe.ibm.com/software/data/ECM/industry/TWDIBMTivoli_OMEGAMON.pdf

Enhanced OMEGAMON V5 family provides information to automation for improved enterprise management
Increased System Availability with faster problem resolution Enhanced 3270 user interface for SMEs Built-in problem solving scenarios Anomaly detection with IBM zAware Improved productivity with simplified data Faster Install/Configuration/Maintenance Reduced costs with decreased resource usage Usage of zIIP specialty servers Simplified OMEGAMON architecture Benefits: Save up to 75% of time needed to find problems Up to 73% of CICS SLA processing off-loaded Reduce fix times from 90 minutes to 2 minutes Main Point: OMEGAMON V5 now has an improved, integrated 3270 user interface and includes built in problem solving scenarios based on customers reporting of their most common problems. In addition, OMEGAMON V5 supports monitoring and reporting on anomalies based on working with the IBM zAware capability. OMEGAMON can work with Tivoli Monitoring with the Tivoli Enterprise Portal GUI for an end to end visibility. Customers using OMEGAMON V5 have seen significant improvements in the ability to find and fix problems. OMEGAMON continues to exploit ZiiP processors to offload cycles from the mainframe. The included problem solving scenarios and the ability to search a sysplex and lead to significant reductions in finding problems like hung userids. 47

OMEGAMON products collaborate via Integration to quickly track down problems
Problem Sensed Dynamic Workspace Linking And Integration shares information across OMEGAMON products Launch OMEGAMON on z/OS OMEGAMON DE for z/OS Launch OMEGAMON for Storage Launch OMEGAMON for Mainframe Networks Problem Investigated Problem Isolated Organizations which applied an integrated approach show superior results compared to organizations which did not Problem Diagnosed

OMEGAMON Launch in Context capability improves collaboration between different types of users
OMEGAMON provides easy to use navigation between users and views Problem Diagnosed Problem Repaired Another aspect of the OMEGAMON portfolio is that function called Launch in Context which improves the collaboration between different types of users. As we mentioned earlier we have those two user interfaces, GUI and Tipically, GUI is utilized for setting some alerts or situations, that allows you of getting and idea about the problems starting to occur, so it gives you a capability of being a little pro-active and start digging into system, what is the problem, before end users notice it. So, you may use GUI for that, as you don’t have to sit in front of the screen for hours, but you will be notified by a situation when bad thing happens. So the technology will identify the exception for you. At this point you can quickly move over from that problem determination using the function Launch in Context to 3270 interface to deep dive and correct the problem. GUI System z Control Panel Integrate broad range of IT information increasing staff visibility and awareness “Launch in Context” provides fast path to SME for quicker problem resolution

OMEGAMON Family provides integrated performance monitoring for improved productivity and availability Business Challenge: Need to see across systems and be more pro-active to avoid outages OMEGAMON family integrated performance monitoring strategy supports this challenge with standardized user Interfaces GUI (Operations - Monitoring) e3270 (System Programmers – Subject Matter Experts) Delivering Operations and Subject Matter Expert views for faster problem determination and resolution yielding higher system availability

Enhanced 3270 UI Workspaces Workspace Navigation and Panel Controls
BA Cognos 10 Template 9/17/2018 Enhanced 3270 UI Workspaces Workspace Navigation and Panel Controls Auto Update On/Off NAV1 / NAV2 Fields Up / Down Left / Right Scroll Controls Toolbar Panel ID Subpanel Collapse / Expand Control Column Sort Control / Indicator Navigation Selection Field Fixed Column Indicator Status / ThresholdHilighting Starting Row Selection Subpanel Close Control 51 Prensenter name here.ppt

Enhanced Configuration and Maintenance Capability via Self-Describing Agents
Faster, easier, less error-prone for improved reliability and productivity Eliminates application support DVDs No distributed installs or upgrades for mainframe-centric customers Eliminate maintenance upgrade errors Applies to new installs, staged upgrades, and maintenance Crosschecks version with installed data and framework Avoids inconsistent application data in ITM framework layers Eliminate monitoring outages caused by ITM Server recycles Product upgrades/maintenance requires agent or RTEMS recycles only Moving from 40 hours a week to 4 hours a week maintenance 80% improvement in time for installation and maintenance 30% improvement in time to configure post installation

single reference book for upgrade guidance
Customer Driven improvements simplify Installation and Configuration using Parmgen Removal of ICAT as primary way to install and configure Before -145 ICAT product-centric jobs to configure 38 components for 1 LPAR RTE Today – 8 Parmgen function-centric jobs to configure components for 1 LPAR RTE Customers experiencing over 35% improvement in install and configuration time Install without requirement of distributed server Easy to walkthrough steps to complete configuration and customize profile Automatically updates hundreds of configuration artifacts, including auto-discovery of system values single reference book for upgrade guidance The overall process has been simple and quick. Total time for 3-4 products (z/OS, CICS, DB2, TOM plain vanilla) has been about 2 hours Field Engineer Main Point: Replacing complex and error prone ICAT with Parmgen. Combined multiple instructions into single reference guide. Lots of Beta testing on this new capability. “I like using the Parmgen approach better than CICAT/ICAT. I find it much easier to make things repeatable... I like the fact that Parmgen does not overwrite my running members” Typical quotes from early adopters program 53

Moving to simplified architecture driving decreased resource utilization without loss of current function Enhanced OMEGAMON Architecture TEMS CICS IMS z/OS DB2 Stor MfN MSG Single Manager and User Interface across OMEGAMON family TEMAS Tivoli OMEGAMON Manager (TOM) Enhanced 3270 TEP GUI Old OMEGAMON Architecture Classic 3270 IMS z/OS CICS Storage MfN DB2 Messaging Multiple Address Spaces and User Interfaces across each OMEGAMON CUA 3270 TEMS TEMAS TEP GUI 54

Reduce Costs How about improving usage besides using zIIPs, now that is worth exploring and why you should be talking OMEGAMON! OMEGAMON utilize zIIPs and even leverages RMF collections to reduce usage Other vendors don’t discuss their improvement release to release! Where are those details? This is what our test analysis shows, your mileage may vary. Specialty processers certainly provide offload capability but OMEGAMON also provides this. How about release to release. It is our nature in IBM to improve and reduce costs. Need examples and we test this all the time. OMEGAMON XE for IMS from v 4.2 to v 5.1 While Running the DSW (data systems workload at ~5000 TPS) There was a reduction in CPU usage by about 45% in 510 As part of the DSW workload and running IMS: Response Time Analysis feature There was a reduction in Classic's CPU usage by about 97% in 510 and storage usage dropped by about 96%. 55

Reduce Costs How about improving usage besides using zIIPs, now that is worth exploring and why you should be talking OMEGAMON! OMEGAMON XE for CICS from v 4.2 to v 5.3 While Running eRWW (e-business Relational Warehouse Workload) There was a reduction in CPU usage by about 22%. As part of the ERWW workload and running SLA processing running ST96 workload with zIIP enabled There was a reduction in General Processor CPU usage by up to 70%. OMEGAMON XE for MfN from v 4.2 to v 5.1.1 While Running the running the ~30k TN3270 sessions with Application workload modeler Data collection for Gateway Routes There was a reduction in CPU usage during data collection for gateway route information by about 90% Data collection for Interfaces There was a reduction in CPU usage during data collection for interface information by about 77% 56

Reduce Costs More Examples of OMEGAMON improvements, What if you don’t have a zIIP on that lpar, do you still gain benefits? OMEGAMON XE for DB2 v 4.2 to v 5.2 Reduction in CPU for batch processing of 10% Average reduction in CPU for realtime collection, depending on scenario, of about 30% Using thread filtering, about 70% Near Term History reduction of about 20% Total memory usage reduction close to 5% Below the bar memory reduction of about 10% OMEGAMON XE on z/OS from v 4.2 to v 5.3 When the TEP workspace was refreshing every 30 seconds, there was a reduction in CPU usage by about 17% in 510 all while increasing collections for new metrics. OMEGAMON XE for Messaging v 7.0 to v 7.3 Customers using situations this release were provided capability for synchronized collections and this reduced CPU usage by about 77% 57

OMEGAMON XE v5.3 / v7.3 (NTH) Increased problem determination capability with Near-Term-History function in E 3270 UI Understand information related to when the problem began with Enhanced 3270 User Interface Near-Term-History Easily see when a CPC CPU busy is very high and select for details Main Point: OMEGAMON V5.1 provides new levels of visibility into the entire IT environment across z/OS and subsystems (CICS, IMS, DB2). We have updated a number of our OMEGAMON products: OMEGAMON XE for z/OS V5.1.1, OMEGAMON XE for Mainframe Networks V5.1.1, OMEGAMON XE for Storage V5.2 and OMEGAMON XE for z/VM and Linux V4.3 The enhanced OMEGAMON XE for z/OS V5.1.1, along with NetView supports monitoring and management of zEnterprise zAware In addition, there is additional improvements in the installation and configuration capability delivered with Parmgen designed to make make operations more productive and efficient. With the improvements being able to see and react to more information on a single 3270 screen, there are significant savings in time to find problems. There are over 380 new 3270 problem solving screens shipped with OM Moving the CICS monitoring off the mainframe MIPs and onto the zIIP processor has saved significant resource. We are planning to continue that over time, including moving the Tivoli OMEGAMON Monitor (TOM) to zIIP. Benefits: Save up to 75% of time needed to find problems. Finding and fixing a Looping Job: Old way of having to find the problem by going from LPAR to LPAR to check for job. Each LPAR search used a different monitor, and then operations had to figure out where to go to cancel. Now we can do it all, find and fix, from one screen. Up to 73% savings in reporting on if CICS transactions are meeting SLAs. Savings by exploiting zIIP to off-load OMEGAMON monitoring overhead. Reduce fix times from 90 minutes to 2 minutes. Hung user scenario across large CICS Plex with multiple CICS regions across multiple machines which could take up to 90 minutes to manually search. Could not find the user across large Enterprise easily or quickly. Now with ‘find user’ command under E3270UI with one command OMEGAMON will go find the hung user and we can cancel from the same screen. Customers using OMEGAMON for CICS have really liked this new capability. 48% total less CPU usage running OMEGAMON 5.1 using the E3270UI improvement over OMEGAMON 4.2 CUA monitoring. This was achieved by reducing the number of address spaces and monitors used by OMEGAMON. ============================================================= 5698-A59 IBM Tivoli OMEGAMON XE on z/OS V3.1.0 (5608-S81) GA Nov 2005 OMEGAMON History – We continue to enhance this key customer monitoring solution 5698-T01 IBM Tivoli OMEGAMON XE on z/OS V5.1.0 (5608-S81) GA March 2012 5698-A33 IBM Tivoli OMEGAMON XE on z/OS V4.2.0 (5608-S81) GA March 2009 5698-A33 IBM Tivoli OMEGAMON XE on z/OS V4.1.0 (5608-S81) GA Jan 2007 zAware is a mainframe monitor for IBM’s zEnterprise EC12 mainframe server Improved Visibility for APM * Up to 73% of CICS SLA processing off-loaded Decrease resource usage by taking advantage of zIIP specialty processor OMEGAMON for CICS * Reduce fix times from 90 minutes to 2 minutes Improve availability with new ‘Find’ command to easily locate hung users and connections over entire cicsplex Visibility into IBM DB2 Analytics Accelerator (IDAA) delivering query results for ‘Train of Thought’ analysis OMEGAMON for DB2 * Improve performance for multiple applications simultaneously with increased APM and visibility Unlock performance of DB2 Stored Procedures with new displays * Maximize organization's ROI from appliances OMEGAMON XE for DB2 Performance Expert offers the industry’s most comprehensive DB2 for z/OS application performance tool as part of the OMEGAMON family. Along with the capabilities shared across the suite, OMEGAMON DB2’s Extended Insight is a unique capability that can dramatically cut down the time DBAs spend proving that DB2 is not the problem by breaking down response time into its component parts. OMEGAMON DB2 ensures you have the visibility you need to maximixe your investment into the IDAA query accelerator - the Netezza appliance that delivers lightening-fast query results for train-of-thought analysis. Business uses Stored Procedures to encapsulate program logic that can be widely deployed across host and distributed applications. This wide deployment can have dramatic impact on application performance – good and bad. Use OMEGAMON DB2 Performance Expert to unlock their performance attributes and ensure they’re effectively tuned to keep those costs in check. And lastly, your tools have to be ready when you are to exploit new features of DB2. Industry leaders rely on OMEGAMON for complete exploitation, not only toleration, for the latest DB2 versions as well as what DB2 releases through the service stream. * V5.1 uses 24% less CPU than 4.2 running ATF MIPS reduction with Application Trace Facility replacing near term history. OMEGAMON for IMS * 80% improvement in time for installation and maintenance Faster, Easier Installation with Parmgen and Self describing Agent support Enhanced support for Websphere MQ v 7.1 and Websphere Message Broker v 8.1 New views of health of Queues, Queue Managers and Channel Managers. OMEGAMON for MQ Increased visibility outside z platform for common Websphere MQ metrics. Effortlessly explore data around when a CPU busy occurred 58 58

BA Cognos 10 Template 9/17/2018 OMEGAMON XE v5.3 / v7.3 Embedded Data function in E3270 UI for easier problem identification and determination Embedded Data provides the ability to view data, sourced from different OMEGAMON monitors, in a single report. In this example address space information from the z/OS monitor is combined with data from the CICS monitor. This simplifies problem resolution in situations where the solution may involve data from more than one OMEGAMON. Prensenter name here.ppt

OMEGAMON Dashboard Edition for z/OS v5
OMEGAMON Dashboard Edition for z/OS v5.3 Integration the key to collaboration and efficiency Working as a team is vital to getting the job done and the same can be said about your systems management information Greater Visualization, Control and Automation - Integrate management Information from multiple IBM management products on a single workspace for of your enterprise views of IT resources Reduce problem isolation time and correction - Create consolidated alerts that represent all computing resources servicing your critical workloads to quickly isolate and avoid or correct problems Main Point: Search part of Analytics focused on Log analytics Reduce response times to problems and costs - Utilize the policy feature to create sophisticated responses to the world class alerting/situations coming from the OMEGAMONs

z/OS Availability and Performance management Tool
OMEGAMON XE on z/OS v5.3 z/OS Availability and Performance management Tool Overall z/OS Sysplex, LPAR and workload management capabilities providing Availability, Performance, and Workload views to maximize efficiency and effectiveness Greater problem determination for zOS Subject Matter Experts can use the Near-Term-History displays in Enhanced 3270 UI using RMF Monitor III collection to investigate root causes of problems associated to the recent performance problem being addressed. Reduced time-to-resolution of problems with new improved Enhanced 3270 User Interface workspaces including embedded data from CICS, MQ and z/OS for applications monitoring (out of the box but extendable to other DB2, IMS, etc.) Increased ability to deliver service to your user base with new zAware information workspaces and alerts through Enhanced 3270UI and IBM Tivoli Enterprise Portal (TEP). Lower Cost of Ownership with simplified Install/Config with Parmgen enhancements for first time users up to 60% less Time and Effort 61

OMEGAMON XE for CICS on z/OS v5
OMEGAMON XE for CICS on z/OS v5.3 a complete solution for CICS and CICS/TG monitoring OMEGAMON XE for CICS includes capability to gain improved visibility and management of CICS workloads CICS Transaction Gateway new to the Enhanced 3270 User Interface Efficiency and cost saving through integration, version 5.3 includes integrated monitoring with both Enhanced 3270 User Interface and Tivoli Enterprise Portal Increased problem determination capability with Enhanced 3270 User Interface Near-Term-History allows recent performance problem identification combined with CICSplex wide views of transaction details, tracing a transaction across a CICSplex Reduced time-to-resolution of problems with new improved Enhanced User Interface workspaces including embedded data from Z/OS, MQ and Storage bringing pertinent information to where you need it Lower Cost of Ownership with simplified Install/Config with Parmgen enhancements up to 60% in time and effort also increased usage of specialty processors with up to 95% decrease in Bottleneck function CPU Main Point: OMEGAMON V5.1 provides new levels of visibility into the entire IT environment across z/OS and subsystems (CICS, IMS, DB2). We have updated a number of our OMEGAMON products: OMEGAMON XE for z/OS V5.1.1, OMEGAMON XE for Mainframe Networks V5.1.1, OMEGAMON XE for Storage V5.2 and OMEGAMON XE for z/VM and Linux V4.3 The enhanced OMEGAMON XE for z/OS V5.1.1, along with NetView supports monitoring and management of zEnterprise zAware In addition, there is additional improvements in the installation and configuration capability delivered with Parmgen designed to make make operations more productive and efficient. With the improvements being able to see and react to more information on a single 3270 screen, there are significant savings in time to find problems. There are over 380 new 3270 problem solving screens shipped with OM Moving the CICS monitoring off the mainframe MIPs and onto the zIIP processor has saved significant resource. We are planning to continue that over time, including moving the Tivoli OMEGAMON Monitor (TOM) to zIIP. Benefits: Save up to 75% of time needed to find problems. Finding and fixing a Looping Job: Old way of having to find the problem by going from LPAR to LPAR to check for job. Each LPAR search used a different monitor, and then operations had to figure out where to go to cancel. Now we can do it all, find and fix, from one screen. Up to 73% savings in reporting on if CICS transactions are meeting SLAs. Savings by exploiting zIIP to off-load OMEGAMON monitoring overhead. Reduce fix times from 90 minutes to 2 minutes. Hung user scenario across large CICS Plex with multiple CICS regions across multiple machines which could take up to 90 minutes to manually search. Could not find the user across large Enterprise easily or quickly. Now with ‘find user’ command under E3270UI with one command OMEGAMON will go find the hung user and we can cancel from the same screen. Customers using OMEGAMON for CICS have really liked this new capability. 48% total less CPU usage running OMEGAMON 5.1 using the E3270UI improvement over OMEGAMON 4.2 CUA monitoring. This was achieved by reducing the number of address spaces and monitors used by OMEGAMON. ============================================================= OMEGAMON History – We continue to enhance this key customer monitoring solution 5698-A59 IBM Tivoli OMEGAMON XE on z/OS V3.1.0 (5608-S81) GA Nov 2005 5698-A33 IBM Tivoli OMEGAMON XE on z/OS V4.1.0 (5608-S81) GA Jan 2007 5698-A33 IBM Tivoli OMEGAMON XE on z/OS V4.2.0 (5608-S81) GA March 2009 5698-T01 IBM Tivoli OMEGAMON XE on z/OS V5.1.0 (5608-S81) GA March 2012 zAware is a mainframe monitor for IBM’s zEnterprise EC12 mainframe server Improved Visibility for APM OMEGAMON for CICS Decrease resource usage by taking advantage of zIIP specialty processor * Up to 73% of CICS SLA processing off-loaded Improve availability with new ‘Find’ command to easily locate hung users and connections over entire cicsplex * Reduce fix times from 90 minutes to 2 minutes OMEGAMON for DB2 Visibility into IBM DB2 Analytics Accelerator (IDAA) delivering query results for ‘Train of Thought’ analysis * Maximize organization's ROI from appliances Unlock performance of DB2 Stored Procedures with new displays * Improve performance for multiple applications simultaneously with increased APM and visibility OMEGAMON XE for DB2 Performance Expert offers the industry’s most comprehensive DB2 for z/OS application performance tool as part of the OMEGAMON family. Along with the capabilities shared across the suite, OMEGAMON DB2’s Extended Insight is a unique capability that can dramatically cut down the time DBAs spend proving that DB2 is not the problem by breaking down response time into its component parts. OMEGAMON DB2 ensures you have the visibility you need to maximixe your investment into the IDAA query accelerator - the Netezza appliance that delivers lightening-fast query results for train-of-thought analysis. Business uses Stored Procedures to encapsulate program logic that can be widely deployed across host and distributed applications. This wide deployment can have dramatic impact on application performance – good and bad. Use OMEGAMON DB2 Performance Expert to unlock their performance attributes and ensure they’re effectively tuned to keep those costs in check. And lastly, your tools have to be ready when you are to exploit new features of DB2. Industry leaders rely on OMEGAMON for complete exploitation, not only toleration, for the latest DB2 versions as well as what DB2 releases through the service stream. OMEGAMON for IMS MIPS reduction with Application Trace Facility replacing near term history. * V5.1 uses 24% less CPU than 4.2 running ATF Faster, Easier Installation with Parmgen and Self describing Agent support * 80% improvement in time for installation and maintenance OMEGAMON for MQ New views of health of Queues, Queue Managers and Channel Managers. Enhanced support for Websphere MQ v 7.1 and Websphere Message Broker v 8.1 Increased visibility outside z platform for common Websphere MQ metrics. 62 62

IBM MQ for z/OS (WebSphere MQ)
OMEGAMON XE for Messaging v7.3 provides complete solution for MQ and Broker monitoring OMEGAMON XE for Messaging includes capability to gain improved visibility and management of messaging subsystems IBM MQ for z/OS (WebSphere MQ) IBM Integration Bus for z/OS (WebSphere Message Broker) Efficiency and cost saving through integration, Messaging offers an enterprise-wide single point of control with other OMEGAMONs and distributed platform ITCAM Agents for WebSphere Messaging within both the Tivoli Enterprise Portal and the Enhanced 3270 User Interface Increased problem determination capability with Enhanced 3270 User Interface Near-Term-History for all the most important MQ monitoring attributes, to understand when a queue depth began to rise, or a channel changed from running status Reduced time-to-resolution of problems with new improved Enhanced User Interface workspaces including embedded data from CICS and z/OS for connected applications or queues, and direct access to queue manager address space monitoring Main Point: OMEGAMON V5.1 provides new levels of visibility into the entire IT environment across z/OS and subsystems (CICS, IMS, DB2). We have updated a number of our OMEGAMON products: OMEGAMON XE for z/OS V5.1.1, OMEGAMON XE for Mainframe Networks V5.1.1, OMEGAMON XE for Storage V5.2 and OMEGAMON XE for z/VM and Linux V4.3 The enhanced OMEGAMON XE for z/OS V5.1.1, along with NetView supports monitoring and management of zEnterprise zAware In addition, there is additional improvements in the installation and configuration capability delivered with Parmgen designed to make make operations more productive and efficient. With the improvements being able to see and react to more information on a single 3270 screen, there are significant savings in time to find problems. There are over 380 new 3270 problem solving screens shipped with OM Moving the CICS monitoring off the mainframe MIPs and onto the zIIP processor has saved significant resource. We are planning to continue that over time, including moving the Tivoli OMEGAMON Monitor (TOM) to zIIP. Benefits: Save up to 75% of time needed to find problems. Finding and fixing a Looping Job: Old way of having to find the problem by going from LPAR to LPAR to check for job. Each LPAR search used a different monitor, and then operations had to figure out where to go to cancel. Now we can do it all, find and fix, from one screen. Up to 73% savings in reporting on if CICS transactions are meeting SLAs. Savings by exploiting zIIP to off-load OMEGAMON monitoring overhead. Reduce fix times from 90 minutes to 2 minutes. Hung user scenario across large CICS Plex with multiple CICS regions across multiple machines which could take up to 90 minutes to manually search. Could not find the user across large Enterprise easily or quickly. Now with ‘find user’ command under E3270UI with one command OMEGAMON will go find the hung user and we can cancel from the same screen. Customers using OMEGAMON for CICS have really liked this new capability. 48% total less CPU usage running OMEGAMON 5.1 using the E3270UI improvement over OMEGAMON 4.2 CUA monitoring. This was achieved by reducing the number of address spaces and monitors used by OMEGAMON. ============================================================= 5698-A59 IBM Tivoli OMEGAMON XE on z/OS V3.1.0 (5608-S81) GA Nov 2005 OMEGAMON History – We continue to enhance this key customer monitoring solution 5698-T01 IBM Tivoli OMEGAMON XE on z/OS V5.1.0 (5608-S81) GA March 2012 5698-A33 IBM Tivoli OMEGAMON XE on z/OS V4.2.0 (5608-S81) GA March 2009 5698-A33 IBM Tivoli OMEGAMON XE on z/OS V4.1.0 (5608-S81) GA Jan 2007 zAware is a mainframe monitor for IBM’s zEnterprise EC12 mainframe server Improved Visibility for APM * Up to 73% of CICS SLA processing off-loaded Decrease resource usage by taking advantage of zIIP specialty processor OMEGAMON for CICS * Reduce fix times from 90 minutes to 2 minutes Improve availability with new ‘Find’ command to easily locate hung users and connections over entire cicsplex Visibility into IBM DB2 Analytics Accelerator (IDAA) delivering query results for ‘Train of Thought’ analysis OMEGAMON for DB2 * Improve performance for multiple applications simultaneously with increased APM and visibility Unlock performance of DB2 Stored Procedures with new displays * Maximize organization's ROI from appliances OMEGAMON XE for DB2 Performance Expert offers the industry’s most comprehensive DB2 for z/OS application performance tool as part of the OMEGAMON family. Along with the capabilities shared across the suite, OMEGAMON DB2’s Extended Insight is a unique capability that can dramatically cut down the time DBAs spend proving that DB2 is not the problem by breaking down response time into its component parts. OMEGAMON DB2 ensures you have the visibility you need to maximixe your investment into the IDAA query accelerator - the Netezza appliance that delivers lightening-fast query results for train-of-thought analysis. Business uses Stored Procedures to encapsulate program logic that can be widely deployed across host and distributed applications. This wide deployment can have dramatic impact on application performance – good and bad. Use OMEGAMON DB2 Performance Expert to unlock their performance attributes and ensure they’re effectively tuned to keep those costs in check. And lastly, your tools have to be ready when you are to exploit new features of DB2. Industry leaders rely on OMEGAMON for complete exploitation, not only toleration, for the latest DB2 versions as well as what DB2 releases through the service stream. * V5.1 uses 24% less CPU than 4.2 running ATF MIPS reduction with Application Trace Facility replacing near term history. OMEGAMON for IMS * 80% improvement in time for installation and maintenance Faster, Easier Installation with Parmgen and Self describing Agent support Enhanced support for Websphere MQ v 7.1 and Websphere Message Broker v 8.1 New views of health of Queues, Queue Managers and Channel Managers. OMEGAMON for MQ Increased visibility outside z platform for common Websphere MQ metrics. 63

OMEGAMON XE for Storage on z/OS v5.3
Cornerstone for every z/OS Storage management Tool box! Overall z/OS Storage management capabilities provide Availability, Performance, Workload views, and Toolkit functions to maximize efficiency and effectiveness for daily z/OS Storage Management functions Reduce resource consumption, operations Managers will appreciate New Minimal Monitoring Configuration and reduction in Cache and LSpace Collector performance – 20% improvement in CPU collection of data Improve trend analysis and planning - New Dataset Attribute Group Extraction (DAGX) allows analysis of dataset attribute groups using spreadsheet or other analytics tools outside of Tivoli Data Warehouse for Storage Administrators Increased problem determination capability with new E3270UI Embedded Data support makes it easier for Storage Admins to combine displays of related information from OM CICS and OM MQ for better cross storage information analysis Reduced Time to Resolution with new Near-Term-History displays in E3270UI simplifying trending analysis 64

OMEGAMON Performance Management Suite V5 provides complete solution for enterprise monitoring
Ensure platforms and middleware on z/OS are optimized Tivoli OMEGAMON Performance Management Suite for z/OS provides an integrated solution with extensive capabilities to manage on-line and middleware sub-systems like CICS, DB2, IMS WAS on z/OS and the platform which supports these capabilities Simplified, management of your z/OS environment: Portfolio built to manage the operating system and sub-systems servicing your critical workloads running on your z/OS platform Provides a foundation offering for further Analytics and C&SI solutions in the future Integrated for faster identification and isolation of problems Increased productivity with common user interfaces Promotes efficiency between IT groups Manage by exception with sophisticated alerting process New Enhanced 3270ui with workspaces derived for problem solving Single vendor providing managing solution committed to the z/OS environments – Trusted vendor and capabilities Tivoli provides on-line and middleware operational management capabilities that can expand and integrate at the enterprise and business levels Easy to order and price benefit OMEGAMON Performance Management Suite Integration = Effectiveness + Efficiency z/OS Network Storage CICS DB2 IMS MQ WAS Main Point: OMEGAMON V5.3 provides new levels of visibility into the entire IT environment across z/OS and subsystems (CICS, IMS, DB2). We have updated a number of our OMEGAMON products: OMEGAMON XE for z/OS V5.3, XE for Storage V5.3 and OMEGAMON XE for CICS V5.3 Value propositions: Single offering built to manage the operating system and sub-systems servicing your critical workloads running on your z/OS platform Provides a foundation of z/OS management for future capabilities like …. Analytics and Integration Improve productivity of personnel with common user interface tools Promotes efficiency between IT groups (break down the silo’s) Manage by exception with sophisticated alerting process (become more productive) New Enhanced 3270ui with workspaces derived for problem solving (more efficient use of tools) Single vendor providing managing solution committed to the z/OS environments – Trusted vendor and capabilities Tivoli provides on-line and middleware operational management capabilities that can expand and integrate at the enterprise and business levels (z/OS component of an enterprise wide solution). Easy to order and price benefit 65

OM Perf Mgmt Suite for z/OS Objective
Goal: A flexible consolidated offering the address the monitoring of IT OPS for their z/OS platform and middleware environments. Value Highlights Comprehensive z/OS platform information that is needed for analytics Unified Integrated Suite Pricing Benefit as purchased by a suite Flexibility in usage Single trusted vendor solution Ease of decision making Addresses TCO Addresses easier decision making Use any product included up to z/OS Cap Discounted Pricing Trusted vendor committed to z/OS environment Strong support infrastructure Proven management capability in all disciplines of z/OS 66 66 66 66

Tivoli Asset Discovery for z/OS Value
BA Cognos 10 Template 9/17/2018 Tivoli Asset Discovery for z/OS Value z/OS products and applications are shared by many thousands of users and business processes Managing such a highly shared environment relies on site experience and educated guesswork unless you have Tivoli Asset Discovery for z/OS (TADz) to show you who is using what, where and when Benefits from TADz discovery can be achieved in the first week and ROI increases will continual usage monitoring Protect against losing money Reduce unexpected outages e.g. Software upgrades can be managed safer when TADz shows you who would be impacted by the change Avoid license compliance violations Assist planning for mergers, acquisitions and strategic outsourcing Get the most for your budget Software license cost optimization Hardware upgrade optimization Assist planning for more efficient support team structures Less administration to prove license compliance Negotiate with vendors with the power of knowing usage trends Financial accountability Justify license and support costs Product licence costs Product support costs Application support costs Hardware costs Substantiate charge-back 68 Prensenter name here.ppt

Scenarios Reduce unexpected outages from z/OS asset upgrades
BA Cognos 10 Template 9/17/2018 Scenarios Reduce unexpected outages from z/OS asset upgrades See who would be impacted by an upgrade See which products a job is using See where different maintenance levels are deployed See what needs to be replicated to Disaster Recovery systems Get the best value from your z/OS software budget Understanding product usage trends is extremely important for contract renewal negotiations e.g. Which products should be included in an Enterprise License Agreement (ELA) Product LPAR capacity restricted licenses Assess what would be impacted by a competitive product replacement Drop products that are no longer being used Consolidate product versions Consolidate similar products e.g. inherited from company mergers Consolidate product machine/system coverage Sub-capacity license optimization Prove to management that your budget is fully utilized to avoid funding cuts or justify increases Asset management for IT Tivoli Asset Management for IT e.g. contacts, financial, procurement, lifecycle Product inventory verification Audit trail of product use in a z/OS environment 69 Prensenter name here.ppt

PC Browser direct to z/OS based TADz Analyser
BA Cognos 10 Template 9/17/2018 PC Browser direct to z/OS based TADz Analyser Asset reports are good for people who reconcile z/OS product licenses See what product versions are being used, when, where and by whom. 70 70 IBM COPYRIGHT 17/09/2018 Prensenter name here.ppt

Discovery reports are good for people who support z/OS systems
BA Cognos 10 Template 9/17/2018 Discovery reports are good for people who support z/OS systems See what product releases, libraries and modules are being used, when, where and by whom. 71 71 IBM COPYRIGHT 17/09/2018 Prensenter name here.ppt

Report Parameters Optional filter parameters
BA Cognos 10 Template 9/17/2018 Report Parameters Optional filter parameters Click Submit to run the report 72 72 IBM COPYRIGHT 17/09/2018 Prensenter name here.ppt

High Level Summary Reports with easy hyperlinks to details
BA Cognos 10 Template 9/17/2018 High Level Summary Reports with easy hyperlinks to details Hyperlinks to drill down for more details 73 73 IBM COPYRIGHT 17/09/2018 Prensenter name here.ppt

Trend Charts IBM COPYRIGHT IBM COPYRIGHT 17/09/2018
BA Cognos 10 Template 9/17/2018 IBM COPYRIGHT Trend Charts 74 74 IBM COPYRIGHT 17/09/2018 Prensenter name here.ppt

Crosstab reports Hyperlinks to drill down for more details
BA Cognos 10 Template 9/17/2018 IBM COPYRIGHT Crosstab reports Crosstabs are great for highlighting differences at a high level Hyperlinks to drill down for more details 75 75 IBM COPYRIGHT 17/09/2018 Prensenter name here.ppt

Color coded trend reports
BA Cognos 10 Template 9/17/2018 Color coded trend reports At a glance see which hyperlink is worth clicking to see a trend chart and details 76 76 IBM COPYRIGHT 17/09/2018 Prensenter name here.ppt

BA Cognos 10 Template 9/17/2018 This is a report from a new TADz customer database, which shows they have libraries that were created 30 years ago and are still being used ! z/OS upgrades typically add new software releases but also retain the old too – evolutionary Different to Distributed where hardware upgrades are common every few years with software freshly installed – revolutionary How can you safely move users off old product releases in an environment SHARED by thousands of users ? Non-TADz customers Rely on site experience and educated guesswork Exposed to license compliance violations Exposed to product support difficulties TADz customers TADz shows what is being used, where, when and by who Most new TADz customers find year old libraries that are still being used 77 77 IBM COPYRIGHT 17/09/2018 Prensenter name here.ppt

Asset Discovery Core Architecture
BA Cognos 10 Template 9/17/2018 Asset Discovery Core Architecture Remote Mainframe Components Central Mainframe Components Batch Raw Usage Data Usage Monitor Usage Import STC TSO GUI Knowledge Base Repository Analyzer All DASD Raw IQ Data IQ Import Inquisitor TADz V8.1 uses DB2 for z/OS on a central z/OS and now also SQLite One DB2 subsystem with one or more repository databases Designed to keep overhead on production (remote) LPARs as low as possible Single SQLite database with one repository database z/OS based TADz Analyzer: No pre-reqs on any middleware or config e.g. Websphere and Java are not required Interactive analysis from your PC Browser (IE, Firefox) directly to the z/OS based TADz Analyzer running as a batch job or Started Task. Easy download to Excel. Batch reporting - Run a batch job to generate spreadsheets 78 Prensenter name here.ppt

Monitoring Automation
Integrate monitoring and automation to create pro-active automation to find and resolve problems faster Exception display and simple actions Create message filtering and message automation Monitor issues for potential automation Exploit OMEGAMON exceptions for automation Integration of monitoring and automation Manual correlation of problems across applications Exploit single user interface to enable seamless operations Develop escalation with extended information Pro-active automation Correlation of problems across applications Adaption of thresholds Switching on of traces as needed avoids overhead Monitoring Automation Main Point: Monitoring with OMEGAMON and Automation with SA can provide a pro-active vs reactive approach to managing operations. Need to eliminate Islands of operations. Monitoring can find problems, but operations may or may not see them. Thresholds can create exceptions, but may not be set correctly, and vary. Need to minimize operations overhead for find and fixing common problems 80

Higher automation level through integration
Forecasting Anomaly Detection Topology Correlation Adaptive Predictive Integrated Actions Self-learning Correlation History Health based Goal driven Policy based Thresholds Adaptive Adaptive (tuning) Capacity on demand Move Correct Release Escalation Common GUI Recovery Restart Correlation Dynamic Thresholds History KPIs Trace Reaction Exceptions Thresholds Automation Pro-active Monitoring Advanced Automation evolution from re-active to pro-active and – in the future- to adaptive automation is displayed on the left. Monitoring evolution from passive to active, to advanced, to adaptive and – in the future- to predictive monitoring is displayed on the right. The evolution of automation integrated with monitoring is displayed in the middle. Re-active automation is triggered by exceeded thresholds. It is considered basic. Policy based automation can increase automation quality and can reduce greatly automation implementation and maintenance efforts by reducing scripts and by putting all automation definitions at one place, the policy. Goal based automation can greatly simplify operations: the operator just requests what she/he wants, automation takes care of any dependencies and resolution of affected or even conflicting goals. Health based automation allows pro-active automation using monitoring to resolve performance problems before they cause outages. Correlation of automation is done in various manners: Forcing down a resource when the resource it is dependent on fails Using multiple trigger conditions for startup or shutdown State dependant automation and subscription to another resource‘s status Today resource and automation history is in logs, the future adaptive automation might be self-learning from resource behaviour, changed configurations or product versions and from operator actions. At the high end adaptive monitoring correlates dependent on topology and can detect anomalies e.g. by looking for signatures. Predictive monitoring will forecast when thresholds will be exceeded or when problems will surface due to expected and current load and based on history and topology changes. Integrated actions (in the middle) can be done by automation a lot faster, in time and correctly: Start/stop/move resources (work around). Automation is an expert in that! Send a notification to default event receiver or specified owner of resource Unlocking resources and releasing locks Killing resources that consume too many resources. Loved ones can be protected. Resetting resources that do not work Offloading logs and data adding resources like more application servers, more disk, more CPU or more RAM Adaptive automation can tune applications on the fly, however this is specific to applications and needs expert knowledge put into automation. . Active Re-active Passive

Incorporate automation based on monitoring
System Automation for z/OS monitor resources Use any active or passive monitor Determine application health Can act before failure occurs System Automation integrates with OMEGAMON using exceptions and situations IBM Monitoring products OMEGAMON XE NetView Health- Based Automation Exception-Based Automation Resource / Exception Monitoring New range of health-monitoring possibilities Turnkey-solution for exception-monitoring To overcome the islands of monitoring and automation, automation has to incorporate monitoring. The IBM Monitoring products OMEGAMON XE but also NetView provide a wealth of hardware and software performance and availability data. System Automation for z/OS integrates with OMEGAMON XE: It can use OMEGAMON exceptions displayed on 3270 and OMEGAMON XE situations for exception-based automation. The SA monitor resources can determine application and resource health by using active and passive monitor commands. Thresholds and also actions to resolve performance problems can be defined in policy. The monitor result is translated into an application health status that is propagated to monitored resources and aggregated into their compound status to allow easy detection of performance problems. SA is able to detect performance problems and to act before a failure occurs. HW and SW performance and availability data 82 82

IBM allows customers to tie pro-active automation solution components together
Active or passive performance monitoring Managed by automation Integrated with monitor products Determine health state or exceeded thresholds Gather more information from other monitors Send a notification to default event receiver or specified owner of resource Status/Event console (System z or end-to-end) Callout router (escalation process) , SMS, pager Start/stop/move resources (work around) Expert level: Cure performance problem by Using performance monitor, system or affected subsystem API Advanced: Change WLM policy or LPAR weights IBM Tivoli Business Service Manager OMNIBus System Automation NetView OMEGAMON Monitoring What is pro-active automation? As already discussed, active or passive performance monitoring should be integrated with automation. Automation determines the health state based on exceeded tresholds or metrics. The advantages of having performance information in automation are that automation can do more than just a single monitor: Gather more information from other monitors to find out whether the root cause is elsewhere Send a notification to default event receiver or specified owner of resource. This is done by almost every client who uses performance monitoring Start/stop/move resources (work around). Automation is an expert in that! The expert level is to cure performance problems, many clients demand that, but very little have implemented it as there is no general approach. However it is important that all command APIs are available and again automation provides that. A very advanced option would be to change WLM policy or LPAR weights with SA Processor Operations z/OS IMS DB2 z/VM Linux CICS WebSphere 83 83

System Automation Integration Points
General alerting infrastructure to alert and escalate, for example via SA IOM, to send events to OMNIbus, or other products, in case of critical events Management of cross-platform dependencies, end-to-end Enterprise Automation Service Management Workload Scheduling Disaster Recovery Monitoring Events / Notifcations TBSM performs resource discovery and status change notification for use within business systems CICSPlex event monitoring for health based automation SA z/OS DLA discovers resources to be presented in TADDM or CCMDB in context with other configuration data for use by process managers TEP provides operational per-spective side by side with per-formance and availability data SA situations and generic moni-toring capabilities using Status Items Incidents can be opened based on problems detected by SA z/OS, for example in TSRM Access to wealth of OMEGAMON performance and availability data for health based automation On this slide are key integration capabilities in the automation product. NetView is an excellent integration platform: it has many interfaces and great connectivity. In IBM Automation Control for z/OS not all of the interfaces are available. The service offering Geographically Dispersed Parallel Sysplex provides disaster recovery, not only for z/OS but also for Linux on System z and even non System z platforms. Geographically Dispersed Parallel Sysplex is a Tivoli System Automation for z/OS application and only available with Tivoli System Automation for z/OS. Escalation to various notification targets can be setup easily using pre-defined or user defined alert points on a resource level to: Create incidents in IBM Tivoli Service Request Manager® or other products. IBM Tivoli Directory Integrator is used as an interface. Create events in IBM Tivoli Netcool® OMNIbus through Event Integration Facility (EIF) Alarm staff using , pager, or SMS using IBM Tivoli System Automation for Integrated Operations Management Display Exceptional messages and status for resources that have SDF as notification target on the Status Display Facility (SDF). Workload automation products can create requests to start or stop applications by using the request driven interface Comprehensive integration with Tivoli Workload Scheduler exists. Tivoli Workload Scheduler has an automation workstation that allows to send any command to automation, synchronously and asynchronously. Automation can display the status of the current plan and also query wether today is marked as a holiday in the TWS calendar Pro-active automation with OMEGAMON XE To overcome the islands of monitoring and automation, automation has to incorporate monitoring. The IBM Monitoring products OMEGAMON XE but also NetView provide a wealth of hardware and software performance and availability data. System Automation for z/OS and IBM Automation Control for z/OS integrate with OMEGAMON XE. System Automation for z/OS and IBM Automation Control for z/OS can use OMEGAMON exceptions and situations for exception-based automation. The monitor resources allow to define active and passive monitors, thresholds and also actions to resolve performance problems. The monitor result is translated into a application health status that is propagated to monitored resources and aggregated into their compound status to allow easy detection of performance problems. Pro-active automation is able to detect performance problems and to act before a failure occurs. CICS Automation allows the monitoring of events that are issued by CICSPlex System Manager (CICSPlex SM). When an event is received, the event severity is mapped to the health status of a related monitor resource and, in addition, defined recovery commands are issued. SA z/OS collects and records job-related information, and writes System Management Facility (SMF) records at specific events in the lifetime of a resource. The INGPUSMF batch utility produces a report file that you can import into a spreadsheet. You can also convert and write the report into DB2 tables that are provided and exploited by the IBM Tivoli System Automation Application Manager. Integration into end-to-end automation, that is provided by IBM Tivoli System Automation Application Manager, is available with Tivoli System Automation for z/OS. Flexible command interface in TWS to issue SA and NetView commands SA z/OS is basis for GDPS for start / stop of systems and provides hardware command interface to perform disaster recovery at a remote site

OMEGAMON integrates within a total System z Business Service Management solution
OMEGAMON Portfolio provides performance and availability visibility for System z events and data consumed by a set of Tivoli BSM products Business Assessment OMEGAMON TBSM OMNIbus Tivoli OMEGAMON Manager e3270ui Discovery XE agents TADDM IBM Tivoli Monitoring (ITM) RMF Transaction Tracking PURPOSE: This slide is an additional slide to address integrations scenarios with other IBM and/or partner offerings, if needed. SOURCE: Business Plans, augmented with other information available at the time of the DCP. CHANGE HISTORY: Sept 2011: New slide Note that this slide is intended to address integration in the context of usecase scenarios so the team can express the value of the “combined set of products” from the perspective of the end user. The team is also asked to evaluate the impact the offering roadmap has in other offerings, i.e., impact in the next 2-3 years, taking into consideration the IBM strategy. TEP Cloud OM DE ITCAM TADDM – Tivoli Application Dependency Discovery Manager ITCAM TT – Transaction Tracking for z and distributed platforms SC APM – IBM SmartCloud Application Performance Manager TBSM – Tivoli Business Service Manager SC APM 85 85

Policy-based escalation of problems
IBM Automation Control for z/OS Policy-based escalation of problems Send alerts to Netcool OMNIbus or other EIF receiver Events can be sent to SDF or TEP also CAPMSGS defines severity Built-in alert points Alerting infrastracture with INGALERT Exit allows additional suppressing based on calendar or to add attributes System Automation for Integrated Operations Management escalates using SMS text messages with confirmation Netcool Tivoli Enterprise Portal Tivoli Directory Integrator EIF probe EIF SA IOM TTT EIF z/OS NetView & SA z/OS Policy USR TEMS APL & MVC IOM SDF Messages ITM SA TEMA CAPMSGS INGALERT The message ID for the code match is CAPMSGS. CODE1 is set to the message ID of the message being captured. CODE2 is set to the job name (you can alternatively set this to the subsystem name) of the subsystem that issued the message. CODE3 is set to the value specified in the Code parameter. The severity code that is defined as the value to be returned to the command list can be one of the following: IMPORTANT The message is captured and its color is set to PINK. IGNORE The message is not captured. NORMAL The message is captured and its color is set to GREEN, but not forwarded to SDF or NMC. UNUSUAL The message is captured and its color is set to YELLOW. CRITICAL The message is captured and its color is set to RED. Alert point Suppress Attributes TWS AOFEXC17 Calendars MessageID USER © Copyright IBM Corp Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Netcool/OMINbus event forwarding enablement, events as shown in the Netcool Console
The benefits of the TEC and Netcool/OMNIbus products and the details of how they can be integrated with IBM Tivoli Monitoring are described in the ″Event integration scenarios″ section of IBM Tivoli Monitoring: Installation and Setup Guide. 87

Health Checker integration
Displays a summary of information about each checks (On 3270, Health Checker Status and Health Checks views are on the same panel)

zAware Analysis Workspace (TEP)
89

Omegamon XE on z/OS 90

zAware Workspace (e3270)

IBM zAware, Automation, Event Management and PD Tools
When classic alerts occur like SLA violations detected by Tivoli monitoring tools View events in Active Event List Use NetView sample to add information on message anomalies from zAware to Active Event List If abnormal message traffic occurs, use zAware to find which message ids and components are interesting Browse NetView CANZLOG to perform problem determination NetView NetView processing … Query zAware (10 minute interval) If anomaly detected Generate ‘anomaly’ message Generate Event Browse NetView CANZLOG Perform PD for anomaly IBM Tivoli NetView for z/OS Use the APIs to pull the IBM zAware results Sample programs are available from Described in detail in the Redbook: Extending z/OS System Management Functions with IBM zAware The samples can be tailored to drive NetView message automation for high anomaly scores: Generate a message Generate an event CANZLOG – Browse consolidated logs for PD Service Management Connect: NetView wiki page to download zAware integration samples and documentation Active automation table policy Morning of work Every 10 minutes Ops MVS track messsage id being generated ---sample that available generates a message id. Automation product should handle it NetView samples provided to generate anomaly message and event(s) - Available for download from Service Management Connect NetView integration referenced from IBM zAware Redbook IBM Services (optional) available to install and configure zAware and NetView 92 All statements regarding IBM’s future directions and intent are subject to change or withdrawal without notice and represent goals and objectives only

IBM NetView CANZLOG consolidated log shows IBM zAware messages
NetView sample uses the IBM zAware API to retrieve information from the IBM zAware LPAR, for consolidation of IBM zAware information into NetView by generating a standard WTO IBM Tivoli System Automation can then be used to automate on message and policies can be established to control corrective actions. The IBM Tivoli NetView CANZLOG function consolidates messages from the z/OS syslog and the NetView Netlog. NetView can automate messages from these sources. Browse NetView CANZLOG in context of zAware anomaly Set filter and timeframe 5 minutes before and after to view related messages to perform problem determination in context of time anomaly occurred Service Management Connect: NetView wiki page to download zAware integration samples and documentation 93 93

Tivoli zStorage Integration - Unmatched Capability
Differentiators Seamless Integration with other IBM/Tivoli management and automation offerings Application view of I/O Performance and Cross System support Deep availability & performance capability Situations – Manage by Exception Best in class HSM reporting, audit & error correction Allocation Management provides more preventive/corrective function IBM exclusive capability for fast replication in Backup & Recovery management Suite packaging and pricing advantages Tivoli zStorage Management Suite -Tightly Integrated Products Tivoli Advanced Reporting and Mgmt for DFSMShsm Tivoli Advanced Allocation Management for z/OS Tivoli Advanced Backup & Recovery for z/OS Tivoli Advanced Audit for DFSMShsm Tivoli Automated Tape Allocation Manager OMEGAMON XE for Storage on z/OS Tivoli Advanced Catalog Management for z/OS Tivoli Tape Optimizer Tivoli z/OS Storage portfolio brings together a rich set of z/OS Storage management capabilities together including hardware and software monitoring, HSM management, ICF Catalog management, Data Allocation & Tape management to prevent costly outages and reduce CPU and storage hardware costs Common interfaces, standard methods of operation, built-in subject matter expertise, consolidated information views, intelligent alerting, and automation of routine tasks all combine to make users more efficient and reduce 24X7 reliance on subject matter “gurus” Tivoli OMEGAMON XE for Storage on z/OS is the hub that integrates with an array of powerful specialty management components to break down organizational silos, share expertise and foster collaboration in solving problems and optimizing the environment . DFSMSdss DFSMShsm DFSMSrmm DFSMSdfp 94

OMEGAMON XE for Mainframe Networks
NetView and OMEGAMON for Mainframe Networks working together create single view of enterprise networks NetView Network Availability OMEGAMON XE for Mainframe Networks Network Performance Common user interface integrates TCP/IP data from both NetView and OMEGAMON XE for Mainframe Networks. Integration function provides customers with a consolidated TCP/IP workbench Allowing management of both TCP/IP availability and performance from the same user interface. Smart IP tracing to immediately learn where poor or unstable TCP/IP connections hamper application performance 95

zEnterprise Monitoring and Discovery
ITM & OMNIbus TBSM OMEGAMON events Business Service Management TADDM Power Workload Resource Groups KVM z/VM LPAR Policy Storage Network Existing operating system, middleware, application monitoring agents and discovery sensors Applications zBX Blade HW Resources Data Power System z PR/SM zEC12/z196/z114 z/OS AIX System p Linux x86 zEnterprise System z/VM z/Aware System z HW Resources pHYP KVM Operating systems Provisioning Current capabilities enable customers to create a service catalog and provide a self-service portal for service requests. Tivoli intends to utilize the Unified Resource Manager APIs to extend the existing capabilities to enable provisioning of zEnterprise resources in the context of heterogeneous workload resource groups. Monitoring and Discovery Existing Tivoli agents and sensors provide monitoring and discovery of operating systems, middleware, applications, network, etc running on zEnterprise LPARs and virtual servers. Tivoli intends to take advantage of new information (zEnterprise hardware resources, ensembles, workload resources groups, virtual servers, network, storage, etc) made available via the Unified Resource Manager APIs to further compliment existing end-to-end monitoring, alerting, and discovery views, providing additional visibility into the end-to-end zEnterprise infrastructure. Business service management Currently provides a fully integrated visualization engine for helping to guarantee business service levels on zEnterprise Tivoli intends to provide expanded end-to-end coverage to enable users to determine which business services are affected when zEnterprise resoures are not meeting their service level objectives. The additional information enabled by the Unified Resource Manager APIs provides greater visibility into the zEnterprise infrastructure allowing Tivoli to integrate zEnterprise data and events with existing Service Management capabilities provided by IBM Netcool/OMNIbus, IBM Tivoli ITM and OMEGAMON XE, IBM Event Pump on z/OS and IBM NetView for z/OS. z/VM LPARs Virtual Servers Blades HW zManager APIs 96

How to improve configuration and setup before SMSz 1.2
Read the Installation manual ... ... decide which of the many installation steps apply to your z/OS environment Perform those steps by.... … adapting all the identified sample files and … … filling in your environmental data at multiple places spread across the sample files And do all this … in a consistent way! Manual configuration steps Often error prone Cumbersome Time consuming ... The traditional approach for installing and configuring a product is to read the manuals and then you have to decide which of the many steps apply to your local installation. You perform these step by step as described in the thick installation manuals. This mean you adapt the delivered samples at multiple places spread often over several sample files. The challenge for the system administrator is to do this all in a consistent way. So normaly the system administrator cross his fingers that this work the right way. 98 98 98

SMSz 1.2 provides simplified automation configuration through an intelligent Configuration Assistant
Significantly improved Time to Configuration with a 80% decrease in time of System Automation base configuration Simple configuration to get base automation components running Automation manger Automation agent Subsystem interface Use of configuration assistant that automates majority of configuration process Keep number of configuration variables down at the necessary minimum Benefit from lab experience using “standard” option set (stylesheet) Post install/configuration verification to ensure all necessary steps (in particular steps that have to be done by other persona) have been completed After you have installed the product with SMP/E the configuration assistance comes into play. It covers the actions to be done when the product target libraries are available to your system environment. The configuration assistance sets up an environment so that the base automation components are running. These are the automation manager, the automation agent and the subsystem interface. The configuration assistance automates the majority of the configuration steps. The concept is that the number of configuration variables is as low as absolutely necessary (around 50). When using the configuration assistance you benefit from the experience of the IBM Böblingen lab. After the configuration assistance has completed, a verification of the generated setup is done against your system environment. 99 99 99

One PDS to Configuration Assistant – How does it work? One job to run
ONLY 3 STEPS TO DEFINE YOUR CONFIGURATION One job to run CONFLIB Options File Configuration Assistant JCLs JCLs JCLs Start Procedures Start Procedures JCLs JCLs JCLs JCLs PARMLIB DSIPARM VTAMLIB VTAMLST JCLs JCLs The concept of configuration assistance is to have one place to store your configuration data. Then have one job to process them. Then have one output PDS where all your JCLs, start procedures and parameter files are stored. Now the SYSPROG can inspect the members and if it is really required can adapt them to the local needs. One place to define your configuration data One PDS to find your configuration files 100100 100 100

Improved System Performance with Automation/Monitoring integration
Situation The overall z/OS system utilization and also the utilization of individual started tasks / jobs is understood for normal and peak hours Problem Detect when started tasks / jobs show abnormally high CPU utilization Some jobs causing CPU to loop and are hard to detect Prevent that these types of work can dominate the system Solution OMEGAMON XE for z/OS data is analyzed by System Automation for high CPU utilization System Automation can categorize different types of work and allows to define various recovery actions through policy – not programming! OMEGAMON XE for z/OS Monitor Looping candidates Categorize / Recover System Automation Summary Looping Address Space Suppression Actively seeks and deals with address spaces in 'hot' CPU loops Define how to deal with them through policy Categorization Recovery actions Diagnostics can help pin point the loop in the code Retrofit to SA 3.4: OA43571 Policy Ignore Warn Diagnose Stop/Cancel Reset Recovery Options Ignore Notify Reset 101101 101 101

Immediate message reporting on Tivoli Enterprise Portal
Situation Incidents happen all the time but luckily, with SA z/OS, they can also be recovered very quickly Problem Customers using TEP as primary console for operations rely on every incident being reported as a situation However, short-lived incidents may remain undetected by situation sampling routines and hence are invisible to the operations team Solution SA z/OS exploits ITM pure event situations So, in combination with its monitoring agent, SA z/OS allows to send selected exceptional messages immediately to TEP by means of policy TEP Push in real-time SA z/OS Monitoring Agent SA z/OS SYSC Incident SYSA SYSB 102102 102 102

Application Pacing System Automation manages dependencies between resources Any parent resource “Start all WAS resources as soon as the start dependencies are fulfilled, for example, all parents are available” HasParent WAS WAS WAS WAS WAS WAS WAS The Problem: Many resources started at once, could be heavy workload dominating the CPU and prevent other work from running. The Solution: IBM Service Management Suite for z/OS 1.2 provides application pacing feature to ensure controlled start and stop of resources to avoid CPU consumption peak and performance impact. 103103 103 103

Multiple User Support for Policy Configuration
browse Automation Policy (PDS containing ISPF Tables) build With SMSz 1.1: Automation policies either can be edited or built. With SMSz 1.2: Multiple users can browse and edit policies concurrently. Users can work in ISPF split screen mode and the policy can be browsed while a configuration built process runs in parallel. 104104 104 104

Performance Management predictive analysis en-hanced
IBM Service Management Suite for z/OS 1.2 support Analytics Predictive Analytics capability for anomaly detection zEnterprise zAware allows outage predictions Improved productivity with enhanced install/config 490 fewer parameters to customize 75% reduction in refresh steps Expert Knowledge Machine Learning Integrated Intuitive IBM zAware SMSz 1.2 members NetView V6.2.1 & OMEGAMON V5.1.1 support Analytics. Benefits: Save up to 75% of time needed to find problems Up to 73% of CICS SLA processing off-loaded Reduce fix times from 90 minutes to 2 minutes 105105

Customers can achieve a number of benefits today integrating mainframe monitoring and automation
OMEGAMON higher availability and easier operations Plug‘n play automation module available Pro-active automation Achieve higher automation degree and higher availability Advantages of having automation where it belongs: SA z/OS Higher automation quality with policies Easier to maintain, control, operate and integrate Policy based automation helps avoiding scripts OMEGAMON can use SA z/OS to: Start expensive traces only when needed Stop or recycle applications to solve problems like memory leak Kill transactions or threads Can use include/exclude lists Correlate events and thresholds across monitor boundaries The following benefits are available today by integrating mainframe monitoring and automation. SA z/OS ships a plug‘n play automation module to make OMEGAMONs and required infrastructure highly available. Pro-active automation uses OMEGAMONs to detect problems before they cause outages. A higher automation degree results in less operator work and higher availability. Although monitoring is able to resolve simple problems by sending a command to a target system, SA z/OS is much more powerful as it does not require many scripts because it is policy based, which also increases automation quality. If automation is at one place it is easier to maintain, control, operate and integrate. OMEGAMON can use SA z/OS to: Start expensive traces only when needed when specific conditions and error situations are detected Stop or recycle applications to solve problems like memory leak Kill transactions or threads. Include/exclude lists can be used to protect loved ones SA z/OS can correlate events and thresholds across monitor boundaries 107 107

Integrated Solution (SA + OMEGAMON) No escalation of problems
Drive down cost of IT operations with pro-active Automation exploiting OMEGAMON and System Automation for z/OS Lack of Integration Integrated Solution (SA + OMEGAMON) No escalation of problems Unable to find root cause Downtime of applications Higher operations costs Trace overhead up to 60% Automatic escalation with extended info Correlation of problems across applications Fix problems before they become outages Easier operations from one GUI Higher automation degree and tracing OMEGAMON provides “Eyes” and “Ears” System Automation provides “Hands” and “Feet” Islands of monitoring and automation lead to potentially more outages and higher costs as automation can not detect and resolve performance problems before they become outages. Operators are alerted about monitor or automation exceptions so operators do not have to monitor many consoles and are not required to enter many commands to detect and diagnose problems Correlation of problems across applications can be done by exploiting ITM situations that trigger automation events and further automated investigation that are displayed in resource status and presented to the operator. Pro-active automation using monitoring can resolve performance problems before they cause outages. The Tivoli Enterprise Portal allows easier operations from one GUI: Tivoli Monitoring agents, OMEGAMON, NetView and Tivoli System Automation for z/OS send status information to the Tivoli Enterprise Management Server (TEMS). Operators are being alerted by situations, can drill down to the root cause and use ITM workspaces for problem analysis. With a high automation degree operators are relieved and recovery time is significantly reduced as more complex recovery is done by automation, fast and reliably. 108 108

Service Management Suite improves ability to manage performance and availability
Better management of resources and costs Simplifies Problem Source Identification across system Helps navigate from alerts to metrics Increases effectiveness Provides capability to manage by exception Matches expert decision making combining thresholds from multiple metrics for greater automation or problem correction Evaluates combined cross system or subsystem events Increasing staff control of z/OS environment with single view of, Operating System, Network (SNA and IP) and z/OS Storage Improve cost reduction, increase effectiveness and better collaboration 109109

Value Highlights Key Value Points
Comprehensive z/OS platform information that is needed for analytics Unified Integrated Suite Pricing Benefit as purchased by a suite Flexibility in usage Single trusted vendor solution Ease of decision making Addresses TCO Addresses easier decision making Use any product included up to z/OS Cap Discounted Pricing Trusted vendor committed to z/OS environment Strong support infrastructure Proven management capability in all disciplines of z/OS 110110 110 110 110

Achieving high availability requires visibility, control and automation provided by IBM Service Management Suite for z/OS 1 Single PID offering that contains the System and Resource level automation, network, monitoring, and discovery capabilities needed to manage z/OS and all key subsystems 2 Simple Pricing metric (z/OS VU’s) enabling customers to deploy infrastructure and middleware solutions as needed. 3 IBM only vendor who can tie technologies together with Visibility, Control and Automation to meet end-to-end SLA 111111

BA Cognos 10 Template 9/17/2018 Backup Prensenter name here.ppt

Value that Cognos brings to Tivoli clients
Simplified report editing Launch web-based Report Studio in context from a report You can run an out-of-the-box report, like an ITM report, and launch the editor in context to change something. Ad-Hoc Reporting Create ad-hoc, on the fly reports Even novice users will be able to rapidly create reports with intuitive drag & drop function via the Query Studio, allowing for greater report usage with little training Other capabilities Automatic ing of reports Additional report formats XML Excel 2000 & 2000 Single Sheet, 2002, and 2007 CSV Granular data security (row-level authorization) 113

IBM Service Management Suite for z/OS

Similar presentations

Presentation on theme: "IBM Service Management Suite for z/OS"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

IBM Service Management Suite for z/OS

Similar presentations

Presentation on theme: "IBM Service Management Suite for z/OS"— Presentation transcript:

Similar presentations

About project

Feedback