IBM Support

PI70815: REORG ABEND04E RC00E70010 DSNXGRDS.DSNXIPND:P080 WHEN MATERIALIZATION OF PENDING DEFINITION CHANGES ENCOUNTERS ERRORS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When REORG utility materializes a pending definition change
    (such as a pending column alteration), if any error is
    encountered during the regeneration advanced triggers that are
    dependent on the altered table, DB2 abends with ABEND04E
    RC00E70010 DSNXGRDS.DSNXIPND:P080 rather than issuing an
    appropriate error message.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All DB2 12 for z/OS users of ALTER TABLE ALTER COLUMN with   *
    * subsystem parameter DDL MATERIALIZATION set to               *
    * ALWAYS_PENDING                                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * REORG abends with ABEND04E RC00E70010 DSNXGRDS.DSNXIPND:P080 *
    * when materialization of pending changes enounters errors.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When REORG utility materializes a pending definition change
    (such as a pending column alteration that was executed with
    subsystem parameter DDL MATERIALIZATION set to ALWAYS_PENDING),
    if any error is encountered during the regeneration of advanced
    triggers that are dependent on the altered table, DB2 abends
    with ABEND04E RC00E70010 DSNXGRDS.DSNXIPND:P080 rather than
    issuing an informative error message.
    

Problem conclusion

  • DB2 has been modified so that REORG utility issues a new more
    informative
    error message DSNU276I to indicate which object encountered
    regeneration
    or rebind errors during materialization of pending definition
    changes.
    
    Following is the new message DSNU276I:
    
      DSNU276I - csect-name - PENDING DEFINITION CHANGES CANNOT BE
    MATERIALIZED DUE
      TO ERROR ENCOUNTERED FOR object-type OBJECT
    object-schema.object-name
      REASON reason
    
      Explanation:  During REORG processing or materialization of
    pending definition
      changes on the target table space, an error is encountered
    which prevented REORG
      from continuing execution and resulted in the ABEND04E
    RC00E400AF abnormal
      termination.
    
      csect-name - the name of the control section that issued the
    message.
      object-type - the type of object that encountered an error.
      object-schema- the schema name of the object that encountered
    an error.
      object-name- the name of the object that encountered an error.
      reason - one of the following reasons can be returned:
               REGENERATION OR REBIND FAILURE OF A DEPENDENT TRIGGER
               Materialization of a pending definition change failed
    due to an error
               encountered when regenerating a dependent trigger or
    rebinding the
               dependent trigger's package.  The SQLCA contents for
    the encountered
               failure are returned in a prior DSNU283I message.
    
      System action:  Utility processing terminated
    
      User response:  Correct the user object based on the reported
    reason.  Re-execute
      REORG TABLESPACE with SHRLEVEL REFERENCE or CHANGE to
    materialize the pending
      definition changes.
    
      REGENERATION OR REBIND FAILURE OF A DEPENDENT TRIGGER
        Examine the SQLCA returned by the prior DSNU283I message and
    correct the problem
        based on the reported error.  In some cases, an ALTER
    TRIGGER statement with
        REGENERATE option may be used to validate that the trigger
    can be regenerated
        successfully prior to re-executing the REORG.
    
      Severity: 8 (error)
    
    Additional Keywords:
    
    SQLALTER
    DSNXIPND P080
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI70815

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-17

  • Closed date

    2017-03-23

  • Last modified date

    2017-05-01

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

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

    UI45800

Modules/Macros

  • DSNFUDIR DSNXIRTR DSNUMSGA DSNXIPND DSNFUDRA DSNXI00  DSNURFIT
    DSNUGPAM
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI45800

       UP17/04/07 P F704

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 May 2017