IT07640: TIVOLI STORAGE MANAGER CLIENT GUI HANGS WHEN PERFORMING A SEARCH AND ENCOUNTERING A MULTIBYTE CHARACTER

IBM Tivoli Storage Manager Client 6.4.3 Downloads and READMEs
IBM Spectrum Protectâ„¢ Client 7.1.3 Downloads and READMEs

APAR status

• Closed as program error.

Error description

• The Tivoli Storage Manager Client GUI (dsmj) may hang when
  issuing a search through archive or backup objects and one is
  found which contains a multibyte character (eg umlaut).
  
  The file count displayed for "Files inspected" will not progress
  past this point and the GUI will hang until cancelled.
  
  
  Tivoli Storage Manager Versions Affected:
  All supported versions and all supported Unix operating systems
  
  Customer/L2 Diagnostics (If Applicable)
  Obtaining a client service trace and also a Java trace will show
  we find a filename containing a multibyte character :
  
  cuqrepos.cpp        (1771): NetToAttrib(): maj: 6, min: 6, os:
  12, fs: 2, client: 1, fileSize: 96
  cuqrepos.cpp        (1775):                type: 586, build: 0,
  mod: 0, attrOnly: 0
  cuqrepos.cpp        ( 662): cuGetArchQryResp: fsID: 9, hl:
  '/dir1/dir2', ll: '/Produktivitﾄt', objType: DIR
  cuqrepos.cpp        ( 667):                   type: 1112,
  fileSize: 96, mgmtClass: 1, copyGroup: 1
  cuqrepos.cpp        ( 671):                   insDate: 05/19/03
  10:16:48, defunct: false, owner: 'Scan Start Time: Thu Sep 19
  10:21:16 2002'
  cuqrepos.cpp        ( 675):                   expDate: 00/00/35
  00:00:00, versId: 0.47489497387433, restOrder: 0.0.0.0.0,
  mediaClass: fixed
  cuqrepos.cpp        ( 691):                   descr: 'Scan Start
  Time: Thu Sep 19 10:21:16 2002'
  dicuqry.cpp         ( 956): =========> Entering
  dicuSendArchQryResp()
  
  but within the Java trace taken at the same time, we appear to
  pass an empty string :
  
  SessID=2, IM (imArchQry): Exiting
  SessID=2, DcgServerRvFileSystemTree (cgGetFileEntries): Exiting
  SessID=2, DcgServerRvFileSystemTree (cgGetNodeEntries): Exiting
  DcgFilterEngine.traverseTree() -> go through childs :
  Entering DcgFilterEngine.traverseTree(,false
  DcgFilterEngine.traverseTree() -> current node is :
  Entering DcgFilterEngine.matchesSearchObjType()
  Entering DcgFilterEngine.nodeMatches(,false)
  Entering DcgFilterEngine.matchesFileType()
  DcgFilterEngine.traverseTree() -> is a search load the node :
  
  
  SessID=2, DcgServerRvFileSystemTree (cgArchQryCallBack): fsID =
  9 hl = /dir1/dir2 ll =
  DcgFileSystemTree::cgSetMCName: mcList.size = 4
  DcgFileSystemTree::cgSetMCName: mcListElement.mcNum =
  15cAttr.mcNum = 1
  
  Note :
  The "current node" and "ll=" are both blank.
  
  This was caused by the locale used and the Backup/Archive client
  not handling the returned value from the system call mbstowcs()
  which leads to an endless loop. In the above example, the LANG
  was set to "en_us" and LC_ALL was set to "Posix". The multibyte
  character encountered could not be translated correctly to
  unicode.
  
  Changing the local so that LANG=en_US and LC_ALL=en_US resolved
  the issue and allowed the search to continue.
  
  Initial Impact: Low|Medium|High
  Low
  
  Additional Keywords:
  TSM java hang
  

Local fix

• Amend the locale that the client GUI is ran in to a supported
  locale for the character set used. Eg, before running dsmj :
  
  export LANG=en_US
  export LC_ALL=en_US
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Tivoli Storage Manager backup-archive client versions 6.3,   *
  * 6.4 and 7.1 on all platforms                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in levels 6.4.3 and 7.1.3.             *
  * Note that until these levels are available, this information *
  * is subject to change at the discretion of IBM.               *
  ****************************************************************
  *
  

Problem conclusion

• The problem has been fixed so that it no longer occurs.
  

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:

Modules/Macros

• dsmagent
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels

• R64A PSY

     UP

• R64H PSY

     UP

• R64L PSY

     UP

• R64M PSY

     UP

• R64S PSY

     UP

• R64W PSY

     UP

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71M PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP