Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for Java Environments 4.1.

Running the list processor JCL

After editing the MJEINPUT file, you must edit and run the list processor JCL file, MJELPRC. MJELPRC creates target definitions and JVM properties files.

Related topic

Setting-up-JVM-targets-by-using-the-Configuration-Assistant

To run the list processor JCL

  1. Copy the MJELPRC member from the BBSAMP library into your library, and open the file in an editing session.This file reads the MJEINPUT file.

  2. In the job, change the following parameters:

    Parameter

    Description

    input_dsn

    Data set name for the MJEINPUT file

    bbproc_dsn

    BMC AMI Ops Monitor for Java Environments BBPROC data set name

    bbparm_dsn

    BMC AMI Ops BBPARM data set

    This data set contains the JMX target definitions.

    Important

    If a target definition already exists, you need to change tgtsuff= with a unique qualifier.

  3. On the COMMAND line, type submit and press Enter.
    The job creates the following items:
    • MJETGTxx member (or members), containing the JSON required to monitor JMX targets
    • JMX properties files, which enable remote JVMs to connect to the MJEJVM. One property file is created for each target JVM.


Where to go from here

Install the MJETGTxx member as a target in the PAS. For more information, see Installing-the-MJETGTxx-target-into-the-PAS.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*