|
This summary provides an organization with a complete view of all failures per environment platform during a specific, user-defined time period. In this example, an organization can easily view batch, CICS Transaction, CICS Region, Windows and UNIX failures to determine where to dedicate its resources. |
Event type summary
|
| |
|
In this example, an organization can view its OS/390 subsystems, batch, CICS, CWI, DB2, IDMS, IMS and MQSeries failures. |
Failures on subsystems summary
|
| |
|
This report provides an organization with a complete view of all failures by machine ID per environment. This example illustrates the platforms on which the failures occurred, such as UNIX, CICS and batch. |
Failures on machines detail report
|
| |
|
This chart provides a view of all program failures during a user-specified time period. An organization easily can view what programs require immediate attention. |
Overall program failures summary
|
| |
|
This summary chart specifically identifies the errors that UNIX programs encounter over a user-specified time period. |
UNIX Program error codes summary
|
| |
|
This summary chart specifically identifies Windows programs that failed during a user-specified time period. |
Windows program failures summary
|
| |
|
This report provides an organization with weekly failures by program. Clicking on a specific program name provides users with more in-depth failure information for that specific program. |
Program failures
detail report
|
| |
|
This event detail report provides an organization with all the important program failure information that Fault Manager captured. In this particular report, you will see that Fault Manager identified an OS/390 batch program failure. |
Event detail
|
| |
|
Fault Manager provides organizations with the ability to view the Abend-AID diagnostics section from Fault Manager which helps alleviate questions or miscommunications regarding the source of the failure and who is responsible for correcting it. |
Abend-AID diagnostics
|
| |
|
This summary provides a high-level view of all program failures by the hour. From this summary, an organization can also review total failures by year, quarter, month, week or day. |
Hourly program failures summary
|
| |
|
This summary provides an organization with important OS/390 program failure information by identifying program failures within each job/region. This summary helps to identify recurring trends. |
OS/390 program summary by job
|
| |
|
This summary provides an organization with specific DB2 program failure information by identifying errors that occurred in each program. This summary helps identify recurring program trends. |
DB2 SQL code summary by program
|
