IT05420: LARGE FILELIST RESTORE/RETRIEVE SHOWS BAD PERFORMANCE FOR MULTILINKED OBJECTS.

TSM client 7.1.1.x interim fix downloads
IBM Tivoli Storage Manager (TSM) Client 7.1.2 Downloads and READMEs
IBM Tivoli Storage Manager Client 6.4.3 Downloads and READMEs
IBM Tivoli Storage Manager (TSM) client 6.3.2.x interim fix downloads - EOL

APAR status

• Closed as program error.

Error description

• During filelist restore/retrieve it is observed that it takes a
  lot of time to prepare the list of objects to process.
  The symptom is caused by the client calling the SameLink()
  function exponentially if the objects to process are
  multilinked, that is having two or more links to the same data
  object.
  In a service trace you can find evidence looking at a trace
  section like the following:
  07/04/2014 13:28:08.999 [008111] [4026529536] : restproc.cpp
  (13161): =========> Entering SameLink()
  07/04/2014 13:28:08.999 [008111] [4026529536] : restproc.cpp
  (12175): =========> Entering MakeRestList()
  07/04/2014 13:28:08.999 [008111] [4026529536] : restproc.cpp
  (12330): MakeRestList: added entry for '<FILESPACE>' '<HL>'
  '<LL>'
  07/04/2014 13:28:08.999 [008111] [4026529536] : restproc.cpp
  (11462): rpAdd(): restore list size: 10000
  The symptom occurs as the client compares attributes of each
  file with attributes of other files when adding a new file into
  the in-memory file list in order to find all the hard links for
  the file.
  If the filelist has many references to hard linked files, the
  hard link checking occurs on each of those objects and this
  checking may significantly add to the time needed for the
  creation of the in-memory file list.
    Tivoli Storage Manager Versions Affected: all supported
    Initial Impact: Medium
    Additional Keywords:TSM list huge links memory zz62 zz63 zz64
  zz71
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Tivoli Storage Manager for Client versions 6.3, 6.4 and 7.1  *
  * running on all AIX, HP IA64, Linux x86, Mac, and Solaris     *
  * 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.2.             *
  * 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

• A fix for this problem is currently targeted for 6.3.2.3 and
  7.1.1.4 interim fix package. Until this interim fix is actually
  available this information is subject to change at the
  discretion of IBM.
  

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

• DSMC
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63M PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP

• 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