IBM Support

PM16187: DB2 LOG ANALYSIS TOOL IS SPECIFYING THE FILE SEQUENCE NUMBER WHEN REQUESTING A CATALOGED IMAGE COPY THAT IS ON TAPE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Datasets that are cataloged do not need to have the file
    sequence number specified during allocation as the catalog will
    supply that information. This can lead to a 'EDG4029I. Volume
    rejected dataset name does not match for a recorded volume' if
    the dataset was moved to a different file sequence number either
    on the same volume or a different volume.
    

Local fix

  • To temporarily get around this issue, the image copy will need
    to be copied / moved back to a volume specifying the original
    file sequence number as shown in SYSIBM.SYSCOPY
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Datasets that are cataloged do not need *
    *                      to have the file sequence number        *
    *                      specified during allocation as the      *
    *                      catalog will supply that information.   *
    *                      This can lead to a 'EDG4029I. Volume    *
    *                      rejected dataset name does not match    *
    *                      for a recorded volume' if the dataset   *
    *                      was moved to a different file sequence  *
    *                      number either on the same volume or a   *
    *                      different volume.                       *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM16187

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-06-08

  • Closed date

    2010-08-03

  • Last modified date

    2010-09-02

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

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

Modules/Macros

  •    ALASUBG
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R310 PSY UK59393

       UP10/08/12 P F008

  • R320 PSY UK59394

       UP10/08/12 P F008

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

Document Information

Modified date:
12 April 2021