Editing the MJEINPUT file

• The MJEINPUT file contains all of the JVMs currently running on an LPAR. Additionally, each JVM has a corresponding job= statement that the list processor uses to create the targets and properties.
• Each job that you want to monitor must have a port assigned to it. Because BMC AMI Ops Monitor for Java Environments cannot know which ports are acceptable in a specific installation, you must enter these ports manually by using a portrange= or a port= statement. For details, see the following procedure or the commented portrange statement in MJEINPUT.
• Ports are assigned sequentially to each job based on the ranges that you specify. Alternatively, you can specify port= on a specific job to override anything specified on portrange=.

Observe the following rules when editing MJEINPUT:

• Lines are processed sequentially, therefore, any parameter not specified on a job= statement defaults to the previous generic setting.
• Use the job= specification to override any generic setting. For example, if port= is set on a job= line, the portrange is ignored and the port number on the job= statement is used.
• A generic setting is in effect for all subsequent job= statements until the JCL encounters another generic setting. For example, if type=cics is encountered, all job= statements that do not specify type= are set to type=cics until another type=xxx generic is found.
• If you specify more than one target suffix (tgtsuff=), the JCL writes multiple MJETGTxx members. Therefore, each instance of tgtsuff= overrides the previous specification.

To edit the MJEINPUT file

1. Locate the input_dsn (MJEINPUT data set) and open an edit session.
2. Remove the # (comment symbol) from the beginning of the portrange= line.
   Uncommenting this line makes MJEINPUT a valid input file for running the list processor.
3. (optional) If the default settings at the beginning of MJEINPUT are not acceptable, update them as needed.
4. Delete or add job= statements as needed:
   • Delete any job= statements for jobs that you do not want to monitor with JMX.
   • Add statements for any jobs that you want to monitor and that are not currently in the list. For example, you might want to add statements for JVMs that were not running when you ran the list generator.
5. (optional) Update the descriptions for each JVM to be monitored.
   Do not lengthen the descriptions. Use only the space between the single quotes.

6. (optional) If you need to override a generic parameter, update the job= statements as needed.  

   Tip

   To apply a parameter change to a single job statement, include the parameter override value on the same line as that statement. 

   To apply the change to a job statement and each subsequent job statement, put the parameter override value on a separate line preceding the first statement to which it applies. 

   Important

   The JCL omits parameters that are using their default values. If you want to specify a value other than the default, add the parameter to the JCL.

   Parameter	Default value	Description
   pre=xxx	MJE	Three-character prefix for a new PDS member that will contain JMX properties for use in the client JVM This parameter must be on a separate line and cannot be combined with a job= statement.
   path=/xxx	/tmp	Directory for the list processor to write JMX property files for JVMs that use the USS file system for reading properties This parameter must be on a separate line and cannot be combined with a job= statement.
   tgtsuff=xx	00	Two-character suffix for MJETGTxx members This parameter must be on a separate line and cannot be combined with a job= statement.
   portrange= portNumber,portNumber... | startingPortNumber - endingPortNumber	No default	Range of available ports that the JMX JVM communications can use Use a comma to separate individual ports, and use a dash to specify ranges. This parameter must be on a separate line and cannot be combined with the job= parameter.
   secsuff=[xx | NO]	NO	Suffix of the SSL member that you want the new target to use for JMX security Valid values are: NO (the default), which adds SSL member MJESSLNO to the target. MJESSLNO contains no SSL parameters xx, representing a two-character user-specified suffix of an existing SSL member. Alternatively, if you want to create a new SSL member, specify a suffix for the new SSL member You can specify this parameter on a separate line or as part of a job= parameter.
   protocol= [JRMP | IIOP]	JRMP	RMI protocol for the MJEJVM to communicate with remote user JVMs You can specify this parameter on a separate line or as part of a job= parameter. Valid values are: IIOP JRMP
   history=[D | Y | N]	D	Whether to collect history data for a JVM Valid values are: D (the default), uses the value that is specified for the MVHISTORY parameter in MJEINIxx Y, collects history data N, does not collect data You can specify this parameter on a separate line or as part of a job= parameter.
   gcevents=[Y | N]	Y	Whether to collect JMX garbage collector events when garbage collection is triggered by the remote JVM
   gcthreshold=nn	90	Threshold percentage of heap memory at which to generate JMX events  If you specify 0, threshold exceeded events are not collected.
   port=portNumber	No default	Unique port for a particular job You can use this parameter only as part of a job= parameter. Specify a single available port for JMX JVM communications.
   description=jobDescription	No default	JVM description Important This parameter is required for every job= statement.
   prpsdsn=propsDatasetName	No default	Data set that stores JMX property members  You specified a property data set before generating the JVM list (Generating-a-JVM-list). For any job statements that should use a different property data set, use this parameter to specify the alternative JMX property data set.
   hcsecsf=[xx | NO]	NO	Suffix of the SSL member that you want to use for building Health Center security properties for a JVM Valid values are: NO (the default), which adds SSL member MJESSLNO to the target. MJESSLNO contains no SSL parameters. xx, representing a two-character user-specified suffix of an existing SSL member You can specify this parameter on a separate line or as part of a job= parameter.
   hc=[Y | N]	Y	Whether to enable the Health Center on the JVM You can specify this parameter on a separate line or as part of a job= parameter.
   hcgarbage=[Y | N]	Y	Whether the JVM should gather garbage collection data for the Health Center You can specify this parameter on a separate line or as part of a job= parameter.
   hcclasses=[Y | N]	Y	Whether the JVM should gather class data for the Health Center You can specify this parameter on a separate line or as part of a job= parameter.
   hchistint=xx	15	Interval (in minutes) to gather class histogram data for the Health Center Valid values are 5 through 60. If you specify a zero value, no data is gathered. You can specify this parameter on a separate line or as part of a job= parameter.
   hcobjaloc=[O | N]	O	Whether to gather out-of-line memory allocation data for the Health Center Valid values are: O (the default), collects all memory allocations within the JVM N, no memory allocations are collected
   jmxport0=[Y | N]	Y	Whether the PAS should attempt to dynamically determine the JMX port You can specify this parameter on a separate line or as part of a job= parameter.
   hcauthfl=path	--	Fully qualified zfs filename that contains the credentials for Health Center MBean authentication You can specify this parameter on a separate line or as part of a job=parameter.
   hcrizefl=path	--	Fully qualified zfs filename that contains the credentials for Health Center Mbean authorization You can specify this parameter on a separate line or as part a job=parameter.

7. Save the edited MJEINPUT file.