Active JVM targets (JVMDTGT)


Use the Active JVM Targets hyperlink to access the JVMDTGT view, where you can see all JMX monitored targets.

The JVMDTGT view displays all discovered JVMs on the system as shown in the following sample:

>W1 =JVMDTGT===========MJECIQ54=*========26MAR2018==06:40:56====MVJE=====D====2
CMD Job      Target JVM               JVM      HC    JMX   ASID Req      Last  
--- Name     Description              Type     Port  Port       Date     Req Ti
    MJECIQ54 C54JVM2 OSGI auto create CICS OSG  1972 54880 00EA 26MAR201 06:30:
    MJECIQ54 MJEWLP4 WLP auto created CICS WLP  1973 54881 00EA 26MAR201 06:30:

The Target JVM description is from the definition given in the TGTPROF view. A blank description indicates that a JVM is not being monitored with JMX, either because no JVM profile is defined or an error prevented connecting to the JMX port.

You can enter the following line commands in the CMD column for any JVM that you want to affect:

  • ADD starts the JVM Add Targets wizard that enables you to define new targets. For more information, see Setting-up-JVM-targets.
  • CPU schedules a CPU time collection into the specified JVM. Because the collection is done asynchronously, the view might not reflect the new time immediately.

The following hyperlinks are provided on the view:


Hyperlink from

To access

Job Name

EZJE in the context of the selected job

JVM Type

MainView product associated with the JVM type

The following table describes the data fields:


Field

Description

Job Name

Job name that is associated with the address space in which the JVM is running

Target JVM description

From TGTPROF, the description of the discovered JVM

This field is blank if the specific JVM is not being monitored with JMX, either because no JVM profile is defined or an error prevented connecting to the JMX port.

The element name for this field is JVMDESC.

JVM Type

Type of JVM that is running in this address space

HC Port

Health Center port number

The element name for this field is HCPORT.

JMX Port

JMX port number

The element name for this field is JMXPORT.

ASID

Hexadecimal address space of the job running this JVM

The data in this field is represented by hexadecimal numbers.

The element name for this field is ASID.

Req Date

The times when the CPU data is collected

The time value is in MVI time format, based on the Jan 1, 1980 epoch. You can change the format by using the DATE option of the MVPARMS command.

If the date and time show NOT REQUESTED, the times are for threads that have ended since the JVM was discovered.

If all TCBs have not responded to a CPU request, this field might show INCOMPLETE. As long as responses are being returned, the field will stay in that state. If you requested CPU data via the JVMCPU view, no new CPU data will be requested as long as the status is INCOMPLETE.

The element name for this field is DATETIME.

Last Req Time

The last time the CPU data was collected

Last Request CPU Time

The total CPU time used by the task running the JVM, displayed in seconds

This value includes time running on the CP and the normalized time running on support processors.

The element name for this field is CPUTIME.

Last Request CP cputime

The total time spent running on a general processor, displayed in seconds

The element name for this field is TIMEONCP.

Normalized Last SUP CPU

The total time spent running on a support processor as if it were running on a general processor

This value (displayed in seconds) indicates how long the run would have taken on a CP if the SuP had not been available.

The element name for this field is TIMESUPN.

Last Request SUP_on_CP cp

The total time spent running on a general processor instead of a support processor because no support processor was available

This is displayed in seconds.

The element name for this field is SUPTONCP.

Act TCB

The number of TCBs that were requested to report CPU for the JVM

The element name for this field is TCBACTC.

Step Name

If a started task is started with a stepname (S JOBNAME.STEPNAME) this field contains the CHKEY value from the CSCB (i.e. STEPNAME)

If ASCBJBNI is not null, this field contains the same value as the job name. This is the normal situation for a batch job.

The element name for this field is STEPNAME.

Sub Type

The sub type of the JVM that is running in the address space

Possible sub type values for the IBM CICS JVM's are:

WLP—Liberty JVM server with deployed Java web applications such as JSP, JSF, and Servlets
SAML—JVM server that runs the CICS Security Token Service
OSGI—JVM server that runs an OSGI framework with deployed applications that are packaged in OSGI bundles
AXIS2—VM server that runs AXIS2 in order to run Java web services or process SOAP requests in a pipeline

The element name for this field is JVMSTYPE.


Related topic



 

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

MainView for Java Environments 3.1