OMEGAMON News - conferences.gse.org.ukconferences.gse.org.uk/attachments/presentations/6... ·...

OMEGAMON News

Dave Swift

david_swift@uk.ibm.com

Date of presentation 03/11/2015

Session OA

Copyright and Trademarks

the IBM Corp. in USA and/or other countries and may be used throughout

this presentation:

Session feedback – Do it online at http://feedback.gse.org.uk/OA

CICS, DB2, IBM, IMS, ITM, NetView, OMEGAMON, RMF, RACF, S/390, Tivoli, VTAM, WebSphere, z/OS, zSeries,

System z, Linux on System z

Other company, product and service names may be trademarks or service

marks of others.

OMEGAMON Packaging Options

Packaging

Service Management Suite for z/OS

- NetView for z/OS

- System Automation for z/OS

- Tivoli Asset Discovery

OM z/OS Perf Mgmt Suite

Available Jan 2014OM z/OS Perf Mgmt Suite

- OM Dashboard Edition on z/OS

Available April 2014

OM z/OS Management Suite

- OM XE on z/OS

- OM XE for Mainframe Networks

- OM XE for Storage on z/OS

- OM z/VM and Linux

Available Oct 2012

- OM XE on z/OS

- OM XE for CICS on z/OS

- OM XE for DB2 PE on z/OS

- OM XE for IMS on z/OS

- OM XE for Messaging on z/OS

- ITCAM for Web Resources

- OM XE on z/OS

Packaging Cont’dService Management Suite for z/OS

- NetView for z/OS

- System Automation for z/OS

- Tivoli Asset Discovery

- Service Management Unite

- OM XE on z/OS

OM z/OS Management Suite

- OM XE on z/OS

- OM z/VM and Linux

- SmartCloud AnalyticsLog Analysis z/OS Insight Packs

- TMS on z/OS 6.3.0.2 (incl. IOAz)

- OM XE on z/OS

- SmartCloud AnalyticsLog Analysis z/OS Insight Packs

- TMS on z/OS 6.3.0.2 (incl. IOAz)

Available Oct 2012

Service Management Unite

Service Management Unite - What is it?

Monitor System Health

Domain and Automation Health

Explore Automation

Domains

IBM Electronic Support

Work with automated

ResourcesHelp

Event Viewer for

OMEGAMON and SA for z/OS

Overview on

Automation DomainsNetView for z/OS

CANZLOG

zWebUI

Web browser

� Reduce problem determination time, even while on the go

� Provide safe and easy access to mainframe

� Optimize time with

IBM Service Management Unite Web Dashboards

zWebUI

JazzSM (WebSphere, DASH and TDI)

zLinux

� Optimize time with integrated, consolidated views

� Uses your existingenvironment – runs on z!

Unite Strategy uses Integration toolkits: DASH Web UI & Tivoli Directory Integrator (TDI)

End to End Federation of Solution DashboardsEnd to End Federation of Solution Dashboards

Mobile UIsMobile UIs

Data federation Data federation

Session feedback – Do it online at http://feedback.gse.org.uk/OA9

Mobile UIsMobile UIs

Product UIs for both distributed and mainframe service Product UIs for both distributed and mainframe service management tools ….. Reporting and administration!management tools ….. Reporting and administration!

AdminAdmin

ReportingReporting

APM, Impact, SCAAPM, Impact, SCA--LA, LA, SCAPI, SAAMSCAPI, SAAM

New! Unite: OMEGAMON, New! Unite: OMEGAMON, Log Analytics, Log Analytics, NetViewNetView for for z/OS, z/OS, TADzTADz, SA for z/OS , SA for z/OS

SAzSAz, , TWSzTWSz, OM , OM zVM&LzVM&L ITNM, TNPM, ITNM, TNPM, OMNIbusOMNIbus, NOI, NOI

Page federation Page federation

OMEGAMON Dashboard Edition

What's New in V530 IF1Situation Status Tree in Enhanced 3270 UI

– Collects and displays situation data from hub TEMS

– Strategic replacement for OMEGAVIEW

Dashboard Edition Enabled versus Non-DE Enabled

From any workspace, attempt to switch to Situation Events

(“Events”, “Alerts”)

Dashboard Edition EnabledRouted to

Situation Status Tree (KOBSITST)

Non-DE EnabledRouted to

Situation Status (KOBSITMN)

(KOBSITST)

Situation Status Tree BasicsEach cell/slot represents a sample of situation data indicating status

A defined number of recent samples are stored. Also a historical time period also shown

The layout of the tree can be customized.

“Worst” status is rolled-up through the branches

Situation Status Tree Basics

Clicking or hitting enter on a cell takes user to a detailed workspace specific to situation results

Basic Customization of Situation Status Tree

• The Situation Status Tree is highly customizable per user within UI − Vary colors used for status indicators

− Tree layout (Tree – Flat – Partial)

− Change number of recent slots/cells to be shown on screen

− Order of the data displayed (MSL – Situation Name – Atom Name)

OMEGAMON For z/OS V5.3

Fixpack 2

Agenda

● Enhancements

● Multi-Threading

● Storage Class Memory (ref)

● LPAR Group 4Hr Rolling Average (ref)

Fix Pack Content - Multi-Threading

• Single threaded CPU cores, in conjunction with z/OS and PR/SM, already optimize

processor cache utilization through “nesting” of a workload's dispatchable units under

HiperDispatch.

• The IBM z13 processor, in conjunction with z/OS version 2.2 (and z/OS version 2.1

+ PTFs), introduces support for multi-threading of CPU cores such that individual threads

are viewed as Logical CPUs by z/OS (LOADxx PROCVIEW CORE).

• When configured by z/OS at the processor class level, CPU core-level threads run

simultaneously such that a thread waiting for a completion of an operation such as cache

miss resolution can allow another thread to execute while waiting to resolve a miss.

• z/OS version 2.2 and the IBM z13 will support zIIP processors being configured as

