IT16933: Extents not marked as damaged when update stgpooldir access=destroyed is run

7.1.7.100-TIV-TSMSRV-WIN
7.1.7.100-TIV-TSMSRV-SolarisSPARC
7.1.7.100-TIV-TSMSRV-Linuxx86_64
7.1.7.100-TIV-TSMSRV-Linuxs390x
7.1.7.100-TIV-TSMSRV-Linuxppc64
7.1.7.100-TIV-TSMSRV-HP-UX
7.1.7.100-TIV-TSMSRV-AIX
IBM Spectrum Protect Server V7.1.7.X interim fix downloads
IBM Spectrum Protect Server V7.1 Fix Pack 8 (7.1.8.000) Downloads

APAR status

• Closed as program error.

Error description

• When a storage pool directory is updated with access=destroyed
  all of the extents in all the containers within the stgpooldir
  are marked as damaged. At IBM Spectrum Protect server level
  7.1.7.000 the update stgpooldir command using the
  access=destroyed option will not mark all of the extents as
  damaged even though the command run to successful completion.
  Subsequent audits or repair commands run to process damaged
  extents will therefore not process all the extents that they
  should.
  

Local fix

• Use the audit container command with stgpool=<container pool
  name> stgpooldir=<storage pool directory>  and
  action=markdamaged options to ensure that all the extents in the
  stgpooldir being updated to an access of destroyed are flagged
  as damaged.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager server users.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in levels 7.1.7.100 and 7.1.8. Note    *
  * that this is subject to change at the discretion of IBM.     *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, Solaris, Linux, and Windows.
  

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

• Fixed component ID

  5698ISMSV

Applicable component levels

• R71A PSY

     UP

• R71L PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP