Using Fault Analyzer
- Introduction
- Real-time analysis
- The Fault Analyzer ISPF interface
- Performing batch reanalysis
- Performing interactive reanalysis
- Performing CICS system abend dump analysis
- Formatting a CICS auxiliary trace data set
- Performing Java analysis
  - Selecting a Java dump data set
    Specification of a Java™ dump data set to be analyzed is done by first selecting File > Analyze MVS Dump Data Set from the Fault Entry List display.
  - Java fault entry reanalysis
  - Displaying the Java information in the interactive report
  - Java event replacement in Fault Analyzer event list
    When an abend includes Java™ events, Fault Analyzer requests a system dump of the JVM. This Java system dump is analyzed by Fault Analyzer using Diagnostic Tool Framework for Java (DTFJ) APIs.
  - Java information reporting limitations
  - Java application samples
    The JCL samples provided in the IDI.SIDISAM1 sample data set demonstrate how to use Java™ and interlanguage calls with Fault Analyzer.
- The Fault Analyzer report
- Using non-ISPF interfaces to access Fault Analyzer history files

Java information reporting limitations

In fault entries created by the Fault Analyzer wrapper utility, variable information is not shown.

This is due to the way the Java™ virtual machine processes exceptions:

The JVM searches each stack frame for a handler (that is, a try-catch block) for an exception.
If there is no handler in a given frame, the JVM discards the stack frame variables and searches the next frame. This search-and-discard repeats until the JVM finds a handler for the exception.

The Fault Analyzer wrapper utility acts as the handler for the otherwise unhandled exception. This means that none of the user-application variable values exist at the point when Fault Analyzer is invoked.

For details on how the JVM handles exceptions, see the section on the athrow instruction in the JVM Specification.