multi-threaded for 2 simultaneous threads (IEAOPTxx MT_ZIIP_MODE = 2).

• Improvements in a CPU core's performance are best achieved by transactional workloads

whereas Batch workloads are least likely to see performance gains.

Attribute Descriptions(1)

● LPAR Name: Name of the multi-threaded logical partition

● Total Cores: Total number of multi-threaded cores configured to

the logical partition

● Total Threads: Total number of threads (logical CPs) running on all

cores configured to the logical partition

● Measurement Interval: Interval, in seconds to three decimal places, that

the workspace metrics represent.

Attribute Descriptions (2)

● Core Type: The core's processor class, CP or zIIP.

MT Mode: The number of threads configured for the processor class.

● MT Mode: The number of threads configured for the processor class.

● Capacity Factor Maximum: How much work a core can complete for a given workload

mix, usually between 1.0 and 1.4.

● Capacity Factor Achieved: How much work an MT=2 core actually completes relative

to an MT=1 core.

● Average Thread Density: Average number of executing threads during Core Busy

Time, varies between 1.0 and 2.0.

● Total Share%: Total % of the physical processor class that the configured

cores are entitled to use (100% = 1 physical core)

● LPAR Busy%: Average % of the logical partition's online time that the

configured cores in the processor class were dispatched

to the partition (Hipervisor view of utilization).

● MVS%: Average % of the logical partition's online time that a

processor class's threads (logical CPUs) were busy (z/OS

view of utilization).

● MT Productivity%: Percentage of a processor class's maximum core capacity

utilized in an interval while its cores were dispatched to the

physical hardware. Range is 0-100% where less than 100%

indicates that one or more threads experienced waiting for

work during the interval.

● MT Utilization%: Percentage of a processor class's maximum core capacity

utilized during an interval.

MT Utilization% = MT Productivity% x LPAR Busy%

● OMEGAMON 3270 Commands - Modified SYS Major ENV Minor Command

If LPAR is configured for Multi-Threading the maximum and configured threads per core are displayed

● OMEGAMON 3270 Commands – Modified HDSP Immediate Command

One row is displayed for each thread (Logical CPU) running on a Core.

Logical CPU MVS % and Park % metrics are presented at thread-level. All other metrics are presented at, and only relevant at, the core-level.

● OMEGAMON 3270 Commands – New MSMT Immediate Command

Multi-Threading Productivity and Utilization Percentages are shown at the Processor Class and individual processor level..

Logical CPU MVS % and Park % metrics are presented at thread-level. All other metrics are presented at, and only relevant at, the core-level.

OMEGAMON For CICS V5.3

• Integrated monitoring solution with both Enhanced 3270 User Interface and Tivoli Enterprise Portal displays of vital CICS and CICS Transaction Gateway performance information.

• Allow users to specify which OMEGAMON CICS agent will monitor a CICSplex.

• Support for Multi-servant WebSphere clients.

Efficiency and cost savingEfficiency and cost savingEfficiency and cost savingEfficiency and cost saving

OMEGAMON XE for CICS on z/OS V5.3OMEGAMON XE for CICS on z/OS V5.3OMEGAMON XE for CICS on z/OS V5.3OMEGAMON XE for CICS on z/OS V5.3

• Additional resources (ICEs and AIDS) can be monitored and controlled from the Enhanced 3270 User Interface.

� Enhanced 3270 User Interface Near-Term-History allows recent

performance problem identification.

• View performance metrics from the recent history to identify periods of concern.

• Navigate consistently for a given time slice as though in real time.

• Navigate to Task History for a point in time.

� CICSplex wide views of transaction details in both real time and

Increased Problem DeterminationIncreased Problem DeterminationIncreased Problem DeterminationIncreased Problem Determination

� CICSplex wide views of transaction details in both real time and historically.

• See all the CICS regions involved in a transaction combining the task

history details for a transaction from anywhere in the CICSplex.

� Combine Application Trace data for a transaction.

• Access to all the trace collected for a transaction spanning multiple regions with a simple view.

• Improved navigation with consistent navigation through real time and History and the use of tabbing within workspaces to better organize the data.

Reduced timeReduced timeReduced timeReduced time----totototo----resolutionresolutionresolutionresolution

• Faster resolution through new improved Enhanced 3270 User Interface workspaces including embedded data bringing pertinent information from multiple components.

• Reduce the complexity and the navigation by bringing all that is known about a resource to where you need it.

• From z/OS display an address space and if it is a CICS region see the useful CICS metrics without switching views.

• CICS is using WebSphere MQ, see the Queue Manager Statistics and Queue details without leaving the CICS view of a region or task.

• Resolve RLS performance problems with OMEGAMON XE for storage details of the physical dataset performance.

• See which CICS Transaction Gateway servers are using your connections or which CICS regions a gateway is connected to.

Lower cost of OwnershipLower cost of OwnershipLower cost of OwnershipLower cost of Ownership

• Increased usage of specialty processors.

• OMEGAMON CICS now dispatches bottleneck Analysis on a zIIP processor automatically if one is available.

• Up to 94% CPU reduction may be realized.

• Simplify the install of OMEGAMON components into CICS regions.

• For the first time OMEGAMON supports installation into a CICS region with NO JCL CHANGES. Significantly reducing the cost of deploying the product across increasingly complex CICS environments.

• Simplified Installation and Configuration with Parmgen enhancements.

• First time user enhancements make it easier to get up and running.

• Best practices and model based configuration built into a new simplified workflow.

• Allows dynamic recognition of Regions as they come online

• Greater protection from rogue applications with Resource limiting extended to include GDSA and container storage.

OMEGAMON XE for CICS on z/OS V5.3

• Transaction details include related transactions across the CICSplex, which increases your ability to solve transaction performance issues in increasingly complex

View Transactions Across a CICSplexView Transactions Across a CICSplexView Transactions Across a CICSplexView Transactions Across a CICSplex

increasingly complex environments.

• In this example CSMI, running in CICS51G2, is related to TEST in CICS51G1 and the details of the related task(s)

