Defining product initialization parameters

Whether to discover new JVMs and JVM threads automatically

At startup, MainView for Java Environments discovers all JVMs running on the system. AUTODISC controls when to discover new JVMs that are added subsequently:

• YES (the default for z/OS 2.2 or later) automatically discovers JVMs when they are added.

  Warning

  Note

  To use this option, you must be running z/OS 2.2 or later.

• NO (the default for z/OS 2.1) uses timed discovery, which checks for new JVMs at timed intervals (instead of automatic discovery).

  Warning

  Note

  If you select timed discovery, you can change the timed interval and check for new JVMs on demand as explained in Working-with-timed-discovery.

  
  

Whether MainView for Java Environments should automatically create target definitions for Health Center agents without defined targets

Valid values are:

• YES, which creates a target definition that will exist for the lifetime of the JVM
• NO, which tells MainView for Java Environments to use only defined targets to collect Health Center data

SSID of the BMC Execution Component for z/OS (DBC) subsystem on which the NGL instance is running

Level of debugging

Valid values are 0 through 255.

Listener port for unsolicited messages from the MJEJVM to the PAS

The last port for which MainView for Java Environments should search for Health Center agent listeners

You can specify any TCP/IP port on which you have or expect to have an active Health Center agent.

The starting port for which MainView for Java Environments should search for Health Center agent listeners

You can specify any TCP/IP port on which you have or expect to have an active Health Center agent.

Whether MainView for Java Environments should start the Health Center port scan and collect Health Center data

Discovery cycle in seconds

Valid values are 1 through 999.

For DFSMS allocation, the data class that MainView for Java Environments sends to NGL for allocating logset data sets

For DFSMS allocation, the management class that MainView for Java Environments sends to NGL for allocating logset data sets

High-level qualifier for MainView for Java Environments logsets

The product will append this HLQ to the logset name for different record types.

For more information, see Working-with-logsets.

If this parameter is already specified, but a new LSPREFIX is required, perform the following steps to apply the new LSPREFIX:

1. Modify LSPREFIX in the active INI member and save it.
2. Stop the MainView for Java Environments PAS.
3. Restart the NGL agent.
4. Delete logset definitions with the old LSPREFIX.
5. Start the MainView for Java Environments PAS.

For DFSMS allocation, the store class that MainView for Java Environments sends to NGL for allocating logset data sets

Volume name for allocating the NGL log file

The maximum number of dumps that MainView for Java Environments should take

Valid values are 1 though 9.

Timeout value (maximum number of seconds that the PAS should wait for a response from the MJEJVM)

Suffix of the logset members that you want MainView for Java Environments to use

Logset members are named MJELGnxx, where n represents the type of data contained in the logset. You can edit the logset members if you need to change default allocations or retentions. For more information, see Working-with-logsets.

Path for the shell script (RunMjeJvm.sh) that generates the MJEJVM

Suffix of the MJETGTxx target data set

This data set defines target-specific parameters. A default target datasest is available when you start the PAS for automatic discovery of Health Center and traditional WebSphere Application Server (WAS) servant JMX targets.

Number of subtasks active in the JVM  

If MONTCBMAX is exceeded for a JVM, MainView for Java Environments issues message MJETCK22W or MJETCH02W for each affected JVM.

To avoid losing data at JVM shutdown, increase the value of MONTCBMAX to 110% of the maximum number of threads that you want to monitor on the JVM.

Sets the default for MainView Infrastructure (MVI) history collection for MJEJVM targets

You can override this default when defining individual targets.

Valid values are:

• YES (the default), which collects history data
• NO, which does not collect history data

Whether MainView for Java Environments should join enclaves to track CPU usage that does not involve IBM z Systems Integrated Information Processors (zIIPs)

Valid values are:

• M, which joins enclaves for all MainView for Java Environments code
• N, which joins only as required

Message level for NGL debugging

Whether MainView for Java Environments can stop or restart the NGL agent

The NGL agents must be restarted if MainView for Java Environments changes the index for a record, or logset definitions.

Valid values are:

• YES (the recommended value), which automatically restarts the NGL agent if MainView for Java Environments determines that restart is required following a change

• NO, which does not automatically restart the NGL agent. If you specify NO, you must manually restart the NGL agent.
  You might want to specify NO  if you are sharing an NGL PIID with another product.

  Warning

  Note

  Queries using any changed indexes result in data that does not match the query being returned, or no data at all—depending on the change.

The context for the MainView for Java Environments PAS

The default context for the MainView for Java Environments PAS is the job name, but you can choose a different context, such as &SYSNAME.

Whether to collect interval JVM CPU data from NGL logsets

Data is collected each time the JINV is updated. Valid values are:

• ALL, which collects all interval JVM CPU data

• TGT, which collects interval JVM CPU data only for jobs that are MVI targets

  Warning

  Note

  This option requires SMF interval data.

  
  

• NO, which does not collect any interval JVM CPU data

Whether to collect SMF 121-1 records for JZOS