IBM Support

OA60641: GROUP CAPACITY LIMIT IS NOT PROPERLY ENFORCED WHEN THE SYSTEM HAS ABSMSUCAPPING ACTIVE AND THERE IS NO DEFINED CAPACITY LIMIT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Group Capacity limit not properly enforced at z/OS 2.3 when
    Group Capping and Absolute MSU Capping are both active and there
    is no defined capacity limit.
    When ABSMSUCAPPING is active each group member should always
    enforce capping at its share of the group capacity. The error is
    in the case that the group 4 hour consumption is still below the
    group limit each member may be capped at the Group Limit instead
    of the share of the Group Limit.
    

Local fix

  • BYPASS/CIRCUMVENTION:
    None
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of z/OS 2.3 (HBB77B0) and above.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Group Capacity limit not properly                            *
    * enforced when Group Capping and                              *
    * Absolute MSU Capping are both active                         *
    * and there is no defined capacity                             *
    * limit.  When ABSMSUCAPPING is active                         *
    * each group member should always                              *
    * enforce capping at its share of the                          *
    * group capacity. The error is in the                          *
    * case that the group 4 hour                                   *
    * consumption is still below the group                         *
    * limit each member may be capped at                           *
    * the Group Limit instead of the share                         *
    * of the Group Limit.                                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a group capacity limit is active together with the OPT
    paramter AbsMsuCapping, the LPAR should be capped to its share
    of the group limit all the time.
    But the module IRAPALCA sets the capping limit of the LPAR to
    the group limit in this case errornously.
    

Problem conclusion

  • IRAPALCA has been changed to set the limit of the LPAR to the
    group limit share instead of the group limit itself in the
    described scenario.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA60641

  • Reported component name

    WORK LOAD MANAG

  • Reported component ID

    5752SCWLM

  • Reported release

    7B0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-12-16

  • Closed date

    2021-02-03

  • Last modified date

    2021-05-28

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

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

    UJ04835 UJ04836

Modules/Macros

  • IRAPALCA
    

Fix information

  • Fixed component name

    WORK LOAD MANAG

  • Fixed component ID

    5752SCWLM

Applicable component levels

  • R7B0 PSY UJ04835

       UP21/02/17 P F102

  • R7C0 PSY UJ04836

       UP21/02/17 P F102

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"7B0"}]

Document Information

Modified date:
29 May 2021