IBM Support

IC35651: FILE AGGREGRATION IS NOT PERFORMING OPTIMALLY. SOME FILES ARE NOT AGGREGATED IN SERVER STORAGE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • File aggregation is not operating optimally in some situations.
    Files may be stored as individual objects, not as members of
    an aggregate.  This may have a performance impact.  There are
    no corruption or integrity concerns with this problem, this is
    a performance issue only.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: TSM Servers that have nodes storing smaller  *
    *                 files that would be contained in an          *
    *                 aggregate.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: File aggregation is not operating       *
    *                      optimally in some situations.  Files    *
    *                      may be stored as individual objects,    *
    *                      not as members of an aggregate.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    File aggregation is not operating optimally in some situations.
    Files may be stored as individual objects, not as members of
    an aggregate.  There are some situations that may cause files
    not to be aggregrated as expected. This may have an impact on
    performance when performing internal server movement operations
    such as migration, reclamation and expiration.
    

Problem conclusion

  • File aggregation is not operating optimally in some situations.
    Files may be stored as individual objects, not as members of
    an aggregate.  There are some situations that may cause files
    not to be aggregrated as expected. This may have an impact on
    performance when performing internal server movement operations
    such as migration, reclamation and expiration.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC35651

  • Reported component name

    TSM SERVER 510

  • Reported component ID

    5698ISMSV

  • Reported release

    51A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2003-02-10

  • Closed date

    2003-02-10

  • Last modified date

    2003-02-10

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

    IC35650

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

Fix information

  • Fixed component name

    TSM SERVER 510

  • Fixed component ID

    5698ISMSV

Applicable component levels

  • R51A PSY

       UP

  • R51H PSY

       UP

  • R51L PSY

       UP

  • R51P PSY

       UP

  • R51S PSY

       UP

  • R51W PSY

       UP

  • R51Z PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"51A","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
10 February 2003