IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools > Using the Reliability, Availability, and Serviceability Interface
Formatting
You can use J9TraceFormat.dat to format JVM-generated tracepoints that are captured by the agent. J9TraceFormat.dat is shipped with the SDK.
J9TraceFormat.dat consists of a flat ASCII or EBCDIC file of the following format:
5.0 j9vm 0 1 1 N Trc_VM_VMInitStages_Event1 " Trace engine initialized for module j9vm" j9vm 2 1 1 N Trc_VM_CreateRAMClassFromROMClass_Entry " >Create RAM class from ROM class %p in class loader %p" j9vm 4 1 1 N Trc_VM_CreateRAMClassFromROMClass_Exit " j9vm 4 1 1 N Trc_VM_CreateRAMClassFromROMClass_Exit "The first line contains the version number of the format file. A new version number reflects changes to the layout of this file.The format of each tracepoint entry is as follows:
<component> <t> <o> <l> <e> <symbol> <template>where:
- <component> is the internal JVM component name.
- <t> is the tracepoint type (0 through 11).
- <o> is the overhead (0 through 10).
- <l> is the level of the tracepoint (0 through 9, or - if the tracepoint is obsolete).
- <e> is the explicit setting flag (Y/N).
- <symbol> is the name of the tracepoint.
- <template> is a template that is used to format the entry. The template consists of the text that appears in double quotation marks (").
Tracepoint types are as follows:
- Type 0
- Event
- Type 1
- Exception
- Type 2
- Entry
- Type 4
- Exit
- Type 5
- Exit-with-Exception
- Type 6
- Mem
Any other type is reserved for development use; you should not find any other type on a release version of IBM Java™.
Note: This condition is subject to change without notice.
The version number is different for each version.
Parent: Using the Reliability, Availability, and Serviceability Interface
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.