are a click away.

Faster Problem Resolution with Application Trace

• In v5.3.0 the application trace facility is enhanced to allow you to trace connected transactions across the CICSplex, which will simplify problem determination efforts

problem determination efforts in complex environments.

• In this example transaction TEST running in CICS51G1 has linked to a mirror task in

CICS51G2.

Customize History Views

• In addition to transaction history a new, customizable, history has been added. This feature allows you to specify reports that will be collected, allowing you to view history for

allowing you to view history for selected tables in historical context.

• Did a problem occur at 21:50 yesterday ? The new feature allows you to navigate to the time slot and investigate the problem using historical data.

Embedded Data Improves Cross-Product Integration

• 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

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.

• In this example of embedded data the CICS view of an RLS dataset is combined with data from the OMEGAMON XE for Storage product’s physical view of the same dataset.

Embedded Data Improves Cross-Product Integration

view of the same dataset.

• This allows you to access a more comprehensive view of the dataset than would be available from a single monitor.

OMEGAMON DB2

What is Embedded Data?

•Product provided workspace display its own product data

•Bring relevant data from other products into the hosting product’s workspaces seamlessly

•Navigate directly to other product workspaces seamlessly

•Speeds up problem determination

•For example, CICS data from CICS agent embedded in the DB2 thread workspace if the thread originated from CICS

CICS Embedded data in DB2 workspace and CrossProduct linking to CICS workspaceDB2 -> CICS

– CICS embedded data in a subpanel in •DB2 thread workspaces •CICS RCT Summary workspace

•CICS RCT Summary workspace

– Zoom items to navigate directly to CICS workspaces

DB2 Embedded data in CICS workspace and CrossProduct linking to DB2 workspaceCICS -> DB2

– DB2 embedded data in a subpanel in •CICS transaction workspace •CICS DB2 Connection Summary workspace

•CICS DB2 Connection Summary workspace

– Zoom items to navigate directly to DB2 workspaces

Enterprise Summary

Type ‘/’ next to a DB2 for Options MenuSelect 'C' to CICS Threads

Hit enter next to a CICS thread to Thread Detail Accounting

CICS Embedded Data in Subpanel “CICS Transaction Details”

Zoom Items to Navigate to CICS Workspaces

Zoom item highlighted in white

Zoom Items Target Workspace---------------- -----------------------Tranaction ID CICS workspace “Transaction Detail”

Tranaction ID CICS workspace “Transaction Detail” Task Number CICS workspace “Details for Transaction Task”Current Program ID CICS workspace “Program Details” CICS Region Name Navigation Options popup

CICS Workspace - Transaction DetailsNavigated from zoom item Tranaction ID

CICS workspace KCPTRND

CICS Workspace – Details for Transaction TaskNavigated from zoom item Task Number

CICS workspace KCPTASD

CICS Workspace – Programs DetailsNavigated from zoom item Current Program ID

CICS workspace KCPPRGD

Click Tab CICS Connections to DB2 CICS Connections

CICS ConnectionsSelect 'R' to CICS RCT Summary

CICS Embedded Data in Subpanel “CICS Region Summary for a CICS Region”

Problem Diagnosis Tips

•Make sure DB2 thread is originated from CICS•Make sure CICS agent is up and running•Make sure CICS region connects to DB2 successfully•View -> Workspace Source == > make sure workspace is current with embedded data

•Make sure OA47415/ UA76976 (CICS PTF required for embedded data) was applied•Check SYSPRINT for error messages•Tools -> 1 Trace (User Interface) -> 1 Basic UI Flow of Control ==> check SYSPRINT for trace data for problem determination

OMEGAMON for IMS V5.3

What's New in OMEGAMON IMS v530

New and enhanced 3270UI Content�Application History (ATF)�Bottleneck Analysis�DBCTL�Multiple Systems Coupling (MSC)�Response Time Analysis (RTA)�Shared Queues�OTMA, Tmember and Tpipe

�OTMA, Tmember and Tpipe�Storage Pools�VSAM, OSAM, and database buffer pools�Near Term History (NTH) on eligible workspaces�Embedded data support for CICS�Type-1 IMS Command support

Deprecated componentsJLF has been replaced with z/OS log streams to record ATF dataTRF has been removed. Use ATF and IMS Performance Analyzer for

z/OS instead to produce charge-back or performance reportsSAP has been removedETE has been removedTCR reports removed from distribution DVDIMS 9.1 support

Global definitions moved to a text member

Global definitions moved to a text memberKOIGBLxx has been deprecated, replaced with KIPGLBxxKIPGLBCR sample will create the default KIPGLBxx memberKIPGLBCV sample will convert KOIGLBxx to KIPGLBxxKIPGLBVR sample will verify the syntax of a KIPGLBxx memberPARMGEN allows sharing the global member repository dataset

across an RTE boundary.

Application History (ATF) Enhancements�JLF has been replaced with z/OS log streams reducing storage footprint, especially 64-bit memory which was the subject of an RFE�New startup parameters to support the ATF log streams�SUMMLOGR�DETLLOGR�SUMXLOGR�DETXLOGR�Following startup parameters are deprecated for ATF

�Following startup parameters are deprecated for ATF�BUFFSIZE�ECSAMAX�TOTTRANS�TRACE�Hooks have been removed in favor of IMS Monitor exit in IMS 14.1

Application History (ATF) EnhancementsNew Trace options– Transaction count limit– BMP trace by message/CHKP (each CHKP treated as separate

transaction)New status field to show if trace stopped due to transaction count limitATVD events are now shown in chronological orderChanged startup parameter default for 64-bit memory• ATFBUFF now defaults to 512

• ATFBUFF now defaults to 512Data is written synchronously to system logger eliminating another 64-

bit memory queue and improving throughputATF trace definitions may now use Backup/Restore/Deploy utility

(REXX)– Define common traces in one Classic region and deploy to others– Backup/Restore ATF trace definitions

