Viewing the fault entry duplicate history
The Fault Entry Duplicate History display provides information about additional occurrences of the fault, within the NoDup option time limit in effect for the fault type and subject to the defined duplicate criteria.
The display can be invoked by:
- Entering the H line command against a fault entry from the Fault Entry List display.
- Placing the cursor on the Fault Entry List display Dups column value for a fault entry, when this entry is presented as a point-and-shoot field, and pressing Enter.
- Issuing the DUPS primary command from within the interactive reanalysis report.
- Placing the cursor on the Fault Entry Information display Duplicate Count value, when this value is presented as a point-and-shoot field, and pressing Enter.
An example of a Fault Entry Duplicate History display follows:
The following information is provided:
- Most recent duplicate occurred
- The local date and time when the most recent duplicate of this fault occurred. The formatting of the date and time is subject to the Locale option in effect.
- Initial abend occurred
- The local date and time when the initial fault that caused the entry to be written occurred. The formatting of the date and time is subject to the Locale option in effect.
- Total duplicate count
- The total number of duplicates that have been registered against this fault.
- Duplicate details in reverse chronological order
- Details of the duplicate occurrences. Depending on whether the duplicates resulted from NoDup(Normal) or NoDup(CICSFast) processing, the information that is provided differs:
- NoDup(Normal) duplicates For NoDup(Normal) duplicates, the information that is provided for each instance is comprised of:
- Date
- The date when the duplicate occurred. The formatting of the date is subject to the Locale option in effect.
- Time
- The time when the duplicate occurred. The formatting of the time is subject to the Locale option in effect.
- Jobname
- The name of the job that caused the duplicate fault.
- Job ID
- The JES job ID of the job that caused the duplicate fault.
- System
- The name of the system on which the job that caused the duplicate fault was executing.
- Dup Type
- The type of duplicate (always "Normal" for NoDup(Normal) duplicates).
- User ID
- The user ID that is associated with the job that caused the duplicate fault.
- Stepname
- The name of the job step that caused the duplicate fault.
Multiple consecutive NoDup(Normal) occurrences are grouped under a common heading.
- NoDup(CICSFast) duplicates
For NoDup(CICSFast) duplicates, the information that is provided consists of:
- A common section, with details that are applicable to all duplicate
faults (one or more) that occurred within the recording interval:
- Date
- The date when the first duplicate occurred within the recording interval. The formatting of the date is subject to the Locale option in effect.
- Time
- The time when the first duplicate occurred within the recording interval. The formatting of the time is subject to the Locale option in effect.
- Jobname
- The name of the job that caused the duplicate faults.
- Job ID
- The JES job ID of the CICS® region that caused the duplicate faults.
- System
- The name of the system on which the CICS® region that caused the duplicate faults was executing.
- Dup Type
- The type of duplicates (always "Fast" for NoDup(CICSFast) duplicates).
- Detailed information of up to 10 unique faults that occurred within
the recording interval:
- User ID
- The CICS® user ID that caused the duplicate faults.
- Terminal ID
- The CICS® terminal ID that caused the duplicate faults.
- Count
- The total number of occurrences of this unique combination of CICS® user ID and terminal ID that occurred within the recording interval.
Note: If the sum total of all "Count" values does not equal the total number of duplicates that occurred within the recording interval, then a note is provided with information about the number of duplicates for which details are not available.This situation can happen if duplicate faults for more than 10 unique combinations of CICS® user IDs and terminal IDs occurred during the recording interval.
- A common section, with details that are applicable to all duplicate
faults (one or more) that occurred within the recording interval:
Note: If the sum total of all duplicate faults shown does not equal the total duplicate count for the fault entry, then a note is provided with information about the number of duplicates for which details are not available.This situation can happen if more duplicate faults have occurred than can be recorded with details in the fault entry.
- NoDup(Normal) duplicates