Java fault entry reanalysis
Only fault entries that were created from analysis of Java™ dumps, or from real-time analysis of Java abends, include Java information in the reanalysis report.
Use the "I" line command against a history file fault entry to perform interactive reanalysis.
If the asynchronous DTFJ processing for the fault entry has not yet completed, then the Confirm Java Fault Entry Reanalysis display is presented, as the example shown in Figure 1.
┌ ─────────────────────────────────────────────────────────────────────────────┐
│ Confirm Java Fault Entry Reanalysis Line 1 Col 1 76 │
│ Command ===> Scroll ===> CSR │
│ │
│ Java DTFJ processing has not yet completed for this fault entry. │
│ │
│ Press Enter to continue reanalysis with incomplete Java information, or │
│ press PF3/PF12 to cancel. │
│ │
│ *** Bottom of data. │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
By pressing the Enter key, reanalysis continues, but the Java information is incomplete.
If instead PF3 or PF12 is pressed, then the reanalysis is canceled. Subsequent reanalysis at a later point in time might find that the asynchronous Java DTFJ processing has completed, and therefore continue the analysis without displaying this prompt.
If the asynchronous DTFJ processing for the fault entry failed to complete within a reasonable time, then message HFZ0177E is issued instead of the Confirm Java Fault Entry Reanalysis display.
- The MVS™ post-dump exit HFZXTSEL has not been installed (for details, see Installing the MVS post-dump exit HFZXTSEL).
- The HFZS subsystem has not been started (for details, see Using the Z Abend Investigator HFZS subsystem).
- The HFZ.SHFZAUTH data set has not been added to LINKLIST or provided via STEPLIB in the HFZS subsystem JCL (for details, see HFZS subsystem requirements for Java).