IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools > Using system dumps and the dump viewer > Using the dump viewer
![]()
Support for compressed files
When you run the jdmpview tool on a compressed file, the tool detects and shows all system dump, Java™ dump, and heap dump files within the compressed file. Because of this behavior, more than one context might be displayed when you start jdmpview.
The context allows you to select which dump file you want to view. On z/OS, a system dump can contain multiple address spaces and multiple JVM instances. In this case, the context allows you to select the address space and JVM instance within the dump file.
Example 1
This example shows the output for a .zip file that contains a single system dump from a Windows system. The example command to produce this output is jdmpview -zip core.zip:
Available contexts (* = currently selected context) : Source : file:/C:/test/core.zip#core.20120329.165054.4176.0001.dmp *0 : PID: 4176 : JRE 1.7.0 Windows 7 amd64-64 build 20120228_104045 (pwa6470sr1-20120302_01(SR1) )
Example 2
This example shows the output for a compressed file that contains a system dump from a z/OS system. The system dump contains multiple address spaces and two JVM instances:
Available contexts (* = currently selected context) : Source : file:///D:/examples/MV2C.SVCDUMP.D120228.T153207.S00053 0 : ASID: 0x1 : No JRE : No JRE 1 : ASID: 0x3 : No JRE : No JRE 2 : ASID: 0x4 : No JRE : No JRE 3 : ASID: 0x6 : No JRE : No JRE 4 : ASID: 0x7 : No JRE : No JRE *5 : ASID: 0x73 EDB: 0x8004053a0 : JRE 1.7.0 z/OS s390x-64 build 20120228_104045 (pmz6470sr1-20120302_01(SR1)) 6 : ASID: 0x73 EDB: 0x83d2053a0 : JRE 1.7.0 z/OS s390x-64 build 20120228_104045 (pmz6470sr1-20120302_01(SR1)) 7 : ASID: 0x73 EDB: 0x4a7bd9e8 : No JRE 8 : ASID: 0xffff : No JRE : No JRE
Example 3
This example shows the output for a compressed file that contains several system dump, Java dump, and heap dump files:
Available contexts (* = currently selected context) : Source : file:///D:/Samples/multi-image.zip#core1.dmp *0 : PID: 10463 : JRE 1.7.0 Linux amd64-64 build 20120228_104045 pxa647sr1-20120302_01(SR1)) Source : file:///D:/Samples/multi-image.zip#core2.dmp 1 : PID: 12268 : JRE 1.7.0 Linux amd64-64 build 20120228_104045 pxa647sr1-20120302_01(SR1)) Source : file:///D:/Samples/multi-image.zip#javacore.20120228.100128.10441.0002.txt 2 : JRE 1.7.0 Linux amd64-64 build 20120228_94967 (pxa6470sr1-20120228_01(SR1)) Source : file:///D:/Samples/multi-image.zip#javacore.20120228.090916.14653.0002.txt 3 : JRE 1.7.0 Linux amd64-64 build 20120228_94967 (pxa6470sr1-20120228_01(SR1)) Source : file:///D:/Samples/multi-image.zip#heapdump.20111115.093819.4336.0001.phd 4 : JRE 1.7.0 Windows 7 amd64-64 build 20111105_94283 (pwa6470sr1-20111107_01 SR1))
Working with Java dump and heap dump files
When working with Java dump and heap dump files, some jdmpview commands do not produce any output. This result is because Java dump files contain only a summary of JVM and native information (excluding the contents of the Java heap), and heap dump files contain only summary information about the Java heap. See Example 3 listed previously; context 4 is derived from a heap dump file:
Source : file:///D:/Samples/multi-image.zip#heapdump.20111115.093819.4336.0001.phd 4 : JRE 1.7.0 Windows 7 amd64-64 build 20111105_94283 (pwa6470sr1-20111107_01 SR1))If you select this context, and run the info system command, some data is shown as unavailable:
CTX:0> context 4 CTX:4> info system Machine OS: Windows 7 Machine name: data unavailable Machine IP address(es): data unavailable System memory: data unavailableHowever, because this context is for a heap dump file, the info class command can provide a summary of the Java heap:CTX:4> info class instances total size class name 0 0 sun/io/Converters 1 16 com/ibm/tools/attach/javaSE/FileLock$syncObject 2 32 com/ibm/tools/attach/javaSE/AttachHandler$syncObject 1 40 sun/nio/cs/UTF_16LE .... Total number of objects: 6178 Total size of objects: 2505382
Parent: Using the dump viewer
Error 404 - Not Found Error 404 - Not Found
The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.