PM84395: CROSSLOADER GETS AN ABEND0C4 IN DSNUGSDA+539C ON ENFORCE PHASE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Crossloader utility (load by cursor) sporadically gets abend0C4
    in DSNUGSDA +539C (at level UK83424).
    Analysis of the dump shows that this happens when positioning
    on the SORTOUT dataset which should have the foreign keys that
    need to be read to check for violations.
    It looks to be a timing issue .
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 10 for z/OS users of the LOAD        *
    *                 utility involving tables with unique indexes *
    *                 and referential integrity, with parallel     *
    *                 index build.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABENDS0C4 DSNUGSDA OFFSET539C during    *
    *                      the ENFORCE phase of a LOAD INCURSOR    *
    *                      on a table with unique indexes and      *
    *                      referential integrity.                  *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    A LOAD INCURSOR utility with parallel index build was run on a
    table space with unique indexes and referential integrity (RI).
    The utility abended in the ENFORCE phase with an ABEND0C4 in
    DSNUGSDA +x'539C'.  The abend occurred when LOAD attempted to
    position on the SORTOUT data set to read in the foreign keys
    with data set positioning information that was all zeroes.
    
    During the SORTBLD phase, the SYSUT1 data set is opened.  This
    open acquires a new data set checkpoint control block, copies
    the old block into the new, updates each entry within the block
    with the new address and frees the old checkpoint block.  There
    is a timing window (particularly with small amounts of data)
    where a checkpoint can occur for the SORTOUT data set just prior
    to the creation of the new checkpoint block during the SYSUT1
    open, causing SORTOUT positioning data to be lost.
    
    Also, if the freed checkpoint storage is immediately reused,
    the LOAD can abend in the SORT phase with ABEND0C4 in
    ICETRYB +x'1D76' with ABEND04E RC00E40347 and other possible
    SORT related abends.
    
    Additional Keywords: OFFSET1D76 cross-loader crossloader
    

Problem conclusion

  • LOAD code has been modified to open the SYSUT1 data set prior
    to the attachment of the subtasks in the SORTBLD phase.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM84395

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-08

  • Closed date

    2013-04-23

  • Last modified date

    2013-06-24

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

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

    UK93717 PM89197

Modules/Macros

  •    DSNUGSDA DSNURPIB DSNURPPL DSNURPTB
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM84395

Modified date:

2013-06-24

Translate my page

Machine Translation

Content navigation