IC89231: UNEXPECTED DRIVE CLEANING CAN BE INVOKED WHILE SERVER RUNNING DRIVE OPERATIONS

IBM Tivoli Storage Manager (TSM) server V6.3.3.x interim fix downloads
IBM Tivoli Storage Manager V5.5 Fix Pack 7 (5.5.7.000) Server Downloads

APAR status

• Closed as program error.

Error description

• Cleaning drive operation can be invoked unexpectedly while drive
  operation such as mount/dismount running on Tivoli Storage
  Manager server or Storage Agent.
  The situation can occur when the "cleanFrequency" option for
  the drive definition is set to "gigabytes" or "asneeded" on
  Windows platforms.
  Even when the amount of bytes written does not reach the
  gigabytes set or there is no valid request from H/W, Tivoli
  Storage Manager server mistakenly interpret SENSE code from
  drives and judge that drive cleaning should be made.
  
  Tivoli Storage Manager Versions Affected: All supported versions
  on Windows platform.
  
  
  Customer/L2 Diagnostics (If Applicable)
  When collecting the results of "show library" commands for every
  few minutes, it can be seen that needsCleaning flag become "1"
  even though the value of KBytesProc does not exceed the value of
  CleaningFreq or though there has not been H/W cleaning request.
  
  Here will be seen in the result of "show library" command.
  ---------------
  CleaningFreq(GB)=XXXXX, KBytesProc=YYYYY, needsCleaning=1.
  
  
  Initial Impact: Middle
  
  Additional Keywords: zz55 zz61 zz62 zz63 cleanFrequency
  needsCleaning clean drive
  

Local fix

• To avoid the problem, set cleanFrequency option to "none" with
  "update drive" command.
  When the value is set for the option, drive cleaning operations
  which are invoked by H/W should be suppressed.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users of   *
  *                 server-managed drive cleaning with IBM       *
  *                 tape drives.                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: See error description.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 5.5.7, 6.2.6, and 6.3.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

• R55A PSY

     UP

• R55H PSY

     UP

• R55L PSY

     UP

• R55S PSY

     UP

• R55W PSY

     UP

• R55Z PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP

• R62Z PSY

     UP

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP

• R63Z PSY

     UP