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 Sample Confirm Java Fault Entry Reanalysis display.
┌─────────────────────────────────────────────────────────────────────────────┐ │ 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 IDI0177E is issued instead of the Confirm Java™ Fault Entry Reanalysis display.
- The MVS™ post-dump exit IDIXTSEL has not been installed (for details, see Installing the MVS post-dump exit IDIXTSEL).
- The IDIS subsystem has not been started (for details, see Using the Fault Analyzer IDIS subsystem).