Applying an action to a particular fault
- A - display source
- Display the source-level debugging information captured during real-time analysis when the LangxCapture option is enabled. See LangxCapture.
- B - batch reanalysis
- Submit a batch job to reanalyze the selected fault entry. The analysis report is written to
SYSPRINT.
See Performing batch reanalysis for details.
- C - copy
- Copy the fault entry to a different history file.
See Copying history file entries for details.
- D - delete
- Delete the fault entry from the history file. After you delete
an entry, it is immediately removed from the Fault Entry List display,
and is not displayed by any subsequent refresh.
See Deleting history file entries for details.
- H - duplicate history
- When available, shows details about existing faults that were deemed duplicates of the selected
fault entry.
If duplicate details are available for a fault entry, then the Dups column value the entry becomes a point-and-shoot field. In this case, entering the H line command against a fault entry is equivalent to placing the cursor in the Dups column value for the entry, and pressing Enter.
See Viewing the fault entry duplicate history for details.
- I - interactive reanalysis
- Run interactive reanalysis against the selected fault. After a
little while, the interactive report is displayed. The interactive
report does not replace the real-time analysis report.
See Performing interactive reanalysis for details.
- J - edit JCL
- Display and edit the JCL captured during real-time analysis when the JclCapture option is enabled. This command performs the same function as the JCL command used in interactive reanalysis. See JCL and JclCapture.
- L - lock
- Lock fault entry using default lock flag setting.
To change the default lock flag setting, see Fault Analyzer preferences.
- M - move
- Move the fault entry to a different history file.
See Moving history file entries for details.
- P - package fault entry
- Generate JCL to package related fault entry data to a tersed data set suitable for transmission
to the Fault Analyzer product support team. The JCL is
displayed in an edit session which can then be amended and submitted.
See Packaging fault entries for details.
- U - unlock
- Unlock fault entry.
- V (or S) - view report
- View the saved fault analysis report:
See Viewing a saved report for details.
- X - XMIT
- XMIT the fault entry to a specified user ID and node.
See Transmitting history file entries for details.
- ? - view fault entry information
- View the fault entry information. In particular, this information shows the associated MVS™ dump data set name, if there is one.
See Viewing fault entry information for details.
If you enter a line command against an entry, and Fault Analyzer is unable to complete the command, then the line command is not cleared from the line. Here are some examples of this situation:
- You attempt to run a batch dump reanalysis against a fault that has no associated dump data set.
- The dump data set is unavailable.
You can type line commands against many entries before you press Enter. In this case, Fault Analyzer attempts to honor each command, starting with the entry at the top. When Fault Analyzer is unable to honor a command, here is what happens:
- It stops processing.
- It clears the line commands from each entry it was able to process.
- It leaves the line commands for each entry it failed to process or the entry at which it was unable to honor the command.