Copying history file entries

You copy by entering the line command C against the fault entry in the Fault Entry List display.

You can also copy a range of fault history entries, using two CC range markers. When you copy a range of a matched set of entries, you only copy the entries displayed on the screen. You do not copy any entries that are not displayed, but are interleaved with the displayed entries on the original history file.

After pressing the Enter key, a display showing the list of fault entries that are selected for copy with the C or CC commands is presented. Included are also any fault entries that are selected for move with the M or MM commands. The display provides a field for specification of a history file to which the fault entries should be copied. This field is initialized with the name of the history file last specified. The following is an example of the Specify Move/Copy Options display that is shown after pressing the Enter key.

A separate option, Include Tightly Coupled Dump Data Sets, has these possible settings:
Specifies that all associated dump data sets that uniquely belong to the selected fault entries will be duplicated.
Specifies that all associated dump data sets that uniquely belong to the selected fault entries will only be duplicated if a fault entry does not include a minidump. This might be the case, if for example a Recovery Fault Recording (RFR) fault entry has not yet been analyzed.
Specifies that no associated dump data sets will be copied.
Figure 1. Sample Specify Move/Copy Options display
│ Specify Move/Copy Options                                  Line 1 Col 1 76  │
│ Command ===> ___________________________________________  Scroll ===> CSR   │
│                                                                             │
│ Verify or change move/copy options for the selected fault entries and       │
│ press Enter, or press PF3/PF12 to abort the move/copy request.              │
│                                                                             │
│ Move/Copy Options:                                                          │
│   Destination History File: 'IDI.COPY.HIST'                                 │
│   Include Tightly Coupled                                                   │
│   Dump Data Sets. . . . . : N (All/Conditionally(*)/None)                   │
│ (*) Only include tightly coupled dump data sets for fault entries with no   │
│     minidump.                                                               │
│                                                                             │
│ Selected Fault Entries:                                                     │
│   BAT14648 BAT14649 BAT14650 BAT14651 BAT14652 BAT14653 BAT14654 BAT14655   │
│   BAT14656 BAT14657 BAT14658 BAT14659 BAT14660 BAT14661 BAT14662 BAT14663   │
│   BAT14664 BAT14665 BAT14666 BAT14667 BAT14668 BAT14669 BAT14670 BAT14671   │
│   BAT14672                                                                  │
│                                                                             │
│ *** Bottom of data.                                                         │
│  F1=Help     F3=Exit     F7=Up       F8=Down    F12=Cancel                  │

The destination history file that is specified is checked for UPDATE access authorization prior to commencing the move/copy processing. 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 original fault ID is preserved, if possible. However, if an identical fault ID already exists in the destination history file, then the fault number is incremented to the next available fault ID.

If the copy of one or more fault entries was not successful, then a display detailing the reasons is shown.

The TSO user's access authorization level required to copy a fault entry is READ.