PK56579: CKZ11533E UNEXPECTED END OF FILE ON VOLBKUP

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• CKZ11533E UNEXPECTED END OF FILE ON VOLBKUP
  RENAME SAFE got: IEC030I
  B37-04,IFG0554A,TECRCSRN,STEP010,VOLDUMP on the volbkup data
  set.
  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  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: Users of DB2 Cloning Tool for Z/OS.          *
  ****************************************************************
  * PROBLEM DESCRIPTION: CKZ11533E UNEXPECTED END OF FILE ON     *
  *                      VOLBKUP RENAME SAFE got: IEC030I        *
  *                      B37-04,IFG0554A,TECRCSRN,STEP010,       *
  *                      VOLDUMP on the volbkup data set.        *
  *                      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  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 this condition.
  

Problem conclusion

• APPLY the PTF.
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

•    CKZ00110
  

Fix information

• Fixed component name

  DB2 CLONING TOO

• Fixed component ID

  5655N1000

Applicable component levels

• R210 PSY UK32642

     UP08/01/04 P F801

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.