IBM Support

OA50356: NEW FUNCTION: AUTOMATIC DELETION OF CIM REPOSITORY BACKUPS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Whenever an upgrade to the CIM repository is made via PTF or
    upgrade, a backup of the current repository is made to the
    /var/wbem/ directory.  These are not cleaned up and over time
    there can be numerous copies of old repositories, with a small
    chance of these being needed.  This can cause excessive growth
    of the CIM file system for unnecessary data.  Users have to
    manually remove directories to free up space.  Having aggrgrow
    on for all data sets is not a long term option as the file could
     grow excessively, again due to backups that are not needed. We
    should implement an automatic deletion of repository backups
    either based on version (like a z/OS GDG) or date . This will
    clean up old directories.
    

Local fix

  • Customers have to manually remove directories to free up space
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All z/OS CIM customers                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: The CIM repository backups cause        *
    *                      excessive growth of the CIM file        *
    *                      system for unnecessary data. Users      *
    *                      have to manually remove directories     *
    *                      to free up space.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Introduce a new CIM server configuration maxRepositoryBackups
    to configure how many repository backups the customer want to
    have. When there is a success repository upgrade, CIM will scan
    the repository directory for the repository backups, just keep
    the number of maxRepositoryBackups latest repository backups.
    The others will be deleted.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    OA50356

  • Reported component name

    ESERVER OS MGMT

  • Reported component ID

    5752SCCIM

  • Reported release

    7A0

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2016-04-24

  • Closed date

    2016-08-22

  • Last modified date

    2016-10-04

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

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

    UA82531

Modules/Macros

  • CFZRPAX  CFZRSHR
    

Fix information

  • Fixed component name

    ESERVER OS MGMT

  • Fixed component ID

    5752SCCIM

Applicable component levels

  • R7A0 PSY UA82531

       UP16/09/07 P F609

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7A0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7A0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 October 2016