IBM Support

PI34733: VIEWING MANY EXCEPTIONS OR SQLCODES IN ISPF DATASHARING CAN CAUSE MEMORY ISSUES IN CAE SERVER, INCLUDING ISSUING CQMC2502E

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using the datasharing view in ISPF to view large numbers of
    exceptions or SQLCODES (e.g. 10,000 or more, depending on the
    REGION size and CQM_HEAP of the CAE Server), the CAE server may
    use large amounts of memory, and sometimes also run out of
    memory.
    
    When attempting to retrieve large numbers of exceptions,
    sometimes the user will receive a message like the following:
    
    CQMC2502E: 100,025 records required 508,927,200 bytes, which
    exceeded available memory 243,540,416 bytes on the server
    
    Sometimes the request will never complete, and the CAE Server
    log willshow Out Of Memory Errors.
    
    This APAR changes the memory management model for this request
    in the CAE Server. The limitation on the number of records
    retrieved will be then more dependent on the REGION size of the
    user's TSO Address Space.
    
    It is recommended that the user try to limit the number of
    exceptions by controlling how many are collected, or by
    filtering the exception records using the "filter" command. This
    will improve performance.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Query Monitor.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using the datasharing view in      *
    *                      ISPF to view large numbers of           *
    *                      exceptions or SQLCODES (e.g. 10,000 or  *
    *                      more, depending on the REGION size and  *
    *                      CQM_HEAP of the CAE Server), the CAE    *
    *                      server may use large amounts of memory, *
    *                      and sometimes also run out of memory.   *
    *                      When attempting to retrieve large       *
    *                      numbers of exceptions, sometimes the    *
    *                      user will receive a message like the    *
    *                      following:                              *
    *                      CQMC2502E: 100,025 records required     *
    *                       508,927,200 bytes, which exceeded      *
    *                       available memory 243,540,416 bytes     *
    *                       on the server                          *
    *                      Sometimes the request will never        *
    *                      complete, and the CAE Server log will   *
    *                      show Out Of Memory Errors. This APAR    *
    *                      changes the memory management model     *
    *                      for this request in the CAE Server.     *
    *                      The limitation on the number of         *
    *                      records retrieved will be then more     *
    *                      dependent on the REGION size of the     *
    *                      user's TSO Address Space. It is         *
    *                      recommended that the user try to limit  *
    *                      the number of exceptions by             *
    *                      controlling how many are collected, or  *
    *                      by filtering the exception records      *
    *                      using the "filter" command. This        *
    *                      will improve performance.               *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI34733

  • Reported component name

    DB2 QUERY MONIT

  • Reported component ID

    5655E6701

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-02-10

  • Closed date

    2015-07-07

  • Last modified date

    2015-08-03

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

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

Modules/Macros

  • CQM$ACTV
    

Fix information

  • Fixed component name

    DB2 QUERY MONIT

  • Fixed component ID

    5655E6701

Applicable component levels

  • R320 PSY UI29178

       UP15/07/14 P F507

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.2.0"}]

Document Information

Modified date:
17 March 2021