Robust new capabilities are provided in OMEGAMON XE for IMS v5.3.0
dkitay 110000HYE0 Visits (13545)
OMEGAMON XE for IMS v5.3.0 is a key part of the IBM® Tivoli OMEGAMON Performance Management Suite for z/OS® v5.3.1 announcement today. With the new OMEGAMON XE for IMS you can find IMS system and application problems more quickly and speed up problem resolution time.
The enhanced 3270 user interface has a large set of new workspaces to better monitor key resources such as: shared queues, response time analysis, IMS Open Transaction Manager Access (OTMA), Bottleneck Analysis, IMS DB Control (DBCTL), Application Trace Facility (ATF) workload history, storage pools, Multiple Systems Coupling, Virtual Storage Access Method (VSAM), Overflow Sequential Access Method (OSAM), database buffer pools, and more. The following is an example of the IMSPlex Enterprise Summary views:
Enhanced 3270 user interface workspaces enable Subject Matter Experts to navigate quickly through data across OMEGAMON products and the ability to see data from multiple products in a single workspace. For example, data from OMEGAMON for IMS and OMEGAMON for CICS is combined to provide consolidated viewing for Global and Local locks and for DBCTL thread details. For example, this Global locks workspace combines IMS and CICS data to more quickly identify the source of a problem:
Near-term history workspaces help you see recent trends and determine when a problem began. Near-term history is available for each of the real-time workspaces in the enhanced 3270 user interface similar to this view of IMSPlex Heath history:
The Application Trace Facility (ATF) summary, exception and detail data can now be viewed within the Enhanced 3270 user interface. In addition to some display enhancements, performance improvements have been made in the collection, storage and reporting of Application history data allowing you to better track your transaction workloads and identify performance problems. In addition IMS Performance Analyzer (IMS PA) has enhanced its reporting of the ATF data. Here is an example of Transaction history summary showing average CPU, average and maximum elapsed response time and counts for any abends:
Some additional enhancements include the ability to send Type 1 or Type 2 commands to an IMS system, the addition of some metrics to various workspaces including the Health Summary views, and a tool to help backup, restore and deploy ATF trace definitions across multiple IMS systems to help you standardize your data collection.
Read the full announcement at http