IMS Exit Usage�All IMS exits and their support routines are located in xKANMODR�xKANMODR is now concatenated in IMS control region STEPLIB rather than the entire xKANMOD library reducing the need to cycle the IMS control region to apply maintenance.�All IMS exits are release agnostic reducing configuration effort�LOGWRT is the Log Writer user exit and is used by the RTA component.

component.�PPUE is the Product Partner User Exit used by our IMS type-1 command support�IMSMON is the IMS Monitor user exit used by the ATF component for IMS v14.1 only

Currency�Day 1 support of IMS v14.1�Latest CICS release support�Toleration of 128 CPUs per LPAR�Removed 10+ hooks into IMS and now use IMS exits where available

Miscellaneous ItemsRFE. Automatically start RMONRFE. Add SQ Affinity count to IMS Health workspaceRFE. Add startup message to console for automationFeedback. Added ATF Status column to Monitored IMS SystemsFeedback. Added Zoom capability to several e3270UI workspacesFeedback. Added ASIDX to KIPDEPS for use with Take ActionICAT removal. PARMGEN is only configuration tool now.

ICAT removal. PARMGEN is only configuration tool now.

OMEGAMON for Messaging V7.3

OMEGAMON XE for Messaging v7.3 Highlights

• 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

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

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 3270 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

• Monitor the health of all queue managers in your enterprise using either the Enhanced 3270 UI or the Tivoli Enterprise Portal

• Navigate directly to other OMEGAMONs

Efficiency and Cost Saving through Integration

Increased Problem Determination Capability

• Understand information related to when the problem began with Enhanced 3270 User Interface Near-Term-History

• Easily see when a queue depth began to rise, and select for details

details

• Effortlessly explore data around when a channel goes into retry status

• Quickly view CICS or z/OS Enhanced 3270 User Interface embedded data for applications or queues, with automatic detection of application type

• MQ workspace includes relative CICS or z/OS monitoring data

• Click on any white

Cross Product Embedded Panels

• Click on any white field name to zoom to workspaces in the other OMEGAMON

• Easily navigate forward and backward among the workspaces

• Directly access queue manager z/OS address space monitoring data in Enhanced 3270 User Interface workspaces for both MSTR and CHIN

• Zoom from Current Queue Manager Status to this MQ workspace with z/OS CPU monitoring data

Reduced time-to-resolution of problems

• Zoom on Job Name for direct access to the following z/OS options:

• Immediately display any MQ data available with MQSC display or ping commands from most MQ workspaces in the Enhanced 3270 User Interface

Reduced time-to-resolution of problems

OMEGAMON For Storage V5.3

Efficient Space Processing

• Eliminates redundant issuing of LSPACE

• Dynamically invoked when applicable

• Requires z/OS 1.13 and above

• Storage agent must be active on every member of the

Sysplex

• Recommendation to collect space data on only one system in a shared DASD environment remains valid

• Exclude list (KDFDEVSU member of RKANPARU) is still honored

Efficient Space Processing - Modes

• Three processing modes– ON

• Default mode

• Efficient Space Processing controlled dynamically based upon status of sysplex

members in XCF group

– OFF

• Set manually

• Efficient Space Processing disabled on this z/OS image AND on all other z/OS

images in the sysplex unless overridden

– Force

• Set manually

• Efficient Space Processing enabled for this z/OS image regardless of the status

of other z/OS images in the sysplex

• Manually setting Efficient Space Processing mode– ESPMODE(xxx) where xxx is ON, OFF, or FORCE in KDFDEVIN member of

RKANPARU dataset

– /F tems-name,DFESP MODE,xxx with xxx is ON, OFF, or FORCE

New Attributes

– S3_Channel_Path attribute group• zHPF Requests per Second

• zHPF Requests Deferred per Second

– S3_Cache_Devices attribute group• zHPF Read I/O Requests

• zHPF Read I/O Requests

• zHPF Write I/O Requests

• zHPF Prefetch Requests

• zHPF Prefetch Hits

• zHPF Read I/O per Second

• zHPF Write I/O per Second

• zHPF Prefetch Hit Percent

• zHPF Request Percent

Channel Path Report

New Attributes

Total Storage CU Volumes

New Attributes

E3270 Embedded Data

• The Enhanced 3270 UI embedded data feature brings relevant data from other products into the hosting product's workspace in a seamless manner. This seamless integration of relevant

data and navigational ability speeds up problem

data and navigational ability speeds up problem determination and the users understanding of the data.

• Storage data is embedded in OM XE for Messaging and OM XE for CICS.

• Available as a PTF for v520.

• Embedded data with other OMEGAMONs is planned for a future release.

E3270 Embedded Data - CICS

• CICS scenario: User sees that transactions using VSAM RLS datasets are experiencing performance problems. In order to gain a fuller view of the dataset

In order to gain a fuller view of the dataset statistics for these datasets the user wants to see dataset statistics from the Storage product within the CICS workspaces.

• Key fields include average response time, CA/CI splits, DIWA lock requests.

E3270 Embedded Data - CICS• CICS RLS File Details w/s has VSAM RLS statistics from the Storage

product.

E3270 Embedded Data - Messaging

• Messaging scenario: A situation indicates that the MQ page set is not available. In order to get a deeper view of the dataset activity, the user wants to see performance and space statistics from the Storage product.

• In order to take full advantage of the embed, the Storage

• In order to take full advantage of the embed, the Storage product must be configured to monitor performance, including I/O (at the volume level or via application monitoring monitoring).

E3270 Embedded Data• MQ Page Set Statistics w/s – use action “d” to view page

set details.

E3270 Embedded Data

• Page Set Dataset Details w/s has Space and Performance data from the Storage product.

E3270 Near Term History

• Provides access to TEPS/TEMS “short term history” data stored in PDS (persistent data store) files.

• “h” action key is now reserved for accessing history screens. Previous h actions have been changed.

• Part of HKOB730 (OMNIMON base v7.3)

• PARMGEN change: the default allocation for the

