IDI0138S received occasionally indicating there is no minidump or MVS dump available for reanalysis

Technote (troubleshooting)


Problem(Abstract)

There are times when we get an entry in our Fault Analyzer history file, but when we try to "V"iew the report or perform "Interactive reanalysis" of the fault entry, we receive error IDI0138S. The full message is:

IDI0138S No minidump or MVS dump data set is available for reanalysis
of history file TEST.IDI.HIST fault ID F68035

Why do we receive these unusable fault entries to our history file?

Resolving the problem

When a user tries to analyze a particular fault entry and receives the error, "IDI0138S No minidump or MVS dump data set is available for reanalysis of history file hist-file fault ID faulta," this indicates that there was a problem during FA's analysis of the abend. This should be a rare occurrence and can occur due to various problems encountered during FA's real-time analysis of the original application abend.

When the fault entry contains no minidump or report, this fault entry is known as an RFR (Recovery Fault Recording) fault entry, and reanalysis of this fault entry as it was written will not be possible. If you have set up the writing of RFR dumps as covered in Chapter 13 of the Fault Analyzer User's Guide and Reference, then an RFR dump will be written. Having an RFR dump in place allows analysis of the abend after the fact.

While the RFR fault entry does not contain a report or minidump, it does contain the name of the RFR dump that was written, so when you go to View or do Interactive Reanalysis of this fault entry, FA does a reanalysis of this RFR system dump and allows the viewing of the abend information and the saving of the report and of the minidump. To allow the analysis of abends where no report or minidump was written, it is highly recommended that you set up Recovery Fault Recording in Fault Analyzer to allow RFR dumps to be written and saved.

In this particular instance of the IDI0138S messages, it was a problem successfully generating FA fault entries to your history file that correctly referenced the generated SDUMP. This was due to the IEAVTSEL user exit provided by Fault Analyzer IDIXTSEL not being installed. A sample job IDI.SIDISAM1(IDIWTSEL) is provided to install this user exit. This MVS post dump exit requires FA's IDIS subsystem to be running and performs the action of updating the RFR fault entry with the SVC dump name, once the DUMPSRV address space finished writing this dump. Once this user exit is in place, you will need to do an IPL to have this user exit implemented in the DUMPSRV address space. If an IPL is not possible, you should be able to cancel the DUMPSRV address space. When it is cancelled, DUMPSRV will automatically restart, with the user exit in place.


Related information

Fault Analyzer Library

Historical Number

41047-122-000

Rate this page:

(0 users)Average rating

Document information


More support for:

Fault Analyzer for z/OS
HISTORY FILE

Software version:

10.1, 11.1, 12.1

Operating system(s):

z/OS

Reference #:

1617747

Modified date:

2013-04-11

Translate my page

Machine Translation

Content navigation