Creating a history file entry
File View Services Help ┌──────────────────────── Create History File Entry ─────────────────────────┐ │ │ │ To create a history file entry for the analyzed MVS dump data set, specify │ │ a history file data set name and press Enter. │ │ │ │ History file DSN . . 'NWILKES.DEMO.HIST' │ │ │ │ Minidump pages . . : 29 │ │ Suppress minidump . . N (Y/N) │ │ │ │ F1=Help F3=Exit F12=Cancel │ └────────────────────────────────────────────────────────────────────────────┘ DFHSM0002 CICSDI A severe error (code X'030E') has occurred in module DFHSMGF. Severity 3 Observations *** Bottom of data. F1=Help F3=Exit F5=RptFind F6=Actions F7=Up F8=Down F10=Left F11=Right
- If necessary, change the supplied name of the history file (obey the ISPF data set name specification rules).
- Optionally change the
Suppress Minidump
option to 'Y' to show that a minidump with the indicated number of pages must not be created. - Press Enter.
Instead of the default, the user can specify a different history file name. Standard TSO naming convention for data sets is assumed, that is, if the data set name is not enclosed in single quotes, the current TSO prefix is used as the high-level qualifier.
If the specified history file does not exist, then the New History File Allocation display is shown (for details, see New history file allocation).
The user must have at least UPDATE access to the specified history file.
If a history file entry was created, message IDI0003I is issued to
inform you of the assigned fault ID. The history file in which the fault entry was created is
automatically selected as the current history file. A MATCH FAULT_ID
fault_id
command is issued so that only the newly created fault
entry is displayed. This command is issued because the newly created fault entry might not be at the
top of the chronologically ordered Fault Entry List display, and thus difficult to locate. To again
see all fault entries in the history file, enter the MATCH ALL
command (normally
mapped to PF12).
The performance of subsequent reanalysis of the fault is improved by creating a fault history entry for a CICS® system abend, and writing a minidump.