PM61736: ABEND04E DSNUGACC+12F8 DURING DGTT APPLICATION THAT USES WORKFILE PARTITION-BY-GROWTH TABLE SPACE (PBG) RC00E400A0

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The 0C4 abend happens due to a garbage xInsLPart value in
    DSNISRTI - OBDPSCMP(xInsLPart) is ON by mistake.
    
    In DSNISGPI, OBDPSET needs to be refreshed after FIND_NEXT_PART
    as is done in DSNISUPI.
    
                                                          (d153538)
    Potential for DB2 crash after the DSNUGACC abend exists
    MSGDSNV086E RC00F30420.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 10 (NFM) for z/OS users of declared  *
    *                 global temporary tables (DGTT) who employ    *
    *                 partition-by-growth table spaces in Workfile *
    *                 database                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABEND0C4 DSNUGACC+12F8 during DGTT      *
    *                      application that uses a partition-by-   *
    *                      growth workfile table space (PBG)       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During a partition-growing insert into a DGTT which was residing
    in a partition-by-growth workfile table space, the 0C4 abend
    occurred because the insert driver module was looking at the
    old (pre-growth) OBDPSET structure while thinking that it was
    looking at the new (post-growth) one.
    
    Specifically, in the old OBDPSET, the OBDPSP2L array slot did
    not exist for the newly grown partition and therefore the module
    was looking at a memory contents that is unaccounted for. This
    made the module go to a wrong code path, which resulted in the
    aforementioned abend.
    

Problem conclusion

  • Code has been changed to make sure that the OBDPSET structure
    is refreshed after growing a new partition, so that the insert
    driver module will have the latest structure at its disposal.
    
    Additional keywords: SQLPBG SQLDGTT
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM61736

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-03

  • Closed date

    2012-07-10

  • Last modified date

    2013-09-04

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

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

    UK80179

Modules/Macros

  •    DSNISGPI DSNITLPE
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK80179

       UP12/07/25 P F207

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM61736

Modified date:

2013-09-04

Translate my page

Machine Translation

Content navigation