IBM Support

PI49328: POSSIBLE LOOP/HANG AFTER MEMORY EXHAUSTION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A loop/hang has been reported in program ALADTL1 after memory
    has been exhausted for the run. Error processing fails in this
    case first, and a WTO message is put out to the joblog
    indicating message ALAA500 occurred.
    

Local fix

  • Resolve the memory issue by reducing the report timeframe and/or
    reducing the number of objects be tracked.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the DB2 Tool Log Analysis.          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    *                                                              *
    *                      A loop/hang has been reported           *
    *                      in program ALADTL1 after memory         *
    *                      has been exhausted for the run.         *
    *                       Error processing fails in this         *
    *                      case first, and a WTO message           *
    *                      is put out to the joblog                *
    *                      indicating message ALAA500              *
    *                                                              *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    *                                                              *
    *                 A loop/hang has been reported                *
    *                 in program ALADTL1 after                     *
    *                 memory has been exhausted for                *
    *                 the run.                                     *
    *                  Error processing fails                      *
    *                 in this case first,                          *
    *                 and a WTO message                            *
    *                 is put out to the joblog                     *
    *                 indicating message ALAA500                   *
    *                 occurred.                                    *
    ****************************************************************
    

Problem conclusion

  • Apply the PTF
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI49328

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    340

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-09-24

  • Closed date

    2015-10-19

  • Last modified date

    2015-11-04

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

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

    UI32160 UI32161

Modules/Macros

  •    ALALF1
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R340 PSY UI32160

       UP15/10/27 P F510

  • R350 PSY UI32161

       UP15/10/27 P F510

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.4.0"}]

Document Information

Modified date:
30 March 2021