IBM Support

PM35893: POSSIBLE S0C4 WHEN CREATING A LOADFILE DUE TO A TABLE WITH ROW REORDER FORMAT HAVING A COLUMN ADDED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a loadfile is being generated in DB2 Log Analysis for
    multiple tables in row reorder format and one table has a new
    column but the data is not present for that column yet (the
    REORG has not been performed on the object yet) it is possible
    to get a S0C4 due to a value not being cleared out from the
    previous record. Once the table has been reorged and the table
    is only processed from the REORG point forward - this is no
    longer a problem
    

Local fix

  • By removing the table that had the column added, the rest of the
    tables will process correctly. The table that had the column
    added may be able to be processed by itself, but that depends on
    the format of the data and the ordering of the activity.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis Tool.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: If a loadfile is being generated in     *
    *                      DB2 Log Analysis for multiple tables    *
    *                      in row reorder format and one table has *
    *                      a new column but the data is not        *
    *                      present for that column yet (the REORG  *
    *                      has not been performed on the object    *
    *                      yet) it is possible to get a S0C4 due   *
    *                      to a value not being cleared out from   *
    *                      the previous record. Once the table has *
    *                      been reorged and the table is only      *
    *                      processed from the REORG point          *
    *                      forward - this is no longer a problem.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Apply the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM35893

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-03-29

  • Closed date

    2011-05-09

  • Last modified date

    2011-06-02

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

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

Modules/Macros

  •    ALABSDS
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R310 PSY UK67558

       UP11/05/13 P F105

  • R320 PSY UK67559

       UP11/05/13 P F105

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

Document Information

Modified date:
12 April 2021