IBM Support

PI19362: ABEND U=0031 IN MODULE ALADTL2

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If processing multiple compressed Tablespaces, it is possible to
    get a U=0031 ABEND (USER COMPLETION CODE=0031) in module
    ALADTL2. This can occur when processing a non-partitioned
    Tablespace after a certain occur when processing a
    non-partitioned Tablespace after a certain partitioned
    Tablespace. This should only occur if the non-partitioned
    Tablespace has an insert-generated dictionary.
    

Local fix

  • 1) Reorg the Tablespace that is causing the issue.
    or
    2) Remove the object that is causing the issue and run it by
       itself.
    or
    3) Log Forward processing may or may not be successful depending
       on the order of the objects and if DCC is in use.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis for zOS.           *
    ****************************************************************
    * PROBLEM DESCRIPTION: If processing multiple compressed       *
    *                      Tablespaces, it is possible to get a    *
    *                      U=0031 ABEND (USER COMPLETION           *
    *                      CODE=0031) in module ALADTL2. This can  *
    *                      occur when processing a                 *
    *                      non-partitioned Tablespace after a      *
    *                      certain occur when processing a         *
    *                      non-partitioned Tablespace after a      *
    *                      certain partitioned Tablespace. This    *
    *                      should only occur if the                *
    *                      non-partitioned Tablespace has an       *
    *                      insert-generated dictionary.            *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI19362

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    330

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-06-04

  • Closed date

    2014-08-20

  • Last modified date

    2014-09-03

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

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

    UI20736 UI20737

Modules/Macros

  • ALADTS   ALAEXP
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R330 PSY UI20736

       UP14/08/28 P F408

  • R340 PSY UI20737

       UP14/08/28 P F408

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.3.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 September 2014