• PARMGEN change: the default allocation for the RKS3DSA1 group has been increased to allow for 3 days retention. Your allocation value will most likely require tuning.

• History configuration can be edited in either E3270 or TEP.

• Configuration gotcha: enabling TEPS-only features (e.g. data warehouse options) will prevent you from modifying the configuration in E3270. Data will be available regardless.

E3270 Near Term History

• Attribute groups which are NTH-enabled– Cache CU and Devices

– Channel Path

– Volume Group Summary

– DASD Volume Space and Performance

– Dataset Attributes System Summary

– Logical Control Unit

– RLS Lock Structure, Buffer LSU, Perf, Storage Class

OMEGAMON for Mainframe

Networks V5.3

Subject Matter ExpertAnnette

Operations Analyst

Senior SysProg

IT Operations Manager

Working together for an integratedcapability and

common goal: Efficiency,

Effectiveness & Collaboration

• Increased efficiency – enhanced 3270 user interface near-term history capability introduced to provide real-time and historical problem

OMEGAMON XE for Mainframe Networks version 5.3

history capability introduced to provide real-time and historical problem analysis from the same user interface

• Decreased problem resolution time and effort in the

enhanced 3270 user interface with:• Integration of networks with z/OS or messaging on a single workspace;

extendable to other domains (e.g. CICS, DB2)• Improved navigation with FIND command and improved menus• Debug problems faster with network diagnostic commands• Identify overall TCP/IP, VTAM, and buffer pool issues• Identify gaps in monitoring using the enterprise health workspace

• Reduced Time to Value (TTV) and Total Cost of Ownership (TCO) – Simplified install/config/maintenance, including PARMGEN first time user function, for up to 60% less time and effort

OMEGAMON XE for Mainframe Networks v5.3

• Understand information related to when the problem began with near-term history in

the enhanced 3270 user interface

Increased efficiency

Easily see when an application has high percent out of order segments and select for details

Effortlessly explore data around when the out of order segments occurred

segments and select for details

Decreased problem resolution time and effort

� View TCP connections and z/OS address space details together to understand when network performance is impacted by z/OS resource constraints

� Zoom into OMEGAMON on z/OS workspaces to investigate further into bottlenecks, storage usage, and WLM

bottlenecks, storage usage, and WLM

service classes

� View TCP connections and TCP listeners for a queue manager’s channel initiator address space to understand if network performance is impacting the processing of messages.

� Navigate to OMEGAMON XE for Mainframe Networks workspaces to

Mainframe Networks workspaces to

investigate further into any potential network performance issues

� Quickly FIND network resources

� Locate TCP connections,

� Locate TCP connections, FTP sessions, FTP transfers or TN3270 Sessions in your enterprise

� Then navigate in context or issue Take Action commands against a selected network resource

� Debug network problems faster

� Issue PING, NSLOOKUP and TRACERTE commands while viewing any workspace in the enhanced 3270 user interface

� The command is issued from the selected system and the output is displayed in the Command and Response Log workspace

IBM Operational Analytics for

IBM Operations Analytics for z Systems

z/OS SYSLOGInsight Pack

WAS SYSPRINT

Generic

Receiv

Applications Search

Mainframe

WAS SYSOUT

z/OS Syslog

CICS MSGUSR

USS Log Files

SMF Data

Arrows show flow of data from

logs to IOA user interface

WAS for z/OSInsight Pack

Generic

Receiv

z/Linux

Syslog

USS Log Files

� z/OS Log Forwarder / SMF Data Provider installed on each z/OS LPAR where you want to provide Search and Analysis

� The IBM Operations Analytics server is installed on z System (or x System) running Linux (64 bit)

� z/OS Insight Packs are installed on the IBM Operations Analytics server

OMEGAMON Insight Pack

The OMEGAMON Insight Pack provides analysis of the RKLVLOGs. RKLVLOGs

contain messages from the monitoring agents and the Hub and Remote TEMS.

Annotations (patterns) are provided for:

• Message ID• Message Text

• Trace Information

Search multiple RKLVLOGs from a single search bar and quickly find the source

of the problem..

Session feedback

• Please submit your feedback at

http://feedback.gse.org.uk/OA

• Session is OA

This is the last

slide in the deck

• Session is OA

Reference Slides

What is OMEGAMON Dashboard Edition?

Who is entitled to OMEGAMON Dashboard Edition?

– Included in all three suite offerings:

•Service Management Suite for z/OS

OMEGAMON Dashboard Edition on z/OS is a license that allows

customers access to enhanced features and greater

integration of their monitoring environment.

•Service Management Suite for z/OS

•Performance Management Suite for z/OS

•OMEGAMON for z/OS Management Suite

– Ordered individually for customers not using one of the suites

What product components are provided with OMEGAMON Dashboard Edition?

– HKWO310 OMEGAVIEW II 310

– HKMV310 OMEGAVIEW 310 (APAR OA47760)

– JKWO530 OM DE INSTALL 530

OMEGAMON z/OS

Situation Data Collection

Hub TEMS(z/OS)

Periodic requests are sent out from the TOM to all known Hub TEMS (via DRA) to get

situation status.

The default is every 5 minutes

Data stored within TOM address space.

Hub TEMS(Window)

Hub TEMS(Linux)

Hub TEMS(AIX)

The default is every 5 minutes

Fix Pack Content – Storage Class MemoryThe IBM zEC-12 processor, in conjunction with z/OS version 1.13, introduced support for

configuration of Storage Class Memory (SCM) amongst LPARs in a CPC through the Flash

Express product offering.

LPARs configured with SCM will page most types of z/OS pages to SCM (VIO and PLPA

are exceptions) before paging to Local Page Datasets (DASD).

SCM reserves areas exclusively for both 4K and 1 Megabyte pages but 1 Megabyte pages

may be broken up into discontiguous 4K pages if paging to a contiguous 1 Megabyte block is

not possible due to utilization levels.

At times of high paging demand, and when an internal active I/O request threshold is

