JVM monitor for zosconnect STC
search cancel

JVM monitor for zosconnect STC

book

Article ID: 191256

calendar_today

Updated On:

Products

Mainframe Application Tuner

Issue/Introduction

We are a running zosconnect instance and setup a monitor. So we could collect JVM data to see where the hotspots /most usage occurs but when i invoked the monitor it didnt collect any JVM data. 
When we did the install for MAT we did the JVM install for 64 BIT. Setup the directory and unzipped the members needed.  We're running a supported config Java 8. Is there a profile we need to setup to 'activate' or allow us to collect JVM data in our monitor ?

Environment

Release : 12.0

Component : CA MAINFRAME APPLICATION TUNER

Resolution

We have support for variety of Java workload but we haven't certified MAT with ZOSconnect(It might fall under one of the supported scenario like JZOS, BPXBATCH, BPXBATSL or Librity). The way the Java monitoring works is a bit different that the normal monitors.

There are couple of things that needs to be done from the setup point of view and it depends from environment to environment. Because the collection is done by an agent, we need to modify the libpath or agent path to include the CA MAT JAVA AGENT, to say exactly what needs to be changed I need to see the zosconnect STC joblog. Or you might spot something similar to your environment under Installing Java Support

During Monitor criteria definition There is a Java Criteria specification, where you need to specify the classes that you are interested either as Inclusion or Exclusion list.


Based on the above, MAT will start to collect java activities.