Current Active JVM (JVMDISC)
Use the Current Active JVM hyperlink to access the JVMDISC view, which lists all JVMs that are currently running.
The JVMDISC view displays all discovered JVMs on the system, as shown in the following sample (PTF BPF0286 applied):
CMD Job JVM ASID Process Current Active Target JMX HC Lst
--- Name Type ID TCB Cnt
BAQSTRGA Zconnect 010F 17367699 5D3420 Yes Yes Yes Yes 5
IZUSVR1 Liberty 009D 17367108 5D8210 Yes No No No 1
MJEJVMSN java 0148 50924739 5EE0D8 Yes No No No 2
MJEJVMSN java 0148 34146346 5BEE88 Yes No No No 1
MJEJVM33 MJEJVM 023D 17370358 5C4430 Yes No No No 1
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 menu in the context of the JMX target |
JVM Type | MainView product associated with the JVM type |
ASID | MainView for z/OS Summary job I/O utilization view (JIOZ) |
Process ID | MainView for UNIX System Services easy menu for the process ID |
Active | Discovered JVMs Detail view (JVMDISCD) |
Target | (When the value is Yes) JVMDTGT view for the job in the context of JMX target Note: This hyperlink is active only when the JVM is defined as a MainView target. |
JMX | (When the value is Yes) EZJE in the context of the job name Note: This hyperlink is active when JMX statistics are available and the port has been verified. Other values for JMX:
|
Lst Cnt (PTF BPF0286 applied) | JMVLSPT displaying all active listener ports for the selected job name |
Last Request Time | An update of the data for the line |
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 |
JVM Type | JVM type as defined by MainView for Java Environments Possible values are:
|
ASID | Address space ID The hexadecimal address space of the job running the JVM. |
Process ID | Process ID (PID) that is assigned to the JVM by Unix Systems Services This identifier is unique for each JVM running, even when multiple JVMs run in the same address space. The element name for this field is PID. |
Current TCB | Main TCB address of the JVM running in the address space The data in this field is represented by hexadecimal numbers. The element name for this field is TCBADDR. |
Active | Whether the JVM is currently active on the system |
Target | Whether the JVM has been defined as a MainView target The element name for this field is TGTBOOL. |
JMX | The availability of JMX statistics for this JVM Possible values are:
|
HC | Whether Health Center is active for the JVM The element name for this field is HCACT. |
Lst Cnt (PTF BPF0286 applied) | Number of listener ports that are available for a job name |
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 CPU data is requested 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 CPU Time | The total time spent running on a general processor, displayed in seconds The element name for this field is TIMEONCP. |
Normalized Last SUP CPU Time | 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 value is displayed in seconds. The element name for this field is SUPTONCP. |
Undetermined TCBTTIME CPU | The number of CPU seconds that were gathered using TCBTTIME because TIMEUSED was not available The element name for this field is TIMEUNSP |
RPT CNT | The number of TCBs that responded to the IRB request for JVM CPU data The element name for this field is TCBREPC |
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. |
Sub Type | The sub type of the JVM that is running in the address space Possible sub type values for IBM CICS JVM's are:
The element name for this field is JVMSTYPE. |
Step Name | If a started task is started with a step name (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. |
Related topic