Configuring JVMs in an IMS batch or message processing region

To monitor a Java™ virtual machine (JVM) that runs in an IMS™ Java Batch Processing (JBP) region or Java Message Processing (JMP), add the enablement options for the IBM Z OMEGAMON AI JVMTI agent and OMEGAMON® AI for JVM (KJJ) agent, and then restart the JVM server to pick up the changes.

About this task

For IMS JVMs, IMS supports Java Dependent Regions for both batch and message processing regions. The JVM regions are defined in the IMS PROCLIB member that is specified on the IMS JMP region's JVMOPMAS parameter. JMP batch jobs run Java programs in IMS.

  • If you customized the PARMGEN configuration profiles by using the KCIJPDLA z/OS Discovery Library Adapter (DLA) autodiscovery job that is introduced starting in PARMGEN 4Q16 IF (PTF UA82508), then the $PARSE*-related job generates a list of auto-discovered Java Dependent Regions that are enclosed in the # ************ Discovered IMS Processing Regions ************* section.
  • If there are rows that are generated in this section, active on-line JVMs were auto-discovered at the time the KCIJPDLA job was submitted. Within this section, PARMGEN generates the auto-discovered IMS PROCLIBs directories where the enablement options need to be added. For more information about the KCIJPDLA job, review the job accessible in the Utilities menu. The job is also in the WCONFIG data set.
Important: IMS supports 64-bit Java starting with IMS V14 with PI64142 maintenance. For more information, see the technote: New function APAR that provides JVM 64-bit support.
For information about adding the enablement options, see Configuring Java Applications for Monitoring.

Procedure

  1. Locate the values of the JVMOPMAS and PROCLIB parameters in an IMS JMP batch job, which is shown in the following code block: 
    // ENVIRON=DFSJVMEV, * JVM ENVIRONMENT SETTINGS
// JVMOPMAS=DFSJVMMS * MASTER/STANDALONE JVM OPTIONS
//PROCLIB DD DSN=IMS.PROCLIB,DISP=SHR
  2. Edit the JVMOPMAS member in the IMS.PROCLIB data set and add the enablement options.
  3. Restart the JVM server to pick up the changes.