exceeded, internal z/OS algorithms are run to determine if a page-out operation to SCM be

deferred to Local Page datasets. The algorithm's decision is based on the utilization of SCM

and the comparison of service times between SCM and DASD.

In general paging to SCM is much faster than paging to DASD so it's desirable to avoid

“overflow” to Local Page datasets for SCM-eligible pages.

Fix Pack Content – Storage Class Memory

Measurement Interval: Interval, in seconds to three decimal places, that

● Measurement Interval: Interval, in seconds to three decimal places, that

● SCM Service Time: Lowest recent service time for Storage Class

● Local Paging Service Time: Lowest recent service time for Local Paging

● SCM+Local Paging % Used: Combined SCM and Local Page Dataset

● Total Allocation: Total number of 4K SCM blocks configured to the

● Total In-Use: Total number of SCM blocks currently in use by the

● Percent Used: Percentage of SCM blocks configured to the LPAR

● Backed Shared Groups: Number of LPAR Shared Page Groups backed in SCM.

Release Content – Storage Class Memory

● Backed 64-Bit Shared Pages: Number of LPAR Shared 64-bit Pages

Backed 64-Bit Common Pages: Number of LPAR Common 64-bit Pages

● Backed 64-Bit Common Pages: Number of LPAR Common 64-bit Pages

● 1 Megabyte writes Demoted: Number of LPAR 1 Megabyte Pages written

● Active I/O Threshold: Count of LPAR active SCM I/O output

Blocks in Error: Number of SCM blocks that are “in error”

● Blocks in Error: Number of SCM blocks that are “in error”

● Total 4K Reqs Completed/Sec.: Total number of 4K SCM requests completed

● Total 1M Reqs Completed/Sec.:Total number of 1 Megabyte SCM requests

● Total 4K Writes Completed/Sec.: Total number of 4K SCM writes completed

● Total 1M Writes Completed/Sec.: Total number of 1 Megabyte SCM writes per

● Total Page-Ins/Sec.: Total number of 4K SCM page-ins per

● Total 1M Page-Ins/Sec.: Total number of 1 Megabyte SCM page-ins

● Total Page-Outs/Sec.: Total number of 4K SCM page-outs

Total 1M Page-Outs/Sec.: Total number of 1 Megabyte SCM page-outs

● Total 1M Page-Outs/Sec.: Total number of 1 Megabyte SCM page-outs

● Deferred Non-Fault Pages/Sec.:Count of SCM I/O output requests per

● Deferred Page-Fault Pages/Sec.: Count of SCM I/O output requests per

Fix Pack Content – Storage Class Memory (Flash)

● OMEGAMON 3270 – SCMR Minor of the MSCM Major Command

LPAR-wide metrics provide SCM and Local Page Dataset service times, overall paging utilization, allocation and utilization of SCM, 64-bit backing, large page demotion, SCM blocks in error, active I/O threshold, page deferral and roll-up of address space metrics.

Address space level metrics provide paging, write and request rates for both 4K and 1Meg operations.

Fix Pack Content – Storage Class Memory (Flash)

● OMEGAMON 3270 – SCMC/SCMT Minors of the MSCM Major Command

SCMC is similar to SCMR except the metrics are counts of operations of a given measurement interval.

SCMT metrics provide counts of operations for the life of the each address space and the LPAR since IPL.

Fix Pack Content – LPAR Group 4-Hour Rolling Average

Internally, z/OS maintains up to 48 individual sets of buckets to accumulate MSU

consumption metrics at 5-minute granularity on each LPAR.

In the case of LPAR Groups each LPAR in the group maintains a bucket that contains the

number of MSUs/Hour that are unused based on what was available to the group over a

5-minute period within the LPAR Group Limit.

Several customers using OMEGAMON XE on z/OS expressed a preference for the

measurement of LPAR Group utilization to be available as the Used Group MSUs/Hour in

addition to the Unused Group MSUs/Hour.

This can be considered a more intuitive approach to helping a customer determine when an

LPAR Group's utilization is close to, or at, its LPAR Group Limit and capping imminent or in

effect.

Fix Pack Content – 4Hr Rolling Average

● Current % Group Capacity: Percentage of LPAR Group Capacity used over the most

recently completed 5-minute z/OS monitoring interval.

● Current Used Group MSUs: Number of MSUs/Hour used over the most recently

completed 5-minute z/OS monitoring interval.

● Current Unused Group MSUs: Number of MSUs/Hour not used but were available to

the LPAR Group over the most recently completed

5-minute z/OS monitoring interval.

● Average % Group Capacity: Percentage of LPAR Group Capacity used over the

entire 4 hours of the z/OS rolling average monitoring

interval.

● Average Used Group MSUs: Number of MSUs/Hour used over the entire 4 hours

of the z/OS rolling average monitoring interval.

● % Group Capacity: Percentage of LPAR Group Capacity used over a specific

5-minute z/OS monitoring interval in the overall 4 hour

rolling average.

● Used Group MSUs/Hour: MSUs/Hour used over a specific 5-minute z/OS monitoring

interval in the overall 4 hour rolling average.

● e3270UI – Navigation to 4-Hour Rolling Average MSU Statistics

● e3270UI – KM5MSUO Workspace Enhancements

LPAR Group's Used MSUs/Hour and % Used provide more intuitive metrics related to LPAR Group utilization for all 5-minute intervals in the 4-Hour Rolling Average.

LPAR Group's Used MSUs/Hour and % Used average metrics to complement the existing Average Unused MSUs/Hour. Current metrics provide most recent values based on row 2 of the 5 Minute Intervals sub-panel

● OMEGAMON 3270 – (X)RMSU Minor of the SYS Major Command

OMEGAMON DB2

CICS -> DB2

•Two sets of DB2 embedded data in CICS workspaces 1. DB2 thread data 2. DB2 system health

•DB2 thread data are added to CICS transaction workspace KCPTASDI •DB2 system health is added to CICS DB2 connection summary workspace KCPD2S

