IBM Support

PK44569: DISASTER RECOVERY BUILD MAY INCORRECTLY PROCESS MULTI-VOLUME DB2 ARCHIVED LOGS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When processing DB2 archived logs that span volumes, the
    disaster recovery build process may not correctly catalog
    and build the archived logs.  This change will allow
    multi-volume archived logs to be correctly copied providing
    they are cataloged.
    
    Additionally, this APAR adds the CURRENT keyword to REPORT
    RECOVER and removes the NOSCRATCH option from the VSAM delete
    statements.
    

Local fix

  • Reduce the size of the DB2 active logs or archive the logs to
    devices that can allow for the complete log on a single
    volume.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Automation Tool.                *
    ****************************************************************
    * PROBLEM DESCRIPTION: When processing DB2 archived logs that  *
    *                      span volumes, the disaster recovery     *
    *                      build process may not correctly         *
    *                      catalog and build the archived logs.    *
    *                      This change will allow multi-volume     *
    *                      archived logs to be correctly copied    *
    *                      providing they are cataloged.           *
    *                      Additionally, this APAR adds the        *
    *                      CURRENT keyword to REPORT RECOVER and   *
    *                      removes the NOSCRATCH option from the   *
    *                      VSAM delete statements.                 *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK44569

  • Reported component name

    DB2 AUTOMATION

  • Reported component ID

    5697G6300

  • Reported release

    220

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-05-03

  • Closed date

    2007-10-29

  • Last modified date

    2007-11-02

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

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

    UK30735

Modules/Macros

  • HAA#DDL  HAA#DDL9 HAA#DD7  HAA#YARC HAA#YCAL
    HAA#YCTL HAA#YDEL HAA@YCPL HAAAMPER H25H220J
    

Fix information

  • Fixed component name

    DB2 AUTOMATION

  • Fixed component ID

    5697G6300

Applicable component levels

  • R220 PSY UK30735

       UP07/11/01 P F710

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAUWB","label":"IBM Db2 Automation Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"220","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"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":"220","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
12 February 2021