Product initialization parameters

Number of minutes that BMC AMI OpsMJE should store z/OS Connect EE Interceptor information

Valid values are from 1 through 15.

This number affects the amount of displayed data when you view z/OS Connect Current data in the z-OS-Connect-EE-current-views.

The default value is 5.

Whether to discover new JVMs and JVM threads automatically

At startup, the product discovers all JVMs running on the system. AUTODISC controls when to discover new JVMs that are added subsequently.

Valid values are as follows:

• YES—Default for z/OS 2.2 and later) Automatically discovers JVMs when they are added

  Important

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

• NO—(Default for z/OS 2.1) Uses timed discovery, which checks for new JVMs at timed intervals (instead of automatic discovery)

  Important

  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 the product should automatically create target definitions for Health Center agents without defined targets

Valid values are as follows:

• YES—(Default) Creates a target definition that exists for the lifetime of the JVM
• NO—Tells the product 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

The default value is DC&SYSCLONE.

Level of debugging

Valid values are from 0 through 255.

The default value is 1.

Listener port for unsolicited messages from the MJEJVM to the PAS

The default value is 20333.

EVTZIIP=[YES|NO]

Whether to run the event listener on zIIP

Valid values are as follows:

• YES—Runs the event listener on zIIP
• NO—(Default) Runs the event listener as a task
  Specify NO to keep the backlog to a minimum.

Starting port for which the product 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 default value is 1972.

Last port for which the product 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 default value is 100.

Discovery cycle in seconds

Valid values are from 1 through 999.

The default value is 10.

JMXSEARCH=[YES | HC | NO]

Whether to search for JMX ports

Valid values are as follows:

• YES—(Default) BMC AMI OpsMJE searches for JMX on any server and doesn’t wait for HC to connect.
  You can specify JVMs to include or exclude from JMX Auto Target. By default,BMC AMI OpsMJE includes all JVMs. You can edit the MJEJMX00 member to include or exclude specific JVMs. To change the default member, specify the member suffix in the MJEJMXINI parameter.

  Important

  If a JMX is not configured on a server, but -Xhealthcenter is configured, OpsMJE still autodiscovers the target.

• HC—When Health Center connects, if the JVM doesn't match a specific profile,BMC AMI OpsMJE takes one of the following actions:
  • For non-Liberty JVMs, BMC AMI OpsMJE uses the default JVM profile and attempts to get JMX data from each port on which the monitored JVM is listening.
  • For Liberty JVMs, if a _DEFREST profile is defined,BMC AMI OpsMJE uses the security defined in the profile to request JMX data from the REST interface. For more information, see Using-default-JVM-profiles-to-collect-JMX-data.
    When JMX data is returned, BMC AMI OpsMJE ends the search.
• NO—BMC AMI OpsMJE searches only for static targets that do not have JMX port zero defined.

For DFSMS allocation, the data class that the product sends to NGL for allocating log set data sets

There's no default.

For DFSMS allocation, the management class that the product sends to NGL for allocating log set data sets

There's no default.

High-level qualifier (HLQ) for BMC AMI OpsMJE log sets

The product appends this HLQ to the log set name for different record types. For more information, see Working with log sets.

There's no default.

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 BMC AMI OpsMJE PAS.
3. Restart the NGL agent.
4. Delete logset definitions with the old LSPREFIX.
5. Start the BMC AMI OpsMJE PAS.

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

There's no default.

Volume name for allocating the NGL log file

There's no default.

Maximum number of dumps that the product should take

Valid values are from 1 though 9.

The default value is 5.

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

The default value is 60.

MJEJMX=suffix

Member suffix to include or exclude JVMs from JMX Auto Target

The default value is 00.

For the sample member, see JMX Auto Target inclusion and exclusion parameters (MJEJMX00).

Suffix of the logset members that you want BMC AMI OpsMJE to use

The default value is 00.

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.

(Optional) Job name of the TCP/IP stack

BMC AMI OpsMJEuses the job name to communicate between the MJEJVM and z/OS Connect EE.

There's no default.

By default, BMC AMI OpsMJE uses the job name of the primary stack. If you are running BMC AMI OpsMJE in a multi-stack TCP environment and you want BMC AMI OpsMJE to use a specific stack, specify a value for this parameter.

Suffix of the MJETGTxx target data set

The default value is 00.

This data set defines target-specific parameters. A default target data set 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, the product issues message MJETCK22W or MJETCH02W for each affected JVM.

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

Sets the default for BMC AMI Ops Infrastructure (BMC AMI OpsI) history collection for MJEJVM targets

You can override this default when defining individual targets.

Valid values are as follows:

• YES—(Default) Collects history data
• NO—Does not collect history data

Whether the product should join enclaves to track CPU usage that does not involve IBM zIIPs

Valid values are as follows:

• M—(Default) Joins enclaves for all BMC AMI OpsMJE code
• N—Joins only as required

Message level for NGL debugging

The default value is 8.

Whether the product can stop or restart the NGL agent

If BMC AMI OpsMJE changes the index for a record or log set definitions, you must start the NGL agents.

Valid values are as follows:

• YES—(Default) Automatically restarts the NGL agent if BMC AMI OpsMJE determines that restart is required following a change
• NO—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.

 NGLMAXRECA=number

(BMC.AMIOPS.SPE2301)

(Optional) Maximum number of records to retrieve from the NGL log set All JVM CPU Data

From the main EZ menu, under NGL Logged Data, you can select these data records by using the hyperlinks in the JVM CPU History and JVM Interval Summary fields.

Valid values are from 1 through 99999999.

The default value is 400.

 NGLMAXRECE=number 

(BMC.AMIOPS.SPE2301)

(Optional) Maximum number of records to retrieve from the NGL log set JMX Events

From the main EZ menu, you can select these data records under the JMX Events field. 

Valid values are from 1 through 99999999.

The default value is 400.

 NGLMAXRECG=number

(BMC.AMIOPS.SPE2301)

(Optional) Maximum number of records to retrieve from the NGL log set SMF GC Data

From the main EZ menu, under NGL Logged Data, you can select these data records by using the hyperlinks in the SMF GC Data and SMF Interval GC Data fields.

Valid values are from 1 through 99999999.

The default value is 400.

 NGLMAXRECC=number

(BMC.AMIOPS.SPE2301)

(Optional) Maximum number of records to retrieve from the NGL log set SMF CPU Data

From the main EZ menu, under NGL Logged Data, you can select these data records by using the hyperlinks in the SMF CPU Data and SMF Interval CPU Data fields.

Valid values are from 1 through 99999999.

The default value is 400.

 NGLMAXRECZ=number

(BMC.AMIOPS.SPE2301)

(Optional) Maximum number of records to retrieve from the NGL log set z/OS Connect EE Data

From the z/OS Connect EE menu, you can select these data records under the z/OS Connect EE Detail field. 

Valid values are from 1 through 99999999.

The default value is 400.

Alternate context for the BMC AMI OpsMJE PAS

Whether to collect interval JVM CPU data from NGL log sets

Data is collected each time the JINV is updated.

There's no default.

Valid values are as follows:

• ALL—Collects all interval JVM CPU data

• TGT—Collects interval JVM CPU data only for jobs that are MVI targets

  Important

  This option requires SMF interval data.

• NO—Does not collect any interval JVM CPU data

Whether to collect SMF 121-1 records for JZOS

The default value is YES.

TRACEPATH=path