•DB2 system health is added to CICS DB2 connection summary workspace KCPD2S

In the Enterprise Summary, Click “/” next to CICSplex to see the Options Menu. Then type D to CICSplex DB2 Connections Summary.

Enterprise workspace KOBSTART

You are now in CICS workspace “CICSplex DB2 Connections Summary”. Click next to CICSR52A to “CICS DB2 Connection Summary”

**note** CICS region CICSR52A has connection to DB2 DB1D.

CICS workspace KCPD2P

You are now in CICS DB2 Connection Summary for region CICSR52A. Subpanel “DB2 System Health” is the embedded DB2 data from DB2 agent.

CICS workspace KCPD2S

Zoom items are provided in the DB2 embedded data (DB2 System Health) that enable customer to navigate to the relevant DB2 workspace.

Zoom items DB2 workspace to navigate to •Users Waiting for Threads System Resource Manager (KDPSUBSM)•Threads Waiting on Locks Lock Conflicts (KDPLKC2)•Current Thread Count DB2 Active Threads (KDPTHD52)•EDM Utilization EDM Pool (KDPEDM2A) •DB2 ID popup with navigation options for DB2 as follows (KDPCPDBZ):

•DB2 ID popup with navigation options for DB2 as follows (KDPCPDBZ):

You could type in any of these options to navigate directly to the corresponding DB2 workspace. For example, if you type in S, you will be navigated to DB2 system statistics.

In the Enterprise Summary workspace, click next to CICSplex PLEXG to see all CICS regions in this CICSplex …

Enterprise workspace KOBSTART

Now you are seeing all CICS regions in CICSplex PLEXG. Click next to CICSR52A to “CICS Region Overview”

**note** CICSR52A has connection to DB2 DB1D

CICS workspace KCPRGNS

Now you are seeing the CICS region overview for CICSR52A. Subpanel “Highest CPU Tasks” displays CICS tasks order by CPU Time. Click next to DB2E in subpanel “Highest CPU Tasks” to Task Details. **note** DB2E is a CICS/DB2 transaction accessing DB2 data.

CICS workspace KCPRGNO

Now you are seeing task details for CICS task DB2E.Click on I/O tab to see Transaction I/O Waits.

CICS workspace KCPTASD

Now you are in Transaction I/O Waits workspace. You should see DB2 embedded data in subpanel “DB2 Thread Data”. The DB2 embedded data is provided by DB2 agent. **note**CICS team places embedded data from other agents ( eg. IMS, MQ, DB2) in this workspace “KCPTASDI”.

CICS workspace KCPTASDI

Zoom items are provided in the DB2 embedded data (DB2 Thread Data) that enable customer to navigate to the relevant DB2 workspace.

Zoom items Target DB2 workspaceThread Status Lock Conflicts (KDPLKC2)Correction ID Thread Detail Locks Owned (KDPTHRDL)Elapased Time Thread Detail Accounting (KDPTHDA2)Wait Time Thread Detail Wait Time (KDPTHRD3)Updates Thread SQL Counts (KDPTSQL1)Commit Thread SQL Text (KDPTSQLT) DB2 ID popup with navigation options for DB2 as follows (KDPCPTDZ):

DB2 ID popup with navigation options for DB2 as follows (KDPCPTDZ):

You could type in any of these options to navigate directly to the corresponding DB2 workspace. For example, if you type in S, you will be navigated to DB2 system statistics workspace.

Networks V5.3

� Investigate interfaces and OSA issues with the OSA command

� Investigate issues with TCP/IP resources with the TCPIP or TCPIPMENU commands

Improved navigation:

� Enterprise Network Workspaces menu

– Access using the E action or the NETWORK or NETMENU commands

� Investigate issues with VTAM resources with the VTAM or VTAMMENU commands

Customize filters and queries by setting site or user profile variables

� When you navigate to a workspace or invoke a command, there are default values for query and workspace filters

� Set site or user profile variables in

� Set site or user profile variables in rtename.UKOBDATF dataset to override the defaults

� View UDP endpoints data in context of an Enterprise Extender connection

� The UDP endpoints data displays the byte rates, datagrams discarded, and queued bytes for all the EE connections on this LPAR

on this LPAR

� View additional information by selecting one of the UDP endpoints and navigating to the UDP Connection Details workspace

� Identify overall TCP/IP and VTAM address space issues

– Discards or retransmits– CPU percent– Paging rate– CSA and private storage usage

� Navigate to VTAM Buffer Pools

summary and details workspaces

Identify gaps in monitoring and issues with your monitoring agents with the Enterprise Mainframe Networks Health workspace

� Invoke HEALTH command from any OMEGAMON XE for Mainframe Networks workspace

� Verify monitoring agents are online

� Verify that data collection is active and configured correctly

� SNA Collector and TCP Collector tabs provide additional information

Monitor your OSA-Express5S adapters in the enhanced 3270 user interface

� Enterprise OSA-Express Ports Overview

� OSA-Express Ports for Channel

OSA-Express Ports for Interface

� OSA-Express Ports for Interface

� OSA-Express5S Ports Details

OMEGAMON For Storage V5.3

Efficient Space Processing –How it works

• TEMS joins an OM XE for Storage XCF Group

– XCF Group name is KS3tems-port-number; KS31980

– XCF member name is KS3SPACEsystem-name; KS3SPACESYSNAME1

– Monitoring is done for group member changes

– Messages are received from other members of XCF Group

– By default efficient space processing is in effect when each member of the

sysplex has a Storage agent that has joined the XCF Group

– XCF Group is hub and sysplex centric

• DADSM post processing exit builds table of devices with changes to the VTOC map

• On an interval

– Table is built of changed devices obtained via received XCF messages and

DADSM exit

– Device changes captured by DADSM exit are sent to other members of XCF

Group via XCF message

• During space collection processing, if the device VTOC has not been altered;

LSPACE is not done for the device

• Space data is collected for all devices at least once, unless masked out via

