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.
Recently, I worked with an airline company to identify why a few transactions out of hundreds per second were failing. Many z/OS applications act as a TCP/IP server and accept connections from users or applications on other hosts and mobile devices. The application at this customer that is experiencing problems does accept connections from end users, but it also acts as a TCP/IP client to retrieve information from servers running on Linux. Some of the transactions between the z/OS application and Linux servers were failing. Here's a brief... [More]
This is as easy as "one two three" now with OMEGAMON XE on zOS V5.3. First from the LPAR overview screen in the Enhanced 3270UI pick your LPAR with MSU use high - in this example it is Z2 at 98% of MSU Capacity - put "M" in the selection for the 4HR Rolling Average MSU Statistics for Z2.
The "M" shows us the MSU details for the LPAR Z2.
The OMEGAMON Performance Management Suite for z/OS consists of eight OMEGAMON monitors which are packaged together. In common with the other mainframe OMEGAMON products which were made generally available on September 5th, OMEGAMON XE for CICS on z/OS v5.3.0 included new features which are focused on Enhanced 3270 UI near term history and embedded data. Both of these features will help you resolve problems in your CICS environment by ensuring that the data that you need is available quickly, even when that data is from different subsystems or... [More]
On z/OS data collected during the OMEGAMON history collection process is stored in the Persistent Data Store (PDS). In this blog entry we will provide some insight into how to effectively monitor the PDS maintenance process.
The PDS is a set of pre-allocated flat files that are continually reinitialized and reused. T he PDS maintenance process is an automated process which should not require intervention by the system administrator. However, an understanding of the PDS maintenance process will be helpful to system administrators who want... [More]
On z/OS data collected during the OMEGAMON history collection process is stored in the OMEGAMON Persistent Data Store (PDS). In this blog entry we will discuss PDS sizing considerations for the OMEGAMON XE for CICS and the OMEGAMON XE for CICS TG product components.
The PDS is a set of pre-allocated flat files that are re-used on an oldest data basis. When the active PDS data set becomes full, data collection will switch to the next empty PDS file. When there are no more empty PDS data sets, the PDS data set containing the oldest data... [More]
In this blog we will discuss the best practices for configuring Near Term History (NTH) data collection for the OMEGAMON XE for CICS product. The information provided in this blog is applicable for both the OMEGAMON XE for CICS product component and the OMEGAMON XE for CICS TG product component.
The enhanced 3270UI Near Term History feature only requires that history collection be enabled for the desired attribute groups. The NTH reports viewed in the enhanced 3270UI are generated from the same history data that is used for the... [More]
See OMEGAMON value quickly with new PARMGEN functionality designed especially to get your monitoring products running in 3 hours or less!
Check out many of PARMGEN's upcoming enhancements that embody simplicity and speed in maintaining your monitored LPAR runtime environments (RTEs).
Upcoming PARMGEN PTF UA73689 3Q14 Interim Feature (IF) brings significant improvements to the PARMGEN configuration tool. These enhancements cater to all users, whether you are a new first-time-user (FTU) in... [More]
The WebSphere MQ Monitoring Agent is available in IBM Tivoli OMEGAMON XE for Messaging for z/OS, and for distributed platforms in ITCAM for Applications. This agent provides a large number of attribute groups for your convenience in monitoring IBM MQ. However, only a few of the attribute groups are recommended to be enabled for historical collection in order to achieve reductions in agent historical processing, duplication of data, and historical space requirements.
Out of the box, attribute groups MQ Action Log and MQ Event... [More]
'Dear Rocky' answers your System z monitoring and performance tuning questions.
Rocky McMahan, a Senior Software Performance Engineer in Tivoli R&D, offers valuable tips to help you get more out of your Tivoli monitoring software.
I work on a team of operation analysts for a large food and manufacturing company that employs approximately 35,000 workers and had net revenue of over $5 billion dollars in 2013. Our products are also... [More]
When you associate a mouse click with the Enter key in your 3270 emulator session (see the June 21 2013 blog on how to do this)
then with the Enhanced 3270UI you can go ZOOM ZOOM ZOOM from high level issue very quickly to the specific details.
Here is an example using the OMEGAMON Performance Management Suite and the OMEGAMON XE for Storage feature
where we start at the SMSPLEX overview and see the highest DASD Volume response is 23.2 ms
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]
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]
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]