IBM Support

PM65096: CSQX027E UNABLE TO GET STORAGE, RC=0 AND THE DUMPS SHOW VERY LARGE STORAGE AREA OF 100M

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The customer is intermittently receiving a csqx027e unable
    to get storage, rc=0. In investigating of the storage, there
    were several 100M buffers being created. This APAR was created
    to investigate the allocation of 100 MB in the CHINIT.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of Websphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: If a client application issues MQGET    *
    *                      request with get option                 *
    *                      MQGMO_ACCEPT_TRUNCATED_MSG specified    *
    *                      and does not specify a MaxMsgLength (so *
    *                      that MaxMsgLength defaults to -1), the  *
    *                      chinit may consequently allocate a      *
    *                      100MB buffer to handle the message.     *
    *                                                              *
    *                      CSQX027E messages may result if the     *
    *                      storage needs to increase.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An MQ Java application issues an MQGET request with
    MQGMO_CONVERT, MQGMO_ACCEPT_TRUNCATED_MSG and a wait interval.
    
    Even if the application provides a maximum message size, the MQ
    Java code requests the whole message to be sure it can be
    converted.  The client channel is using streaming, so a
    rfpTST_REQUEST_MSGS is sent to the server with -1 for
    MaxMsgLength.
    
    The request is handled by the channel's async consume thread,
    but there are no messages on the queue, so it waits.
    
    When the client's wait interval expires, the MQ Java code sends
    another rfpTST_REQUEST_MSGS with rfpRMF_CHECK_MSG set to force a
    synchronous response.
    
    rstCheckForOneMessage handles the synchronous request.  Because
    MQGMO_ACCEPT_TRUNCATED_MSG is set, and MaxMsgLength is -1, the
    code allocates a 100MB buffer so that it can handle any size of
    message.
    

Problem conclusion

  • The code has been changed to set a maximum message buffer size
    if it has been provided with one, otherwise to turn off
    MQGMO_ACCEPT_TRUNCATED_MSG  and allocate an appropriate buffer
    size for the whole message.
    100Y
    CMQXRSTF
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM65096

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-05-21

  • Closed date

    2012-09-11

  • Last modified date

    2015-03-20

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

    PM60991

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

    UK81704

Modules/Macros

  • CMQXRSTF
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UK81704

       UP12/10/10 P F210 Ž

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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
20 March 2015