IBM Support

PM93578: GENERAL REPORT NOT PROPERLY SKIPPING RECOVER TIMERANGE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If table or tablespace object(s) are filtered upon, and any
    given table in the result set has a point-in-time recovery
    within the requested timeframe, DML activity that occurred
    within that timeframe may be reported on in the general report.
    It should not be since the RECOVER should preclude such
    reporting unless the misc flags=p is set.
    If a detail report was also requested, ALAA447E may also occur
    in this case in log-forward mode, depending on when appropriate
    image copies were taken.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Object Restore.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: If table or tablespace object(s) are    *
    *                      filtered upon, and any given table in   *
    *                      the result set has a point-in-time      *
    *                      recovery within the requested           *
    *                      timeframe, DML activity that occurred   *
    *                      within that timeframe may be reported   *
    *                      on in the general report. It should not *
    *                      be since the RECOVER should preclude    *
    *                      such reporting unless the misc          *
    *                      flags=p is set. If a detail report was  *
    *                      also requested, ALAA447E may also       *
    *                      occur in this case in log-forward mode, *
    *                      depending on when appropriate image     *
    *                      copies were taken.                      *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM93578

  • 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

    2013-07-22

  • Closed date

    2013-08-09

  • Last modified date

    2013-09-03

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

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

Modules/Macros

  • ALASQL0
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R330 PSY UK96579

       UP13/08/28 P F308

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.3.0"}]

Document Information

Modified date:
31 March 2021