fcreport Command

Purpose

Locates and displays the report of a failure and any failures associated with the failure.

Syntax

/usr/sbin/rsct/bin/fcreport { [ -a ] FFDC_Failure_ID } │ -h

Description

fcreport decodes an FFDC Failure Identifier, and obtains reports on the failure identified by it. The command also detects if any failure was associated with the FFDC Failure Identifier, and if so, obtains the report on that failure. The command continues to examine the report of each failure it locates for associated failures and to obtain reports on the associated failures until one of the following conditions is met:

No further associated failures are detected.
The report for an associated failure cannot be found. This may occur when the associated failure report resides on a remote node that cannot be reached at the moment, or the record of the failure has been removed from the node where it resided.

Using this command, the user can obtain a report for the entire list of failures that caused a specific failure. fcreport is not capable of locating reports for any failures that may have been caused by the initial failure provided to the command; it can only obtain reports of failures that caused this failure.

Flags

-a: Displays all information contained in a report for a failure. The default is to display the network address of the node where the failure report was generated, the time stamp on the failure report, and the description of the incident recorded in the failure report.
-h: Displays a help message to standard output and exits. No other processing is performed, regardless of the options specified.

Parameters

FFDC_Failure_ID: Specifies the FFDC Failure Identifier of the failure to begin the report. fcreport will attempt to obtain the failure information for this failure, as well as any failures that this report lists as an associated failure. Only one FFDC Failure Identifier may be provided to this command.

Security

fcreport uses rsh to obtain failure reports that may reside on remote nodes. The user must have sufficient privilege to execute rsh commands to these remote nodes. If the user does not have this permission, fcreport can only trace the list of related failures so long as they exist on the local node.

Exit Status

fcreport generates one of the following exit status codes upon completion:

0: Failure report located and displayed for the FFDC Failure Identifier provided. Zero or more related failure reports may have been located and displayed as well.
2: Help information displayed and processing ended.
10: Required options or arguments are not provided.
11: The FFDC Failure Identifier provided to this command was generated by a later release of the FFDC software. The command is not capable of correctly interpreting this identifier.
12: Unknown option specified to this command.
20: The FFDC Failure Identifier refers to an entry made in an FFDC Error Stack on this system, but the FFDC Error Stack file cannot be accessed. The file may have been removed, or permissions may have been altered on the file to prevent access to it.
27: The FFDC Failure Identifier provided to this command is not a valid identifier.

Examples

Consider the case where several processes were created in the following parent-child order:

                            PID  562
                                .
                                .
                            PID = 785
                             .      .
                           .          .
                         .              .
                   PID = 2024        PID = 1042
                   .     .
                 .         .
               .             .
          PID = 981     PID = 5012

In this example, process 785 generated the FFDC Failure Identifier .3Iv04ZVVfvp.wtY0xRXQ7.................... and passed it back to Process 562. To obtain a detailed report for FFDC Failure Identifier .3Iv04ZVVfvp.wtY0xRXQ7.................... and any previous failures that led to this specific failure:

$ fcreport -a .3Iv04ZVVfvp.wtY0xRXQ7....................

This report will contain the details of the specified FFDC Failure Identifier, as well as any failures in processes 2024, 1042, 981, and 5012 that may have caused it. The report will not contain any failures in process 562 that may have been caused as a result of process 785's failure.

Implementation Specifics

This command is part of the Reliable Scalable Cluster Technology (RSCT) fileset.