IC60472: TSM SERVER CAN CRASH WHEN SENSE DATA IS EXPECTED FROM A LIBRARY DEVICE WHICH IS ATTACHED TO A DATAMOVER

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

• If a problem is encountered with a tape library attached to a
  datamover(NAS) and sense data is requested by the TSMserver,
  a crash can occur.
  -
  The most likely cause of the crash is that sense data which
  was requested from the datamover was not returned from the
  library device due to a connectivity problem. A crash may also
  occur if the library device was removed without removing it
  or setting it offline to the TSM server.
  TSM Versions Affected: All 5.4 and 5.5 servers
  Customer/L2 Diagnostics:
  The call stack from a core dump on AIX may look like this:
  -
  (dbx) where
  .() at 0xf414
  spiRemoteIoctl@AF57_33(??, ??, ??, ??, ??, ??, ??) at
  0x900000000cad68c
  spiRemoteIoctl(??, ??, ??) at 0x900000000ca7918
  TsmRemoteOpen(0x133df74d8, 0x809000000000000, 0x0, 0x0, 0x0,
  0x0, 0x13465d220, 0x9001000a035ec28) at 0x1005846fc
  PvrRemoteOpenAuto(??, ??, ??) at 0x100582a44
  PvrOpenAutoDevice(??, ??, ??, ??) at 0x10024f620
  OpenAutoDevice(??) at 0x1004a2d6c
  MmsAcquireAuto(??, ??, ??, ??) at 0x10048e0cc
  BuildConfig(??) at 0x1004ac3dc
  PerformInit(??) at 0x1004aa878
  InitThread(??) at 0x1004aaccc
  StartThread(??) at 0x100015194
  Initial Impact: Medium
  Additional Keywords:
  nas datamover path update ndmp crash core restart spi zz61
  

Local fix

• None. Apply fix when available.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager customers who     *
  *                 back up NAS devices to a locally             *
  *                 attached library                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be         *
  *                 fixed in levels 5.4.6,5.5.3 and 6.1.2.       *
  *                 Note that this is subject to change at       *
  *                 the discretion of IBM.                       *
  ****************************************************************
  *
  

Problem conclusion

• The error has been fixed.
  

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

• R51A PSY

     UP

• R51H PSY

     UP

• R51L PSY

     UP

• R51S PSY

     UP

• R51W PSY

     UP

• R52A PSY

     UP

• R52H PSY

     UP

• R52L PSY

     UP

• R52S PSY

     UP

• R52W PSY

     UP

• R53A PSY

     UP

• R53H PSY

     UP

• R53L PSY

     UP

• R53S PSY

     UP

• R53W PSY

     UP

• 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

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP