IBM Support

PI13042: CSQX053E CSQSNAP XFFSXCSFREEOWNEDBUFFERS OWNERS DIDN'T FREE THEIR BUFFERS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CSQX053E xxxx CSQXFFST Error information recorded in CSQSNAP
    data set.
     The problem seen here occurs when a multiplexed channel is
    using a security exit and rriAcceptSecurityReceive needs to
    allocate a larger send buffer following the response from
    the security exit. The larger buffer is not associated with
    the primary conversation (ccxAllocMem is invoked with
    pSess -> hConv which is pointing to the conversation being
    started) and therefore the buffer does not get freed when
    the conversation ends. This leads to the subsequent FFSTs seen
    here.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 0 Modification 1 and Release 1       *
    *                 Modification 0.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Various CSQX053E CSQXFFST SNAP dumps    *
    *                      taken when using channel security exits *
    *                      on SVRCONN channels with SHARECNV > 1   *
    *                      if CSQXDBG DD card is defined.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using security exits on SVRCONN channels defined with
    SHARECNV > 1, if the channel sends more data than can fit into
    the current transmission buffer then we reallocate a larger
    buffer. This realloction process does not correctly update the
    various cached pointers to this buffer and upon channel
    termination a CSQX053E message is displayed and an FFST SNAP
    dump is taken showing either:
    
      "xcsCheckPool Buffer Pool Memory error"
    or
      "xcsFreeOwnedBuffers"
    

Problem conclusion

  • Buffer allocation when sending large amounts of data
    during security exit negotiation has been amended
    to ensure it does not incorrectly update cached buffer
    references.
    010Y
    100Y
    CSQXREXT
    

Temporary fix

Comments

  • ×**** PE14/11/03 FIX IN ERROR. SEE APAR PI28088  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI13042

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    010

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-03-04

  • Closed date

    2014-06-02

  • Last modified date

    2014-11-20

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

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

    UI18505 UI18506 PI30045

Modules/Macros

  • CSQXREXT
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R010 PSY UI18505

       UP14/06/27 P F406

  • R100 PSY UI18506

       UP14/06/27 P F406

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.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
20 November 2014