IC68191: SANDISCOVERY CAN NOT UPDATE AN IBM TAPE PATH IF IT FAILS TO OPEN THIS DEVICE FIRST AND THEN FINDS A SERIAL NUMBER MISMATCH

APAR status

• Closed as program error.

Error description

• This problem only affects IBM tape drives if these tape device
  names are always changed frequently on the SAN.
  When the SAN discovery successfully finds a new tape device to
  an IBM tape drive for an error code as ERROR_FILE_NOT_FOUND, it
  always converts an IBM tape device file name format got from the
  HBAAPI as TapeX to a name format as \\.\TapeX. This new file
  format is stored in an internal array for a further device
  serial mismatch checking. When it detects a serial number
  mismatch for this device \\.\TapeX just found, it will find a
  new device as TapeY from the HBAAPI immediately. This new device
  file will replace the one found previously as \\.\TapeX to this
  internal array. Since this array is not initialized, the device
  file name in this array will become as TapeYapeX.This is an
  invalid device file name on Windows platforms, the SAN discovery
  is not able to open it to get the device serial number.So the
  SAN discovery will fail to update a device path when the device
  serial mismatch occurs to this device.
  
  Tivoli Storage Manager Versions Affected:
  
    Windows 6.1 and 6.2
  
  Customer/L2 Diagnostics :
  
  We encountered this with a VTL TS7650 .
  From actlog
  
  18:40:39  ANR8974I Found new path for SERVERLC and target
    name DRIVE2 old path mt0.3.0.4 new path \\.\Tape5. Path
    information will be updated remotely.  (SESSION: 3)
  18:40:39  ANR0409I Session 5 ended for server SERVERLM
    (Windows).   (SESSION: 3)
  18:40:39  ANR1404W Scratch volume mount request denied -
    mount failed. (SESSION: 3)
  
  From trace
  
  [36][output.c][6673][PutConsoleMsg]:ANR0409I Session 6 ended for
   server SERVERLM (Windows).~
  [36][output.c][6673][PutConsoleMsg]:ANR8974I Found new path for
   SERVERLC and  target name DRIVE2 old path mt0.3.0.4  new path
   \\.\Tape5. Path information will be updated remotely. ~
  [36][mmsdrive.c][12709][DiscoverNewPath]:Updated drive DRIVE2
   (\\.\Tape5) with new path \\.\Tape5 and handle 67420.
  [36][mmsdrive.c][8159][MmsCheckTapeId]:Drive DRIVE2 devType 20
   opened with handle 67420.
  [36][psntpop.c][3748][IBMTapeXinquiry]:Convert is set to 0.
  [36][psntpop.c][3795][IBMTapeXinquiry]:(IBMTapeXinquiry) Issuing
   IOCTL_SCSI_PASS_THROUGH to get tape drive's vendor id with
   handle 67420 in Windows.
  [36][psntpop.c][3951][IBMTapeXinquiry]:(IBMTapeXinquiry) Issuing
   IOCTL_SCSI_PASS_THROUGH to get tape drive's serial with handle
   67420 in Windows.
  [36][psntpop.c][4109][IBMTapeXinquiry]:(IBMTapeXinquiry) Issuing
   IOCTL_SCSI_PASS_THROUGH to get drive's WWN with handle 67420 in
   Windows.
  [36][psntpop.c][4242][IBMTapeXinquiry]:(IBMTapeXinquiry) The
   drive has a valid WWN and the FC identifier type is 3
  [36][psntpop.c][4330][IBMTapeXinquiry]:(IBMTapeXinquiry) The
   drive's Serial number is [1960994020] Vendor name is [IBM] and
   WWN is [20000000C97C6A52] in Window
  [36][mmsdrive.c][8185][MmsCheckTapeId]:Xinquiry was successful
   for drive DRIVE2; opened with path \\.\Tape5 serial
   [1960994020], wwn [20000000C97C6A52], and vendor [IBM].
  [36][mmsdrive.c][8193][MmsCheckTapeId]:Serial number mismatch!
   The serial in descriptor is [1960994008], and the serial for
   inquiry is [1960994020] for drive DRIVE2
  [36][mmsdrive.c][12484][DiscoverNewPath]:Attemtping to discover
   a new path for drive DRIVE2 (\\.\Tape5) with serial number of
   1960994008.
  
  Sandiscovery function to search a device with this serial number
  1960994008
  
  [36][nadiscvr.c][2410][GetPathViaSerial]:serial [1960994008] and
   isLibrary 0
  [36][nadiscvr.c][2436][GetPathViaSerial]:Found a match in SAN
   Info List and create device name is Tape6 serial [1960994008]
  [36][nadiscvr.c][2446][GetPathViaSerial]:for serial [1960994008]
   we found a path Tape6ape5
  [36][pspvr.c][2579][PvrDiscoverPath]:rc = 0 result = 0 old path
   = \\.\Tape5 new path = Tape6ape5
  [36][mmsdrive.c][12535][DiscoverNewPath]:SAN discovery found a
   new path: Tape6ape5.
  [36][mmsdrive.c][12576][DiscoverNewPath]:DiscoverNewPath
   successfully found a new path for drive DRIVE2. The new path is
   Tape6ape5, and the old path is \\.\Tape5.
  [36][pspvr.c][2686][PvrPsOpenDevice]:PvrOpenDevice: error
   opening Tape6ape5
    Reason: the system cannot find the file specified.
    path Tape6ape5 handle -1 rc 4c
  [36][pvr.c][5799][PvrOpenDevice]:Attempted to open device
   Tape6ape5, 1 time(s), rc = 76.
  [36][mmsdrive.c][12584][DiscoverNewPath]:Drive DRIVE2 failed to
   open with the newly discovered path Tape6ape5, rc = 76
  [36][pspvr.c][2686][PvrPsOpenDevice]:PvrOpenDevice: error
   opening \\.\Tape6ape5
    Reason: The system cannot find the file specified.
    path \\.\Tape6ape5 handle -1 rc 4c
  [36][pvr.c][5799][PvrOpenDevice]:Attempted to open device
   \\.\Tape6ape5, 1 time(s), rc = 76.
  [36][pspvr.c][2760][PvrCloseDevice]:device with handle 67420 is
   closed
  [36][pspvr.c][2772][PvrCloseDevice]:Removing device \\.\Tape5
   with handle 67420 from devList
  [36][mmsdrive.c][8293][MmsCheckTapeId]:Returning from
   MmsCheckTapeId for drive DRIVE2 with rc = 76.
  [36][mmsdrive.c][6917][MmsDestroyDriveDesc]:Destroying drive
   descriptor for drive DRIVE2 (\\.\Tape5) in library TS7650LIB.
  [36][output.c][6673][PutConsoleMsg]:ANR0409I Session 5 ended for
   server SERVERLM (Windows).~
  [36][mmsshr.c][5012][SignalMountDone]:MountCount decremented to
   0 for library TS7650LIB.
  [36][pvrmp.c][5846][PvrChangeMpStatus]:Changing MP 0 status from
   3 to 0.
  [36][output.c][6673][PutConsoleMsg]:ANR1404W Scratch volume
   mount request denied - mount failed.~
  
  Initial Impact:  Medium
  
  Additional Keywords:
  TSM zz61 zz62  protectier
  

Local fix

• Use device name \\.\Tapex   when defining tape drive pathes.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users of   *
  *                 the SAN discovery function with IBM tape     *
  *                 devices                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: See error description.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 5.4.7, 5.5.5, 6.1.5 and 6.2.2.     *
  *                 Note that this is subject to change at       *
  *                 the discretion of IBM                        *
  ****************************************************************
  *
  

Problem conclusion

• This problem was fixed.
  Affected platform: Microsoft 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

• R54W PSY

     UP

• R55W PSY

     UP

• R61W PSY

     UP

• R62W PSY

     UP