KDFDEVSU member input

E3270 NTH Configuration

• Select “History Configuration” from the View menu.

E3270 NTH Configuration

• Select the application

• Select an attribute group

Dataset Attributes Group - Review

• The Storage product collects dataset attribute data based on user defined groups.

(Summary view on the Dataset Attributes Group Summary w/s)

Dataset Attributes Group - Review

• A group definition is a set of conditions evaluated over the properties and attributes of a collection of datasets– Properties are dataset properties such as DSN, catalog, SMS class,

VOLSER.

– Attributes are attribute group values which have been collected for the

dataset. Examples: allocated space, EXCPs, percent used, days since

dataset. Examples: allocated space, EXCPs, percent used, days since creation, etc.

• Property conditions are OR’ed

• Attribute conditions are AND’ed

• Example group: all datasets with HLQ=TDSMS.** and management class=PROD where percent used > x or days since creation > 30 days

Dataset Attributes Group – short comings

• Group definitions provide some flexibility but restrictions on properties and attributes make some definitions impossible. – all datasets with HLQ=TDSMS.** AND management class=PROD

where percent used > x AND days since creation > 30 days

• The DAG database can hold a vast amount of data but ITM/TEPS is limited in what it can transport/display.

• Customers make large groups (millions of datasets) and want access to the data.

• Also a need for more advanced filtering and processing options.

Dataset Attributes Group Extractor

• Will be available in v520 via PTF.

• Built on top of the Storage Toolkit as a new action.

• The same authentication/permission requirements apply as with any toolkit action.

• Runs as low priority batch job.

• Extracts data collected by the dataset attributes group collector.

• Output dataset is FB LRECL=1700. Data is formatted in CSV, with the first record being a header record.

• Concurrent operation of the collector and extractor is not possible. Schedule accordingly.

Dataset Attributes Group Extractor – How To

• Create a dataset attributes group definition

• Run collection

• Navigate to the Dataset Attributes Group Summary workspace

• Select the group or groups you want to extract, right click and choose Extract Attributes

and choose Extract Attributes

• Define the output dataset.

• On the remaining tabs, specify standard storage toolkit parameters such as schedule, job card, etc.

• View the results of execution on the Storage Toolkit workspace

• The data is now available for further processing via

• The data is now available for further processing via REXX, Java, etc or as input into other workloads.

• Or download the member to your PC, change file extension to .csv and load it into your favorite spreadsheet program.

OMEGAMON News - conferences.gse.org.ukconferences.gse.org.uk/attachments/presentations/6... ·...

Documents

Transcript of OMEGAMON News - conferences.gse.org.ukconferences.gse.org.uk/attachments/presentations/6... ·...

IDUG NA 2008 Norbert Jenninger: WhatÆs New - OMEGAMON XE ...

IBMTivoli OMEGAMON XE for IMS on z/OS Version 5.1€¦ · Chapter 1. Overview of configuration parameters The IBM ®Tivoli OMEGAMON XE for IMS™ on z/OS® product, the related OMEGAMON

Program Directory for IBM Tivoli OMEGAMON XE on z/OS V5.3.0

OMEGAMON XE for CICSplex User s Guide, V220 - IBMpublib.boulder.ibm.com/tividd/td/ITOXfCICSPlex/GC... · 2 OMEGAMON XE for CICSplex User ’s Guide, Version 220 Registered trademarks

Using IBM Tivoli OMEGAMON XE for WebSphere MQ ...publib.boulder.ibm.com/tividd/td/ITOMEGAXEfWSMQ/SC... · Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration ... Audit Logging

Configuring the OMEGAMON Product Family: The PARMLIB ... · Configuring the OMEGAMON Product Family: The PARMLIB Alternative Approach ... OMEGAMON XE V420s, OMEGAMON XE for Messaging

PRISM을위한Automation Solution - dbguide.net · OMEGAMON XE for DB2, CICS, IMS CICS PM DB2 PE IMS PM Middleware and Services ITM for M&C IntelliWatch OMEGAMON XE for MQ OMEGAMON

OMEGAMON XE for CICS V530 Short client presentation

OMEGAMON XE for Sybase User’s GuideഀⰀ 嘀㌀publib.boulder.ibm.com/tividd/td/ITOMEGAXEfSyb/GC32-9318-00/en_… · This user’s guide introduces you to the OMEGAMON XE for Sybase.

OMEGAMON XE for IMS on z/OS: OMEGAMON for IMS User's ... - IBM€¦ · OMEGAMON XE for IMS on z/OS Version 5.1.0 OMEGAMON for IMS User's Guide SC27-4439-00 (re-released November 2012)

Program Directory for IBM Tivoli OMEGAMON XE for CICS on z/OS

Historical Data Collection Guide for IBM Tivoli OMEGAMON XE Products

Implementing omegamon xe for messaging v6.0 sg247357

OMEGAMON XE for CICS V530 Long client presentation

Using IBM Tivoli OMEGAMON XE for WebSphere MQ ...publib.boulder.ibm.com/tividd/td/ITOMEGAXEfWMQMon/... · Tivoli IBM ® Version 3.7.0 Using IBM Tivoli OMEGAMON XE for WebSphere MQ

Configuring IBM Tivoli OMEGAMON XE for …publib.boulder.ibm.com/tividd/td/ITOXEfWBI/SC31-6884-00/...Tivoli IBM Version 1.1.0 Configuring IBM Tivoli OMEGAMON XE for WebSphere Business

OMEGAMON XE for Storage V530 Long client presentation

OMEGAMON XE for DB2 User’s Guide, Vഀ - IBM Supportpublib.boulder.ibm.com/tividd/td/ITOMEGAXEfDB2/GC... · 2 OMEGAMON XE for DB2 User’s Guide, V100 Registered trademarks and

Program Directory for IBM Tivoli OMEGAMON XE for DB2 ...

Using IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring, … · 2005-04-24 · About This Book 8 Using IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring, V3.7.0 About This Book