Configuring first failure data capture log file purges

The first failure data capture (FFDC) log file saves information that is generated from a processing failure. These files are deleted after a maximum number of days has passed. The captured data is saved in a log file for analyzing the problem.

Before you begin

[AIX Solaris HP-UX Linux Windows][IBM i]The first failure data capture (FFDC) feature preserves the information that is generated from a processing failure and returns control to the affected engines. The captured data is saved in a log file for analyzing the problem. FFDC is intended primarily for use by IBM® Support. FFDC instantly collects events and errors that occur during the product run time. The information is captured as it occurs and is written to a log file that can be analyzed by IBM Support personnel.

[z/OS]FFDC is intended primarily for use by IBM Support. FFDC instantly collects events and errors that occur during the product run time. The information is captured as it occurs and is written to a log file that can be analyzed by IBM Support. The data is uniquely identified for the servant region that produced the exception.

[z/OS]The log file purges in seven days by default. If you are concerned about the amount of disk space used by the FFDC log files, you can configure the days between purges.

The FFDC configuration properties files are located in the properties directory under the Application Server product installation. You must set the ExceptionFileMaximumAge property to the same value in all three files: ffdcRun.properties, ffdcStart.properties, and ffdcStop.properties. You can set the ExceptionFileMaximumAge property to configure the days between purging the FFDC log files. The value of the ExceptionFileMaximumAge property must be a positive number. The FFDC feature does not affect the performance of the Application Server product.

About this task

Perform the following steps to configure the number of days between the FFDC log file purges. The value is in days.

Procedure

  1. Open the ffdcRun.properties file.

    [AIX Solaris HP-UX Linux Windows][z/OS]The file is located in the app_server_root/properties directory.

    [IBM i]The file is located in the profile_root/properties directory.

  2. Change the value for the ExceptionFileMaximumAge property to the number of days between the FFDC log file purges. The value of the ExceptionFileMaximumAge property must be a positive number. The default is seven days. For example, ExceptionFileMaximumAge = 3 sets the default time to three days. The FFDC log file is purged after three days.
  3. Save the ffdcRun.properties file and exit.
  4. Repeat the previous steps to modify the ffdcStart.properties and ffdcStop.properties files.

Results

[AIX Solaris HP-UX Linux Windows][IBM i]The FFDC file management function removes the FFDC log files that have reached the maximum age and generates a message in the SystemOut.log file.

Note: This topic references one or more of the application server log files. As a recommended alternative, you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

[z/OS]The FFDC file management function removes the FFDC log files that have reached the maximum age and generates a message in the SYSOUT of the server job log.


Icon that indicates the type of topic Task topic



Timestamp icon Last updated: March 5, 2017 17:29
File name: ttrb_ffdcconfig.html