AIOps: Monitoring and Observability - Group home

What’s New in IBM Z OMEGAMON for JVM, V550 Fix Pack 1

  

2020 has been a busy year for the OMEGAMON JVM development team. In March we released V5.5.0 of the product with a new name and two editions. IBM Z OMEGAMON Runtime Edition for JVM, V5.5.0 is available for customers who simply want to focus monitoring on a few critical Java applications and haven’t made the investment in the OMEGAMON suites. The OMEGAMON Runtime Edition for JVM is a metered offering that allows customers to license the product based on the number of JVMs they monitor. This requires regular Sub-Capacity Report submissions to IBM generated using the Sub-Capacity Reporting Tool (SCRT).  Product capabilities are otherwise identical to the standard IBM Z OMEGAMON for JVM, V5.5.0 which is priced based on MSUs of the target z/OS systems.

V5.5.0 introduced several new features that customers asked for. Notable features include JVM use of z/OS virtual storage for 24-bit, 31-bit and 64-bit areas, health history for JVMs that have completed, and an enterprise view of z/OS Connect API performance statistics.

Fix Pack 1 for V5.5.0 is now available which provides cumulative fixes for V5.5.0 as well as some usability enhancements. A welcome improvement for z/OS Connect EE customers is a new time range selection dialog for the Tivoli Enterprise Portal UI. Analogous to the time and date range selection criteria that can be supplied in the enhanced 3270UI, this allows users to produce summary and detail reports for broader (or finer) ranges than the current default of the last five minutes. The “z/OS Connect Request Filter” dialog is invoked from the action menu by right-clicking the mouse pointer on any z/OS Connect result row (See Figure 1)

Figure 1: Invoking the z/OS Connect Request Filter


The dialog provides two radio buttons that toggle between two selection modes enabling either the last n minutes/hours option, or to input a specific range of date and times to report API statistics. For example, you can produce summary and detail reports for the last 30 minutes, the last 24 hours, or between 8:00 AM and 8:02 AM on August 13th.

Figure 2: Example of the new z/OS Connect EE request filter dialog in TEP

The selected range affects both the table views and the graphs in the TEP z/OS Connect work spaces.

Figure 3: Example z/OS Connect EE API request detail report in TEP

 

The selected range remains in effect for the duration of the TEP session (or until you change it with the time range selection dialog ), so if you view another z/OS Connect report (say by System of Record resource) the UI produces records for the same time range.

S
taying with z/OS Connect, there are new navigation paths available to z/OS Connect Summary History in V550 FP1.  History may be enabled for z/OS Connect Summary data which can be considered as summary “snapshots” of response time data for APIs taken at history collection intervals. The history snapshot is taken using the collection interval as the summary time span. For example, if the history interval for the z/OS Connect Summary data is every 15 minutes, the summary is calculated using data from the previous 15 minutes of activity at the time of the snapshot.

z/OS Connect EE Request Summary History

The summary history is useful because it is retained in Near Term History (NTH) Persistent Data Store (PDS) datasets and optionally archived to the Tivoli Data Warehouse, so it will be available for up to 7 days in NTH or longer in the TDW. The data stored in the z/OS Connect log streams for OMEGAMON JVM may only be available for 24 hours, depending on the retention period of the log stream.

The summary history snapshot records for an API can be examined using the “H” selection character for an API in the z/OS Connect Request Summary panel in e3270UI

Figure 4: Invoking  z/OS Connect EE Request Summary History in the e3270UI

 This action character produces a report of all near term history records for z/OS Connect EE summary requests.  The period covered is dictated by the history configuration settings in the e3270UI.

Figure 5: Example of z/OS Connect EE request summary history report.



Another usability improvement comes in the Enhanced 3270 UI. It has become common to see CICS systems with more than one JVM server defined. The JVM resource workspaces for OMEGAMON for JVM have always included the jobname and the process ID of the JVM, but they did not include the JVM server name and profile for CICS JVMs. That has now been addressed in V5.5.0 FP1. If you select the Garbage Collection data for a CICS JVM, the workspace title now includes the CICS-defined server and profile name.

Figure 6: Example of CICS JVM server name and profile in OMEGAMON for JVM V5.5.0 work spaces


Other OMEGAMON for JVM work spaces got the same treatment in V5.5.0 FP1 which improves usability by confirming the context for the JVM being examined.

For further information about IBM Z OMEGAMON for JVM  see https://www.ibm.com/products/z-omegamon-for-jvm

You can try IBM Z OMEGAMON for JVM using the IBM Z Software Trials  program, a hands-on virtual system without cost or installation. See https://www.ibm.com/it-infrastructure/z/software-trials for details