IC78241: AFTER AUDIT VOLUME FIX=YES ON DISK POOL VOLUMES REPORTS PCT UTIL AS A NEGATIVE NUMBER

IBM Tivoli Storage Manager (TSM) server V6.2.3.x interim fix downloads

APAR status

• Closed as program error.

Error description

• After migration has run completely  (set to LOW threshold of 0
  (zero))  disk pool volumes still reported data remaining.  Query
  Content on these volumes reported no objects found.  AUDIT
  VOLUME FIX=NO reports error:
  
  Example:
  ANR2017I Administrator NAME issued command:
  AUDIT VOLUME /path/to-disk-volime/vol_name fix=no  (SESSION:
  number)
  ANR9999D_0550440134 DsAuditEmptyVol(dsaudit.c:329)
  Thread<34326>: Erroreous data found for empty volume
   /path/to-disk-volume/vol_name. Re-run the AUDIT VOLUME with
  FIX=YES
  after setting the volume to READ_ONLY to correct the database
  information. (SESSION: number)
  
  Subsequent AUDIT VOLUME with FIX=YES does report that it fixes
  objects, but the Q Volume now reports the percent utilized with
  a negative number.
  Example:
  Pct Util: -7.5
  
  If a second audit volume with fix=yes will increase this
  negative number.
  
  Query Storage pool reports the Percent Utilized as 100% and
  Percent Migrate as 0 (zero)
  Example:
  Pct Util: 100.0
  Pct Migr: 0.0
  
  This was found to be due to a miss calculation held in memory
  after the Audit Volume Fix=Yes.
  
  Initial Impact: Low
  
  Additional Keywords: TSM aud v f=y  f=n q stg zeroaudit volume
  

Local fix

• After disk migration has migrated all data, do audit volume
  fix=yes on volumes that still report data, then restart the TSM
  server to clear the incorrect memory count.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users of   *
  *                 the AUDIT VOLUME command on DISK volumes.    *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in level and 6.2.4 . Note that this          *
  *                 is subject to change at the discretion of    *
  *                 IBM.                                         *
  ****************************************************************
  *
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, HP-UX, 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

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP