IC44820: FILE TYPE VOLUMES ARE NOT BEING DELETED AFTER REUSEDELAY PERIOD HAS BEEN EXCEEDED.

APAR status

• Closed as program error.

Error description

• An empty file type volume, that is in pending state, may not
  be deleted after the reusedelay period has been exceeded.
  This can occur if the volume was created prior to an upgrade
  to TSM Server version 5.3. The following describes the
  scenario in which this problem can occur:
  .
  NOTE: This only occurs for volumes residing in a storage
  pool where reusedelay is being utilized.
  .
  1) File volume created and written to prior to TSM 5.3
  2) TSM Server is upgraded to the 5.3 level
  3) The file volume is emptied and goes into pending state
  4) The TSM Server is recycled prior to the reusedelay period
     being met.
  .
  Per the TSM 5.3 readme, when the TSM 5.3 server starts,
  existing FILE volumes in FILLING state are marked as full.
  This is to prevent the 5.3 TSM Server from appending data to
  a file volume containing data written by a pre-5.3 TSM Server.
  .
  In this case, pending volumes that are empty are being marked
  as full preventing the TSM Server from deleting them even
  after the reusedelay period has been exceeded.
  .
  Platforms affected: All TSM 5.3 Servers
  .
  Customer/L2 Diagnostics
  In order for this APAR to apply, a customer must be
  running a 5.3 TSM Server. If a file type volume shows as
  FULL, but has a pending date, this APAR applies.
  Q volume can be used to find this information.
  .
  I.E.
  Q vol <volume name> f=d
  
  Volume Status: Full
  Date Became Pending: xx/xx/xxxx
  .
  Initial Impact: Medium
  .
  Additional Keywords: ASVA ASVS asvolrestart legacy recycle
                       devtype file sequential check reclaim
  

Local fix

• 1) Run repair volseg <volname> against affected volume
  2) Delete the volume after the reusedelay period
     has been exceeded.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All TSM 5.3.0 server users with FILE volumes *
  *                 created prior to TSM 5.3.0 and in a storage  *
  *                 pool with REUSEDELAY set.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in level 5.3.1. Note that this is subject to *
  *                 change at the discretion of IBM.             *
  ****************************************************************
  See ERROR DESCRIPTION.
  

Problem conclusion

• The TSM server will no longer mark FILE volumes in the PENDING
  state as FULL upon startup.
  

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:

Fix information

• Fixed component name

  TSM SERVER 510

• Fixed component ID

  5698ISMSV

Applicable component levels

• R53A PSY

     UP

• R53H PSY

     UP

• R53L PSY

     UP

• R53S PSY

     UP

• R53W PSY

     UP