PM04292: ADD DIRECTORY STORAGE FOR EARLY FFDC INCIDENTS AS AN OPTION FOR THE GENERIC FFDC

Fixes are available

APAR status

Closed as new function.

Error description

Add capability so that, by setting an environment variable,
storage of FFDC incidents created outside of WebSphere
Application Server (or in early WebSphere Application Server
startup) can be handled in a manner similar to the handling of
WebSphere Application Server runtime ffdc incidents.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: Default FFDC did not provide an         *
*                      ability to store incidents in a         *
*                      directory.                              *
****************************************************************
* RECOMMENDATION:  This fix enables setting of an environment  *
*                  variable com.ibm.ffdc.log to route FFDC     *
*                  incidents that occur in client processes    *
*                  and early FFDC server startup to a          *
*                  directory.                                  *
****************************************************************
In the past, the default FFDC provider (runs in client
processes, non-WebSphere Application Server processes, and
early in WebSphere Application Server startup) did not provide
the ability to route FFDC incidents to a directory as the
WebSphere Application Server FFDC does.  This enables that
functionality.

Problem conclusion

By setting the environment variable
com.ibm.ffdc.log=<someDirectory> (ending in / or \\),
incidents will be stored in that directory just as the
WebSphere Application Server FFDC stores them in
<profileHome>/logs/ffdc/ .  This was needed by some
non-WebSphere Application Server products and makes it better
for WebSphere Application Server as well.  Currently, early
server startup FFDC incidents are not rendered, and by setting
com.ibm.ffdc.log=xxx/ ... the incidents will be saved there
along with a summary file.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.11.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

```
None needed.
```

Comments

APAR Information

APAR number
PM04292
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-12-30
Closed date
2010-01-20
Last modified date
2010-01-20

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM04292: ADD DIRECTORY STORAGE FOR EARLY FFDC INCIDENTS AS AN OPTION FOR THE GENERIC FFDC

Fixes are available

Subscribe

APAR status

Closed as new function.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?