IBM Support

PK49729: RENAME SAFE RECEIVE ERROR MSGIEC030I B37-04,IFG0554A,TECRCSRN,STEP010,VOLDUMP ON THE VOLBKUP DATA

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • RENAME SAFE receive error MSGIEC030I
    B37-04,IFG0554A,TECRCSRN,STEP010,VOLDUMP on the volbkup data
    A larger volbkup data set was created and the contents of the
    original data set copied to the new data set. The data sets were
    renamed so the new data set had the same data set name as the
    original data set.
    RENAME RERUN got: CKZ11533E UNEXPECTED END OF FILE ON VOLBKUP
    The problem (CKZ11533E) is that the writes to the volbkup data
    set are being buffered which causes DB2 Cloning Tool to think
    the meta data backup for a volume has been physically written to
    the volbkup data set when it has not.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of DB2 Cloning Tool for z/OS.      *
    ****************************************************************
    * PROBLEM DESCRIPTION: RENAME SAFE receive error MSGIEC030I    *
    *                      B37-04,IFG0554A,TECRCSRN,STEP010,       *
    *                      VOLDUMP on the volbkup data. A larger   *
    *                      volbkup data set was created and the    *
    *                      contents of the original data set       *
    *                      copied to the new data set. The data    *
    *                      sets were renamed so the new data set   *
    *                      had the same data set name as the       *
    *                      original data set.  RENAME RERUN got:   *
    *                      CKZ11533E UNEXPECTED END OF FILE ON     *
    *                      VOLBKUP the problem (CKZ11533E) is      *
    *                      that the writes to the volbkup data     *
    *                      set are being buffered which causes     *
    *                      DB2 Cloning Tool to think the meta      *
    *                      data backup for a volume has been       *
    *                      physically written to the volbkup data  *
    *                      set when it has not.                    *
    ****************************************************************
    * RECOMMENDATION: Apply the  PTF.                              *
    ****************************************************************
    Code has been changed to correct reported problem.
    

Problem conclusion

  • Apply the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK49729

  • Reported component name

    DB2 CLONING TOO

  • Reported component ID

    5655N1000

  • Reported release

    110

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-07-25

  • Closed date

    2007-08-02

  • Last modified date

    2007-09-04

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

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

    UK27806

Modules/Macros

  •    CKZ00110
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R110 PSY UK27806

       UP07/08/07 P F708

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":"SSAUUE","label":"IBM Db2 Cloning Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"110","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 February 2021