Welcome to the System z Management Blog, where you can read the perspectives from System z experts. This Blog provides insights into the System z solution, as well as technical details about specific IBM products.
Looking for interested customers and business partners to participate in IBM SmartCloud Analytics - Log Analysis for z/OS Early Access and Beta Program
In March 2014, IBM launched its new IBM SmartCloud Analytics - Log Analysis z/OS Insight Pack offerings: the first solution in the market to provide log analytics capabilities for z/OS.
As we continue to develop this ground-breaking solution, we would like to collaborate with interested customers and business partners in our Early Access and Beta Program. This program... [More]
To: OMEGAMON Customers and Business Partners
Re: OMEGAMON Beta Program
The OMEGAMON Development team is looking for interested customers and business partners to participate in the Beta Program for the next release of the IBM OMEGAMON family. The Beta Program started on January 13, 2014 with OMEGAMON XE for CICS on z/OS, and on February 17, 2014 OMEGAMON XE for Messaging on z/OS was added. OMEGAMON XE on z/OS beta code will be available soon for download and installation.
Are your DB2 threads getting enough resources? Are the Work Load Manager Enclave (WLM) definitions too restrictive?
If on the Enhanced 3270UI using the DB2 ® active threads summary (select 'T' from the Enterprise Summary) or the DB2 Thread Detail Accounting screen you see that the elapsed time for a distributed thread is greater than the threshold you have set (the plan name DISTSERV and the correlation ID starting with db2jcc_ indicates this is a distributed thread),
Many systems programmers spend hours debugging problems that involve looping or hung transactions. By working together, z/OS and CICS systems programmers resolve these problems much faster by combining the information available from OMEGAMON XE on z/OS and OMEGAMON XE for CICS on z/OS.
A typical scenario is that the z/OS systems programmer identifies an address space with a high (or low) CPU Percent. Most often, this is in response to a situation alert or a reported problem. Starting with the Address Space Overview workspace in OMEGAMON... [More]
You've been storing data collected by OMEGAMON XE on z/OS in the Tivoli Data Warehouse. You can identify problems that occured in the past using the Tivoli Enterprise Portal. You can go learn more and keep your z/OS systems running smoothly by regularly running the following reports on detailed and summarized data:
z/OS Status DASD Issues
z/OS Status WLM Service Class Period
z/OS Utilization Common Storage
z/OS Utilization LPAR Summary
z/OS Utilization LPAR Usage Summary
Deadlocks and timeouts are unresolved contentions in DB2. These unresolved contentions might cause incomplete transactions and might degrade the overall performance of your system. It is important to monitor and resolve these contentions. Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS (OMPE) is invaluable in detecting and analyzing DB2 for z/OS deadlocks and timeouts. The following link takes you to some of IBM's recommended best practices using OMPE to identify where these are occurring then what steps to take to resolve the... [More]
APAR OA43920 ( www.ibm.com/support/docview.wss?uid=swg1OA43920 ) adds support for your OSA-Express5S hardware in OMEGAMON XE for Mainframe Networks version 5. OSA-Express5S is a technology refresh and introduces a new SNMP MIB with a new set of metrics. This APAR adds 4 attribute groups to OMEGAMON XE for Mainframe Networks version 5. Customers who are running OMEGAMON XE for Mainframe Networks version 4.2 will need to upgrade to version 5 in order to monitor OSA-Express5S.
After installing the PTF and fixpack, the new OSA-Express5S... [More]
Recently a zAware customer commented on the value they had received when zAware spotted an anomaly. It all started when they were notified by email from the OMEGAMON XE for z/OS support that feeds their eventing system. They were able to quickly see the event and the issue that zAware had captured. Leveraging OMEGAMON XE for z/OS situation capabilities allowed the customer to monitor for zAware anomalies without having to stare at a display. This is exactly the value IBM built into zAware and OMEGAMON XE for z/OS for our customers and it is... [More]
With the Enhanced 3270UI in OMEGAMON, there can be times the user sees "No Data" conditions on the 3270. The attached technote takes you to a document that is a first place to look for the most common reasons this may happen. It also has a beginner guide to all the major components you need in order to see e3270ui workspaces.
A few years ago I wrote a lengthy article about how the CICS TG monitoring agent delivered as part of the OMEGAMON XE for CICS product opens up the black-box of CICS Transaction Gateway (CICS TG) on z/OS giving system administrators the information required to tune their CICS TG resources in order to optimize throughput and minimize bottlenecks within this key middleware component. Well, as time moves on URLs change and the original article seems to have disappeared into the ether. The details within in it however, are still very much valid and... [More]
The following lists my recommendations for monitoring WebSphere Message Broker or IBM Integration Bus with OMEGAMON XE for Messaging:
For monitoring WebSphere Message Broker v7 and v8, and IBM Integration Bus v9, use v7.1.0 of the WebSphere Message Broker monitoring agent. That is FMID HKQI710 on z/OS. You'll need the latest PTF levels for later broker releases, which includes PTFs UA71110 and UA69753. On distributed platforms for the same agent in ITCAM for Applications, this level is equivalent to the... [More]
ITCAM for Transactions data collectors on z/OS have filtering mechanisms for selecting portions of workloads for tracking and ignoring the rest. The overhead incurred by ITCAM for Transactions in a z/OS address space can be reduced, often significantly, through workload filtering where only units-of-work that are of interest are selected for tracking and the rest are excluded. This can be especially important where the overhead for ITCAM for Transactions to track an entire workload is considered too costly.
With ITCAM for Transactions... [More]
Why monitor CSA and ECSA? Its simple, when common storage (CSA, ECSA, SQA, and ESQA) is exhausted, a system outage will occur. When ESQA is exhausted, further requests for ESQA are allocated from ECSA. When ECSA is exhausted, further requests are allocated from the much smaller CSA storage. The main reasons why common storage shortages occur:
Not enough common storage is allocated
Activity on the system exceeds previous levels, resulting in additional common storage being allocated
An address space allocates... [More]
We had a busy week at SHARE in Boston.
Download the OMEGAMON and NetView for z/OS presentations and see what you missed:
14073: What’s New with System z Monitoring with OMEGAMON - http://share.confex.com/share/121/webprogram/Session14073.html
13498: Managing z/VM & Linux Performance Best Practices - http://share.confex.com/share/121/webprogram/Session13498.html
14121: OMEGAMON XE for Storage - Hints and Tips to Improve Performance and Usage - http://share.confex.com/share/121/webprogram/Session14121.html