IBM Support

PH67593: WHEN A LOG RECORD DOESN'T FIT IN TWO BUFFERS, THE SECOND BUFFER IS OVERRUN.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The stored procedure log reader splits up log records to fit in
    its 32000 byte buffer. When a log record doesn't fit into one
    buffer, it is split into two parts. The first part fills the
    first buffer and the second part is written to the next buffer.
    When a log record doesn't fit in two buffers, the second buffer
    is overrun.
    
    The same faulty logic exists in the started task log reader but
    it is harder to hit. The started task log reader has a default
    buffer size of 102400, which is big enough to fit the largest
    log record. However, the minimum buffer size is 4096, which is
    even smaller than the stored procedure's 32000 byte limit. If
    the buffer size is reduced to less than half of the length of a
    log record, the started task log reader will overrun the second
    buffer.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: CDC Replication Engine                       *
    *                 for Db2 for z/OS Remote Source               *
    *                 IBM Data Replication                         *
    *                 for Db2  z/OS  Cartridge                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a log record doesn't fit into one  *
    *                      buffer, it is split into two parts.     *
    *                      The first part fills the first buffer   *
    *                      and the second part is written to the   *
    *                      next buffer. When a log record doesn't  *
    *                      fit in two buffers, the second buffer   *
    *                      is overrun.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The stored procedure log reader splits up log records to fit in
    its 32000 byte buffer. When a log record doesn't fit into one
    buffer, it is split into two parts. The first part fills the
    first buffer and the second part is written to the next buffer.
    When a log record doesn't fit in two buffers, the second
    buffer is overrun.
    

Problem conclusion

  • The ability to split long log records was removed and a log
    record longer than the buffer size now fails without writing to
    the buffer. The hidden buffer size parameter was modified to
    have a minimum size of 69632 bytes.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH67593

  • Reported component name

    CLASSIC FED & E

  • Reported component ID

    5697I8200

  • Reported release

    B30

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-07-31

  • Closed date

    2025-10-06

  • Last modified date

    2025-11-03

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

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

    UO05226

Modules/Macros

  •    CECCBCFG CECCCNTL CECCDCFG CECCFGUT CECCLRDD
    CECCLRDE CECCLRDH CECCLRDI CECCLRDQ CECCLRDR CECCLRDT CECCLRD2
    CECCLRD3 CECCLRSM CECCMTO  CECCPACM CECMCFG1
    

Fix information

  • Fixed component name

    CLASSIC FED & E

  • Fixed component ID

    5697I8200

Applicable component levels

  • RB30 PSY UO05226

       UP25/10/08 P F510

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":"BU048","label":"IBM Software"},"Product":{"code":"SSDP9S","label":"InfoSphere Classic Federation Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B30","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Document Information

Modified date:
03 November 2025