Configuring JVMs in subsystems

With IBM® OMEGAMON® for JVM on z/OS® (OMEGAMON for JVM), the Java™ virtual machines (JVMs) that you want to monitor must be configured to run the OMEGAMON for JVM Java agent.

The OMEGAMON for JVM Agent uses the Health Center instrumentation in IBM JVMs. Starting from OMEGAMON for JVM V5.4.0, the installation of this product includes copies of the Health Center Agent that are compatible with OMEGAMON for JVM.

To configure JVMs for monitoring in OMEGAMON for JVM, use the Java Health Center Agent that is packaged in the OMEGAMON for JVM product. By default, the Health Center Agent is located in the following directory:
/RTE_USS_RTEDIR/RTE_NAME/kan/
which is the common HFS/zFS directory.
Before you configure a JVM, specify the correct addressing mode of Health Center Agent for the JVM:
  • For 31-bit JVMs, use the hca_31 directory.
  • For 64-bit JVMs, use the hca_64 directory.
You can identify which addressing mode the JVM uses from either of the OMEGAMON for JVM autodiscovery workspaces:
  • Enterprise Overview workspace in the OMEGAMON enhanced 3270 user interface
  • JVM Overview workspace in the Tivoli Enterprise Portal
The methods to configure JVMs in different subsystems are similar, which consists of adding the enablement options that enable Java Health Center instrumentation and start the OMEGAMON for JVM Java agent. The enablement options can be added in the following ways:
  • Added as Java command line arguments
  • Added to a JVM options file in an HFS/zFS file or an MVS data set
  • Added to the JAVA_OPTIONS environment parameter in an HFS/zFS file or an MVS data set
Depending on the runtime environment type that you select, you can add the enablement options.
  • For the Health Center Agent, the enablement options that you can add are shown in the following table:
    Table 1. Enablement options for Health Center Agent when the JVM runs in a subsystem
    Runtime environment type Enablement options to add

    RTE_TYPE=SHARING RTEs except for SMP/E-sharing RTEs

    RTE_TYPE=FULL RTEs

    
    -Xbootclasspath/p:/RTE_USS_RTEDIR/RTE_NAME/kan/
     hca_64/lib/ext/healthcenter.jar
    -agentpath:/RTE_USS_RTEDIR/RTE_NAME/kan/hca_64/bin/
     libhealthcenter.so=
     path=/RTE_USS_RTEDIR/RTE_NAME/kan/hca_64,
     level=inprocess,disableCH
    Attention:
    • When the JVM which you add the enablement options to runs in IBM Operational Decision Manager (ODM), you can use a plus sign (+) at the end of the line to allow continuation of the option on the next line.
    • When the JVM which you add the enablement options to runs in IMS, you can use a greater than symbol (>) to enable the continuation of options.
  • For the OMEGAMON for JVM Agent, the enablement options that you can add are shown in the following table:
    Table 2. Enablement options for OMEGAMON for JVM Agent when the JVM runs in a subsystem
    Runtime environment (RTE) type Enablement options to add

    RTE_TYPE=SHARING RTEs except for SMP/E-sharing RTEs

    RTE_TYPE=FULL RTEs

    
    -javaagent:/RTE_USS_RTEDIR/RTE_NAME/kan/bin/IBM/kjj.jar

After you configure the JVM, or any time that you change the configuration, you must recycle the JVM for the changes to take effect.

If you are not sure which JVMs are on the LPAR or which ones you want to monitor, you can start OMEGAMON for JVM, which discovers all JVMs that are running on the LPAR. Then, look at the JVM Overview workspace in the Tivoli® Enterprise Portal or the JVM Statistics (KJJCJS) workspace in the OMEGAMON enhanced 3270 user interface. Both of these workspaces display a list of the JVMs that are running on the LPAR, but are not being monitored. From the list, you can determine the JVMs that you want to monitor and see what type of subsystem runs the JVM.

Also, if you customized the PARMGEN configuration profiles using the KCIJPDLA autodiscovery job that is introduced starting in PARMGEN 4Q16 IF (PTF UA83283), then the $PARSE*-related job generates a list of auto-discovered CICS regions enclosed in a section called:
"# ************ Discovered CICS Regions ************"