IBM Support

PM66023: CQM1217W REQUEST WOULD HAVE EXCEEDED MAXIMUM ALLOCATIONS VALUE DB2 QUERY MONITOR MSQLW SUBTASK ABENDABEND0C4

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Build-up of exceptions resulting from exceptions caching.
    
    Additional symptoms may include the following:
    
    CQM1217W REQUEST WOULD HAVE EXCEEDED MAXIMUM ALLOCATIONS VALUE
    
    DB2 QUERY MONITOR MSQLW SUBTASK ABEND
    ABENDS0C4 ABEND0C4 S0C4
    

Local fix

  • Add the following parameter to CQMPARMS (recycle the collector
    to pickup the new parameter):
    DISABLE_EXCP_CACHE(Y)
    The DISABLE_EXCP_CACHE parameter provides the ability to turn
    off the internal exception control block caching (the default is
    'N').  Specifying 'Y' will prevent the build-up of exceptions
    caching that is causing the problem.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Query Monitor.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Build-up of exceptions resulting from   *
    *                      exceptions caching. Additional symptoms *
    *                      may include the following:              *
    *                      CQM1217W REQUEST WOULD HAVE EXCEEDED    *
    *                       MAXIMUM ALLOCATIONS VALUE              *
    *                      DB2 QUERY MONITOR MSQLW SUBTASK ABEND   *
    *                      ABENDS0C4 ABEND0C4 S0C4                 *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM66023

  • Reported component name

    DB2 QUERY MONIT

  • Reported component ID

    5655E6701

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-06-01

  • Closed date

    2012-08-09

  • Last modified date

    2012-09-05

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

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

    UK80961

Modules/Macros

  •    CQM#INIX
    

Fix information

  • Fixed component name

    DB2 QUERY MONIT

  • Fixed component ID

    5655E6701

Applicable component levels

  • R310 PSY UK80961

       UP12/08/21 P F208

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0"}]

Document Information

Modified date:
17 March 2021