Determining Process History

Table of Contents

Understanding Termination Messages
Using Log Information
Specifying the Information to Be Logged
Controlling Job Summary Printing
Saving the Job Summary File
Analyzing the System Log
Programmatically Interrogating Process History
Determining the Type of Termination
Determining Whether a Compilation Was Successful
Responding to Task Failures
Determining Where a Fault Occurred
Protecting a Process from Abnormal Terminations
Preventing All Abnormal Terminations
Protection against Most Conditions
Protection against All Conditions
Including Multiple Statements
Determining the Cause of the Error
Using TRY as an Expression
Providing Alternate Sets of Error Handling Code
Optimizing Performance
Triggering Program Dumps
Protecting a Process from Faults
Retrying a Failed Task
Protecting a Process from Operator DS (Discontinue) Commands
Protecting Procedures from DS and ST Commands
Performing Cleanup during an Abnormal Termination
Interactions between Error Recovery Statements
Multiple TRY Statements
TRY Statements and Library Delinkage
TRY Statements and ON Statements
TRY Statements, EPILOG Procedures, and EXCEPTION Procedures
Controlling Program Dumps
Using Program Statements to Control Program Dumps
Using Operator Commands to Control Program Dumps
Controlling the Program Dump Destination
Using the Task File
Analyzing a Program Dump from a Running Process
Determining Whether a Dump is In Progress
Causing Symbolic Dumps for RPG Processes
Effect of Resource Limits on Program Dumps
Understanding Internal and External Causes

Process history consists of information about how a process terminated, the accumulated resource usage of the process, and what actions the process took while it was active. Process history information can help you determine if a program is running as intended, and can help you to locate the source of any problems that arise.

This section describes the uses of various sources of process history information, including termination messages, job summaries, system log entries, history-related task attributes, and program dumps.