Why monitor Java on z/OS?

Why monitor Java on z/OS?  Is there really that much Java on z?  The answer more and more seems to be that there may be more Java around than you realize.  You may be seeing Java embedded into more and more tools and supporting code.  You may even be seeing some application modernization where legacy code is being re-written to Java.

Omegamon JVM provides detailed analysis of what is happening inside the JVM running on z/OS.  One of the key areas to monitor is Java Garbage Collection (GC).  GC is a typical are of concern in any Java environment, really regardless of platform.  GC being done too often can waste CPU resource.  GC not done often enough can result in memory issues in the JVM.

Here's an example of the Garbage collection data collected by Omegamon JVM.  Note that you may see the GC data both in real time and view the data in history.  History may be important since that gives you an opportunity so see activity over time, and perhaps see trends in usage.