IBM Support

PH08638: POSSIBLE ABEND906-08 IN ALADTL4

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If generating UNDO SQL for the tables with the large volume of
    activity that has referential integrity constraints, it is
    possible to get an ABEND S906. The Abend is due to reaching of
    the maximum number of call FECLINKL operations. This APAR will
    correct the situation and allow the job to finish without
    abending.
    

Local fix

  • Limit the amount of data reported until the product will be able
    to process the data without abending.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM Db2 Log Analysis Tool z/OS.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: If generating UNDO SQL for the tables   *
    *                      with the large volume of activity that  *
    *                      has referential integrity constraints,  *
    *                      it is possible to get an ABEND S906.    *
    *                      The Abend is due to reaching of the     *
    *                      maximum number of call FECLINKL         *
    *                      operations. This APAR will correct the  *
    *                      situation and allow the job to finish   *
    *                      without abending.                       *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH08638

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    350

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-15

  • Closed date

    2019-03-18

  • Last modified date

    2019-04-02

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

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

Modules/Macros

  • ALA@FD28 ALA@FFN8 ALA@FSP  ALAFR6   ALAGEND  ALAIDRP  ALAIN4X
    ALAIN4XR ALAIN5DX ALAIN5GX ALAIN5X  ALALB2   ALALB3   ALAPRI
    ALAPRI2  ALASBDF  ALASQ1CA ALASQ1CB ALASQ9CA ALASQL0  ALASQL0A
    ALASQL0B ALASQL1  ALASQL1A ALASQL1B ALASQL1C ALASQL2  ALASQL2A
    ALASQL2B ALASQL9  ALASQL9A ALASQL9B ALASQL9C ALASQLPR ALASUBG
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R350 PSY UI61952

       UP19/03/20 P F903

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.5.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 April 2019