IC59105: PREDEFINED SEQUENTIAL VOLUMES EMPTIED BY MIGRATION NOT AVAILABLE FOR REUSE UNTIL PROCESS COMPLETES. CAN LEAD TO OUT OF STG SPACE.

IBM Tivoli Storage Manager V6.1 Fix Pack 2 (6.1.2) Server Downloads
IBM Tivoli Storage Manager V6.1 Fix Pack 3 (6.1.3) Server Downloads

APAR status

• Closed as program error.

Error description

• Client backup/archive processing fails with server out of
  storage space condition when storing to a sequential storage
  pool with predefined volumes and migration from that pool is
  running. The TSM server places a lease on each input volume
  processed by migration. For predefined sequential volume this
  lease remains on the volume for the full time migration is
  running. These volumes with a lease on them cannot be used by
  other processes or sessions. This means tht volumes can become
  empty through migration processing but cannot be used until the
  process that emptied them completes. The leasing of these
  volumes should terminate when the last transaction returning
  them to an empty status completes. If/when backups occur to this
  this type of predefined sequential storage pool and a long
  running migration process begins, the storage pool could run out
  of space as the remaining free space in the pool is filled and
  the empty volumes remain leased by the migration process.
  TSM Versions Affected: 5.4.x, 5.5.x
  Initial Impact: Medium
  Additional Keywords: stg stgpool full empty
  

Local fix

• Use scratch volumes or make sure your high and low migration
  thresholds are set to values that allow migratoin to complete
  before the storage pool can fill.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: TSM server users.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available.           *
  *                 This problem is currently projected to       *
  *                 be fixed in levels 5.4.5 and 5.5.3.          *
  *                 Note that this is subject to change at       *
  *                 the discretion of IBM.                       *
  ****************************************************************
  *
  

Problem conclusion

• The TSM server has been corrected.
  

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:

  PK79251 PK79252

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R54A PSY

     UP

• R54H PSY

     UP

• R54L PSY

     UP

• R54S PSY

     UP

• R54W PSY

     UP

• R55A PSY

     UP

• R55H PSY

     UP

• R55L PSY

     UP

• R55S PSY

     UP

• R55W PSY

     UP