Creating a history file entry

When you exit from the CICS® System Abend Interactive Reanalysis Report, you are presented with the option to create a history file entry as shown in Figure 1.
Figure 1. Sample Create History File Entry display
  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
To create a history file entry:
  1. If necessary, change the supplied name of the history file (obey the ISPF data set name specification rules).
  2. Optionally change the Suppress Minidump option to 'Y' to show that a minidump with the indicated number of pages must not be created.
  3. Press Enter.
The "History file DSN" field is by default initialized with the current history file name that is selected on the Fault Entry List display. If a view is being used, then the first history file name that is specified in the view member is used. To avoid creating a history file entry, press either F3 or F12.

If a history file entry was created, message HFZ0003I 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.