IBM Support

PK22724: THE COLLECTOR OUTPUT JAR CONTAINS CASE SENSITIVE AND LOWERCASE PATHS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Collector output jars created on Windows or OS/400 contained
    lowercase and case-specific paths.  These inconsistent paths
    can cause problems when un-jarred on operating systems that
    are more particular about case sensitivity in paths, like
    Linux.  For example, if a linux user attempted to view the
    contents of an output jar from a Windows box, she would only
    be able to view a subset of the collected files.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: WebSphere Application Server version 5 and   *
    *                 6 users running the collector tool on the    *
    *                 Microsoft Windows platform - particularly    *
    *                 when the output jar will be viewed on a      *
    *                 non-Microsoft Windows platform.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Collector output jar contains case      *
    *                      sensitive and lowercase paths.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The output JAR file from the collector tool that was run on a
    Microsoft Windows operating system would contain case
    sensitive paths as well as lower-case paths which might
    contain the same directory (that is, it might contain the
    paths, "C:\WebSphere\AppServer" and "c:\websphere\appserver
    \logs").  This can be read when extracted onto another
    Microsoft Windows box, but runs into problems when extracted
    on a non-Microsoft Windows Operating System (specifically one
    that contains case sensititve paths).
    

Problem conclusion

  • This fix treats all platforms as case sensitive.  Therefore,
    the paths in the output jar will exactly match the paths on
    the system where the collector was run.
    
    The fix for this APAR is currently targeted for inclusion
    in cumulative fixes 5.02.17 and 5.1.1.11 and fixpack 6.0.2.11.
    Please refer to the recommended updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK22724

  • Reported component name

    WEBSPH APP SERV

  • Reported component ID

    5724J0800

  • Reported release

    60W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-04-03

  • Closed date

    2006-04-27

  • Last modified date

    2006-06-06

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

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

Modules/Macros

  • RAS
    

Fix information

  • Fixed component name

    WEBSPH APP SERV

  • Fixed component ID

    5724J0800

Applicable component levels

  • R60A PSN

       UP

  • R60H PSN

       UP

  • R60I PSN

       UP

  • R60P PSN

       UP

  • R60S PSN

       UP

  • R60W PSY

       UP

  • R60Z PSN

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
21 December 2021