IBM Support

PK22246: ABEND S0C4 DURING PROGRAM ALAGEN1 DUE TO EXCESSIVE LOG DATA TRACKED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When massive amounts of log data are tracked and stored
    internally (approx. 15 million UNDO/REDO log records), a storage
    overlay is possible causing the ABEND S0C4 either in csect
    ALAGEN1 or ALASUBG (both during general report processing). This
    APAR addresses both an increase in the size of this failing
    storage area and an appropriate error message (rather than an
    ABEND S0C4) in cases where the size is still exceeded.
    
    OTHER KEYWORDS: ABEND0C4 0C4 S0C4
    

Local fix

  • As the fix will not allow more processing, alternative solutions
    are:
    * run for shorter time period and
    * provide more filtering.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: When massive amounts of log data are    *
    *                      tracked and stored internally (approx.  *
    *                      15 million UNDO/REDO log records), a    *
    *                      storage overlay is possible causing     *
    *                      the ABEND S0C4 either in csect ALAGEN1  *
    *                      or ALASUBG (both during general report  *
    *                      processing). This APAR addresses both   *
    *                      an increase in the size of this         *
    *                      failing storage area and an             *
    *                      appropriate error message (rather than  *
    *                      an ABEND S0C4) in cases where the       *
    *                      size is still exceeded.                 *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK22246

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    230

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2006-03-27

  • Closed date

    2006-04-18

  • Last modified date

    2006-05-01

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

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

Modules/Macros

  •    ALAA40
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R220 PSY UK13667

       UP06/04/25 P F604

  • R230 PSY UK13668

       UP06/04/25 P F604

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":"230"}]

Document Information

Modified date:
18 March 2021