IBM Support

PI73035: FFDC logs are created in a directory relative to the current directory

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • client_ffdc is created in current directory when stopServer.sh
    is run. The FFDC logs are created in a directory relative to
    the current directory rather than a known location.
    

Local fix

  • In stopServer script under WAS_HOME/bin change a single line:
    from:
     -Dcom.ibm.ffdc.log=./client_ffdc/ \
    
    to:
     -Dcom.ibm.ffdc.log="$FFDCLOG" \
    
    WAS_HOME is home directory where WAS is installed.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  invoking stopManager, serverStatus,         *
    *                  stopNode                                    *
    *                  and stopServer scripts.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: The FFDC logs are created in a          *
    *                      directory                               *
    *                      relative to the current directory       *
    *                      rather                                  *
    *                      than a known location.                  *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack containing this APAR.    *
    ****************************************************************
    The FFDC logs from 4 scripts (stopManager, serverStatus,
    stopNode and stopServer) are created in a directory relative
    to the current directory when the script is invoked.  This
    makes finding the FFDC difficult.
    

Problem conclusion

Temporary fix

  • The APAR changes 4 scripts. The same change change can be
    performed manually by editing a single line in each of the
    scripts as follows:
    
    1) Back up WAS_HOME/bin
    
    2) Edit these files:
             stopServer.sh, stopNode.sh, stopManager.sh,
    serverStatus.sh
    
       and in each one, change a single line, from:
             -Dcom.ibm.ffdc.log=./client_ffdc/ \
    
       to:
             -Dcom.ibm.ffdc.log="$FFDCLOG" \
    

Comments

APAR Information

  • APAR number

    PI73035

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-30

  • Closed date

    2017-03-29

  • Last modified date

    2017-03-29

  • 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

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021