IBM Support

PM34122: POSSIBLE PROBLEMS WITHIN LOG ANALYSIS TOOL WHEN ARCHLOG1 OR ARCHLOG2 IS WRITTEN TO MULTIPLE VOLUMES BUT THE OTHER IS NOT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If archlog2 is written to multiple volumes but archlog1 is not,
    then it is possible that DB2 Log Analysis Tool may read both
    datasets and report duplicate activity. This could lead to
    ALAA440E or ALAA040E depending on the situation. The most common
    problem is duplicate activity reported in the General Report.
    

Local fix

  • Update the setup options to only use ARCHLOG1 or ARCHLOG2
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis Tool.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: If archlog2 is written to multiple      *
    *                      volumes but archlog1 is not, then it    *
    *                      is possible that DB2 Log Analysis Tool  *
    *                      may read both datasets and report       *
    *                      duplicate activity. This could lead to  *
    *                      ALAA440E or ALAA040E depending on the   *
    *                      situation. The most common problem is   *
    *                      duplicate activity reported in the      *
    *                      General Report.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Apply the PTF
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM34122

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-03-03

  • Closed date

    2011-05-09

  • Last modified date

    2011-06-02

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

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

Modules/Macros

  •    ALABSDS
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R310 PSY UK67558

       UP11/05/13 P F105

  • R320 PSY UK67559

       UP11/05/13 P F105

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":"310"}]

Document Information

Modified date:
18 March 2021